-
Improvement
-
Resolution: Fixed
-
Major
-
None
The return value of the git step should be the commit hash, etc., and there should be a way to pass that back in to a subsequent git step in case you want to check out the same revision in another workspace (without copying files).
The workaround is to archive and then unarchive sources.
- depends on
-
JENKINS-24141 SCM with non-AbstractProject, revisited
-
- Closed
-
- is blocking
-
JENKINS-37584 P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
-
- Closed
-
- is duplicated by
-
JENKINS-34455 Provide easy access to current commit ID in Jenkinsfile
-
- Resolved
-
-
JENKINS-36436 Environment variables are always NULL
-
- Closed
-
-
JENKINS-35230 The environment variables of git plugin not working in pipeline script.
-
- Closed
-
- is related to
-
JENKINS-45962 GIT_BRANCH variable is not populated in jenkins pipeline
-
- Closed
-
-
JENKINS-26129 Multibranch workflow projects
-
- Resolved
-
-
JENKINS-31386 "checkout scm" does not work in standalone jobs
-
- Resolved
-
-
JENKINS-26942 Easy to way to copy workspace files
-
- Resolved
-
-
JENKINS-30412 Access to build's own changelog from script
-
- Resolved
-
-
JENKINS-47226 Provide easy access to git branch name in (single branch) Pipeline build
-
- Open
-
-
JENKINS-27018 Provide either 'branch' or 'tag' in git step
-
- Resolved
-
- relates to
-
JENKINS-44449 Provide GIT_COMMIT_SHORT environment variable
-
- Closed
-
- links to
- mentioned in
-
Page Loading...
markewaite thanks a lot for your help, upgrading the Git Plugin to 3.3.2 indeed solved my problem !