-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Jenkins Enterprise ver. 1.424.1
cloudbees-folder 1.7
parameterized-trigger 2.12
I am using the Cloudbees Folder plugin. Normal build triggers can defined with relative paths, but the parameterized triggers need to be defined explicitly, with the full Folder path name.
For example, I have a folder
Product1/Release1
If the Build job in the folder wants to trigger a Test job in the same folder, I have to fully write Product1/Release1/Test.
This makes copying configured jobs(or folders) difficult, because if you copy a job, you have to make sure to change every reference.
[JENKINS-12408] paramaterized-triggers do not cooperate with cloudbees Folders to see jobs in the current folder.
Assignee | Original: huybrechts [ huybrechts ] | New: cjo9900 [ cjo9900 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 142774 ] | New: JNJira + In-Review [ 190263 ] |
Closing as should have been fixed in 2.13 by commit
https://github.com/jenkinsci/parameterized-trigger-plugin/commit/693c20eb1140d77e7dd1075fa52a0164fc4667f1