Skip to content

95-move-to-new-version.md

Latest commit

 

History

History
59 lines (30 loc) · 4.3 KB

95-move-to-new-version.md

File metadata and controls

59 lines (30 loc) · 4.3 KB

Move to new version of Galasa

These are manual steps to bump the version of Galasa to the next version.

  1. Create a new branch in all of the repositories below called something like 'version-bump' (don't call it 'release').

  2. Upgrade Galasa

    a. Invoke the ./tools/set-version --version {new version} script in which invokes a separate set-version.sh for each module.

    b. Run the ./tools/build-locally.sh, which will invoke each individual module's build-locally.sh script, which will update the versions in the generated release.yamls.

    c. Manually check that all dev.galasa bundles have been upgraded. Do a search for the current version in VSCode to check for any versions that did not get uplifted by the script, and replace with the new development version.

    d. Make sure the API Server starts locally.

    e. Push the changes to your branch, open a PR, wait for the PR build to pass, then merge in the PR, and wait for the Main build to pass and finish.

    f. When the Isolated Main build is triggered following the CLI module build, cancel it on the GitHub UI here with the "Cancel Workflow" button, as you are going to rebuild it in a next step anyway.

    Note: Once the Galasa mono repo's build finishes, this will trigger the recycle-prod1 Tekton pipeline, which will then trigger the run-tests Tekton pipeline. The run-tests will fail as the CPS properties have not yet been upgraded to the new development version (unless you have already done it with galasactl) - this is okay.

  3. Upgrade Helm

    a. Invoke the set-version --version {new version} script.

    b. Push the changes to your branch, open a PR, wait for the PR build to pass, then merge in the PR, and wait for the Main build to pass and finish.

  4. Upgrade Simplatform

    a. Invoke the set-version --version {new version} script. Note: This will fail if the Galasa OBR has not been fully rebuilt and redeployed yet to the development.galasa.dev site, as the set-version.sh script uses mvn to uplift the versions, which will look for Simplatform's dependencies at the new version in Maven Central then the development.galasa.dev site.

    b. Push the changes to your branch, open a PR, wait for the PR build to pass, then merge in the PR, and wait for the Main build to pass and finish.

  5. Upgrade Web UI

    a. Invoke the set-version --version {new version} script.

    b. Push the changes to your branch, open a PR, wait for the PR build to pass, then merge in the PR, and wait for the Main build to pass and finish.

  6. Upgrade Integratedtests (not a released component)

    a. Currently no set-version.sh script exists so do a search for the current version in VSCode and replace with the new development version. Note: A story is open to create a set-version script so this should be updated when that is complete. Manually check that all dev.galasa bundles have been upgraded then run build-locally.sh to check it builds.

    b. Push the changes to your branch, open a PR, wait for the PR build to pass, then merge in the PR, and wait for the Main build to pass and finish.

  7. Upgrade the internal integrated tests (not a released component)

    a. Currently no set-version.sh script exists so do a search for the current version in VSCode and replace with the new development version. Note: A story is open to create a set-version script so this should be updated when that is complete.

    b. Push the changes to your branch, open a PR, then merge in the PR, and wait for the Main build to pass and finish.

  8. Upgrade Isolated

    a. Invoke the set-version --version {new version} script.

    b. Make sure it builds with the build-locally.sh.

    c. Push the changes to your branch, open a PR, wait for the PR build to pass, then merge in the PR, and wait for the Main build to pass and finish.