Details
-
Story
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Not Needed
-
Iteration Orange, Iteration Papaya
Description
Compass releases are almost fully automated except for 2 manual steps that has to happen to trigger the release and to finalize the release.
1) Add a npm run release beta command to compass.
npm run release beta starts a beta release of compass from a release branch.
npm run release start-beta can only run from a MAJOR.MINOR-release
branch.
It bumps the version according to the branch name, doing +1 on the prerelease version as required:
- Newly promoted branch:
If the release branch is 1.22 and package.version < 1.22.0, it will create 1.22.0-beta.0. - Beta bump:
When package.version is 1.22.0-beta.0, do 1.22.0-beta.1. - New beta after bumped GA:
When package.version is 1.22.1, do 1.22.2-beta.0.
2) Add a npm run release ga command to compass.
npm run release ga starts a GA release of compass from a release branch.
It bumps the version according to the branch name:
- Newly promoted branch:
If the release branch is 1.22 and package.version < 1.22.0, it will create 1.22.0. - Promote from beta:
When package.version is 1.22.1-beta.123, do 1.22.1. - GA bump:
When package.version is 1.22.1 do 1.22.2.
3) Add a npm run release publish command to compass.
Which completes a release by publishing all the artifacts.
- Waits for all the artifacts to be available and correctly built.
- Checks for the relative Github release to exist.
- Publish the Github release
- Update the download center config with the new artifacts.
- Verifies that the new version is picked up by both download center and by the updater by issuing the same api call