8000 CI(github-actions): Ensure build number tagging by Krzmbrzl · Pull Request #6033 · mumble-voip/mumble · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

CI(github-actions): Ensure build number tagging #6033

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

Merged
merged 1 commit into from
Jan 14, 2023

Conversation

Krzmbrzl
Copy link
Member

If the actual build is skipped due to a duplicate workflow run, the build number script won't run. This can be problematic if this would have been the only place where the script runs for the given commit as that'll mean that for this commit no build number will be tagged on our central server.

Therefore, we now fetch the build number in a separate step that will not be skipped, if the build itself is skipped.

Checks

@Krzmbrzl Krzmbrzl added the ci label Jan 14, 2023
@Krzmbrzl Krzmbrzl force-pushed the ci-ensure-build-on-push branch 2 times, most recently from b98d8f5 to d8078a0 Compare January 14, 2023 13:27
If the actual build is skipped due to a duplicate workflow run, the
build  number script won't run. This can be problematic if this would
have been the only place where the script runs for the given commit as
that'll mean that for this commit no build number will be tagged on our
central server.

Therefore, we now fetch the build number in a separate step that will
not be skipped, if the build itself is skipped.
@Krzmbrzl
Copy link
Member Author

💚 All backports created successfully

Status Branch Result
1.5.x

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@davidebeatrici davidebeatrici deleted the ci-ensure-build-on-push branch January 14, 2023 19:47
Krzmbrzl added a commit that referenced this pull request Jan 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0