LT-22298: Fix Patch Build Numbers #491
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Rename all former BUILD_NUMBER references to RELEASE_BUILD_NUMBER. * Round $lastJenkins build numbers to the next hundred for easier association with GHA run numbers. * Also ignore nunit_random_seed.tmp Change-Id: Ic040408ad62a9846558cb84700bad0b7591f8576
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would really prefer to revert back to BUILD_NUMBER, which was a reserved environment variable in Jenkins but not in GHA. Thoughts?
This change is