-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: deployment workflow run rework #2566
Conversation
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a specific reason to use ubuntu-20.04
instead of a more recent version ?
I made some test trying to fix an issue with npm install. but i found the guilty one. I'll run using ubuntu 24.04 instead |
Quality Gate passedIssues Measures |
🎉 This PR is included in version 2.35.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 2.35.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What does this PR do ?
This PR rework the way the deployment workflow runs.
We had an issue where some docker images were not properly tagged. For example, this run of CD should have created the 2.34.0 tag instead of the 2.34.0-beta.1 tag for the plugin-dev.
Turns out, the deployment using semantic was launched at the same time as the deployment docker images.
When semantic release ends the process it makes a commit to update the NPM version of Kuzzle. (You start to see what's coming?)
This commit was not always pushed when the process read the current package.json
Since the package version isn't updated, we still have the -beta.x suffix. Which result in a wrongly tagged docker image.
This PR aim to fix this issue making sure the semantic release process is ended when we start creating all docker images.
How should this be manually tested?
Well, you can't.
Other changes
Nope, nothing
Boyscout