set variables before checkout #10
Open
Conversation
This file contains 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
|
Likely addresses https://issues.jenkins-ci.org/browse/JENKINS-32532 |
|
Pre-checkout does not actually cover all cases. E.g. if you use a Pre-SCM build step, the info won't be propagated there. Fix like oleg-nenashev/ownership-plugin@9871283 should be a better solution |
@oleg-nenashev is your observation and suggestion still valid today? @kizdebski are you still interested in this pull request? Thanks! |
|
Likely this issue: https://issues.jenkins-ci.org/browse/JENKINS-24277 |
|
@fabiodcasilva I'm interested. On newest version of plugin problem still exists. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Can we move providing environment parameters before checkout?
Some plugins like jenkins release plugin (my case) run in "Build Environment, not directly in "Build". Effect is that during releasing version variables are not generated yet.
Moving variables generation before scm checkout solves such cases.