Release build process

1. Run the release build in Jenkins

https://hyc-liberty-tools-team-jenkins.swg-devops.com/job/liberty-tools-eclipse-release/ (Sorry... IBM only)

The release build does the following:

1. Clones the latest content from this git repository
2. Builds and runs our suite of tests scenarios on Linux
3. Signs the repository content
4. Outputs the signed repository directory and repository zip

2. Download and manually test

The release build already runs all of our test scenarios on Linux. The only required testing at this point is to make sure the tool installs without the "Installing unsigned content" prompt (we have yet to figure out how to automate this check).

3. Upload the repository directory and repository.zip to DHE

1. SFTP using IBM intranet id to w3-transfer.boulder.ibm.com
2. CD to /www/stage/export/pub/software/openliberty/liberty-tools-eclipse
3. Make new directory for new version
4. Transfer repository/ and repository.zip to new directory and latest/ directory
5. Wait for sync to public site: https://public.dhe.ibm.com/ibmdl/export/pub/software/openliberty/liberty-tools-eclipse/ (should occur every hour)

4. Create new entry in Eclipse Marketplace

1. Log in to https://marketplace.eclipse.org/content/liberty-tools
2. Click "Edit" on marketplace entry
3. Create new "Solution Version" for the new version being added (Add link to DHE public site)

5. Create git tag and release

1. Check out latest in local git main branch
2. git tag <tag_name> e.g. git tag liberty-tools-0.9.0.202305051539
3. git push origin <tag_name>
4. Click on "Draft new release" here: https://github.com/OpenLiberty/liberty-tools-eclipse/releases
5. Select newly created tag, add title and description (following previous releases)
6. Change name of repository.zip to full name e.g. io.openliberty.tools.update.eclipse-repository-0.9.0.202305051539.zip and attach to release