-
Improvement
-
Resolution: Fixed
-
Major
-
None
Popular maven plugins designed to give you access to the git branch name are ineffective when using the workflow Multibranch Plugin.
- The JGit Build Number plugin at https://github.com/alx3apps/jgit-buildnumber falls back to coimmit id because GIT_BRANCH is not getting populated
- The Git Commit ID Maven Plugin from https://github.com/ktoso/maven-git-commit-id-plugin also fails to extract the branch (unsure why)
For multbranch builds it's reasonable to expect use cases where the branch info is use to augment artifact names and manifest entries so people can easily distinguish branch built artifacts from one.
Would be nice if the DSL just made this state available - but populating the env would be a nice start.
- is blocking
-
JENKINS-30744 multibranch issues if branch contains /
-
- Closed
-
- is related to
-
JENKINS-24141 SCM with non-AbstractProject, revisited
-
- Closed
-
-
-
- Open
-
-
-
- Resolved
-
- links to
[JENKINS-30252] Provide easy access to git branch name in multibranch workflow scripts
Ronald Pomeroy
created issue -
Ronald Pomeroy
made changes -
| Comment |
[ I tried to log out the env.JOB_NAME with echo " *** ${env.JOB_NAME} *** " and got ... Running: Print Message *** ${env.JOB_NAME} *** ... ] |
env.JOB_NAME (I assume) is static. If new branches are indexed (in the multibranch plugin case) how can the JOB_NAME contain the git branch name?
Am I missing something?
Regards
Ron
Ronald Pomeroy
added a comment - - edited env.JOB_NAME (I assume) is static. If new branches are indexed (in the multibranch plugin case) how can the JOB_NAME contain the git branch name?
Am I missing something?
Regards
Ron Yes you are missing something. For example, in the stock CD demo (1.10), adding
echo "running from ${env.JOB_NAME.replaceFirst('.+/', '')}"
works (after approving method java.lang.String replaceFirst java.lang.String java.lang.String for the sandbox).
| Labels | New: multibranch |
| Remote Link | New: This issue links to "Stack Overflow (Web Link)" [ 13165 ] |
| Link |
New:
This issue is blocking |
Ah. That explains why my workflow produces nulls in
node('docker') { checkout scm; echo "Build of ${env.GIT_COMMIT} on ${env.GIT_BRANCH}"; // etc etc
Seems like SCM passing environment vars is going to be pretty important?
magnayn
added a comment - - edited Ah. That explains why my workflow produces nulls in
node( 'docker' ) {
checkout scm;
echo "Build of ${env.GIT_COMMIT} on ${env.GIT_BRANCH}" ;
// etc etc
Seems like SCM passing environment vars is going to be pretty important? JENKINS-24141 tracks core changes needed to allow the Git plugin to define $GIT_COMMIT and the like. You can work around that particular variable using git rev-parse HEAD of course.
| Link |
New:
This issue is related to |
Depends on RFE to let SCM pass environment variables to a Run.
Workaround: env.JOB_NAME