Minor I want to checkout files to specific change list. I can do this in Perforce Plugin passing CL to Label parameter, this does not work in P4 plugin.
[JENKINS-26373] Cannot checkout using change list
ilia s
created issue -
Paul Allen
made changes -
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
ilia s
added a comment - Hi Paul,
We have some use cases there we need to get files according to specific change list.
1. Developer wants to perform tests on private build and supplies change list from his private stream( not necessary latest CL)
2. Build fails and system wants to binary search between latest good CL and broken one to find who broke a build
3. Child Job wants to get same version as Parent job( submit may happens between )
Currently, we are using Perforce plugin(https://wiki.jenkins-ci.org/display/JENKINS/Perforce+Plugin) which supports a use case by using "P4 Label" configuration field of the perforce plugin. P4 Label accepts as Labels as ChangeLists
Thanks
Ilia
ilia s
added a comment - Hi Paul,
We have some use cases there we need to get files according to specific change list.
1. Developer wants to perform tests on private build and supplies change list from his private stream( not necessary latest CL)
2. Build fails and system wants to binary search between latest good CL and broken one to find who broke a build
3. Child Job wants to get same version as Parent job( submit may happens between )
Currently, we are using Perforce plugin( https://wiki.jenkins-ci.org/display/JENKINS/Perforce+Plugin ) which supports a use case by using "P4 Label" configuration field of the perforce plugin. P4 Label accepts as Labels as ChangeLists
Thanks
Ilia Paul Allen
added a comment - There are two ways you can do this with the new plugin:
1. pin a build to a label (under the Populate Options)
2. use a parameterized build, click on the 'Build Review' button and specify a label or change (the other fields are optional. You can also call this as a url endpoint (see Markdown file for details).
Paul Allen
added a comment - There are two ways you can do this with the new plugin:
1. pin a build to a label (under the Populate Options)
2. use a parameterized build, click on the 'Build Review' button and specify a label or change (the other fields are optional. You can also call this as a url endpoint (see Markdown file for details). Paul Allen
added a comment - The release 1.1.3 has a fix for use-case 3, where child builds will use the parent's change.
Paul Allen
added a comment - The release 1.1.3 has a fix for use-case 3, where child builds will use the parent's change. Paul Allen
added a comment - Old Issue Paul Allen
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 160438 ] | New: JNJira + In-Review [ 208334 ] |
Interesting feature; please will you provide me with some details on a typical use-case? If you rely on any other Jenkins plugins as part of the use-case let me know.