Move all uses of BUILD_NUMBER to BUILD_ID #303
Labels
good first issue
Good for newcomers
Comments
stronk7
added a commit
to moodlehq/moodle-ci-runner
that referenced
this issue
Jun 7, 2024
Some old scripts still use BUILD_NUMBER instead of the newer BUILD_ID. The later is the preferred one in new scripts (no matter both still work). Once moodlehq/moodle-local_ci#303 is fixed we'll revert this change, when we have everything working with BUILD_ID.
stronk7
added a commit
to moodlehq/moodle-ci-runner
that referenced
this issue
Jun 7, 2024
Some old scripts still use BUILD_NUMBER instead of the newer BUILD_ID. The later is the preferred one in new scripts (no matter both still work). Once moodlehq/moodle-local_ci#303 is fixed we'll revert this change, when we have everything working with BUILD_ID.
stronk7
added a commit
to moodlehq/moodle-ci-runner
that referenced
this issue
Jun 7, 2024
Some old scripts still use BUILD_NUMBER instead of the newer BUILD_ID. The later is the preferred one in new scripts (no matter both still work). Once moodlehq/moodle-local_ci#303 is fixed we'll revert this change, when we have everything working with BUILD_ID.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since long ago, the "official" name of the build number env variable in Jenkins is
BUILD_ID.While the previous
BUILD_NUMBERone still works perfectly, right now we have a mix of uses. This is about to move all to beBUILD_ID(that is the official one and the one used by our newer tools).Ref.: https://www.jenkins.io/doc/book/pipeline/jenkinsfile/#using-environment-variables
Ciao :-)
The text was updated successfully, but these errors were encountered: