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.
|Workflow||JNJira [ 160090 ]||JNJira + In-Review [ 180250 ]|
|Component/s||pipeline-general [ 21692 ]|
|Component/s||workflow-plugin [ 18820 ]|
|Component/s||workflow-scm-step-plugin [ 21717 ]|
|Component/s||pipeline [ 21692 ]|
|Remote Link||This issue links to "subversion PR 176 (Web Link)" [ 15341 ]|
|Assignee||Jesse Glick [ jglick ]||Andrew Bayer [ abayer ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Remote Link||This issue links to "Git plugin PR #492 (Web Link)" [ 16318 ]|
|Remote Link||This issue links to "Core PR #2730 (Web Link)" [ 16319 ]|
|Remote Link||This issue links to "SCM Step PR #16 (Web Link)" [ 16320 ]|
|Remote Link||This issue links to "SVN PR #182 (Web Link)" [ 16321 ]|
|Remote Link||This issue links to "Mercurial PR #102 (Web Link)" [ 16322 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
Hello, I had this support ticket [https://support.cloudbees.com/hc/en-us/requests/47538] marked as resolved based on the work done to resolve this issue. My request was for pipeline to support GHPRB style "skip build phrase". Forgive me but it's not obvious how I would leverage the fix for this issue to give me the "skip build phrase" type functionality. Could you give some pointers on that?
|Remote Link||This issue links to "Page (Jenkins Wiki)" [ 20839 ]|