Skip to content
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

Merged
merged 9 commits into from
Dec 19, 2024
Merged

fix: deployment workflow run rework #2566

merged 9 commits into from
Dec 19, 2024

Conversation

rolljee
Copy link
Contributor

@rolljee rolljee commented Dec 18, 2024

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

      - name: Get current version from package.json
        shell: bash
        id: get-version
        run: |
          echo "version=$(jq -r .version package.json)" >> $GITHUB_OUTPUT
          echo "major-version=$(jq -r .version package.json | cut -d. -f 1)" >> $GITHUB_OUTPUT

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

@rolljee rolljee self-assigned this Dec 18, 2024
@github-advanced-security
Copy link

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.

Copy link
Contributor

@fmauNeko fmauNeko left a 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 ?

@rolljee
Copy link
Contributor Author

rolljee commented Dec 18, 2024

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

@rolljee rolljee merged commit 78e3176 into 2-dev Dec 19, 2024
61 checks passed
@rolljee rolljee deleted the fix/workflow-run-rework branch December 19, 2024 15:36
@kuzzle
Copy link
Contributor

kuzzle commented Dec 19, 2024

🎉 This PR is included in version 2.35.0-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@kuzzle
Copy link
Contributor

kuzzle commented Dec 19, 2024

🎉 This PR is included in version 2.35.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@kuzzle kuzzle added the released This issue/pull request has been released. label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released on @beta released This issue/pull request has been released.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants