-
Bug
-
Resolution: Fixed
-
Major
-
CentOS 6 x86-64
JDK 1.6.x (latest version)
When using the Rundeck Jenkins Plugin as a build publisher within a conditional build-step (either single or multi-step) the JobID field doesn't persist to the job's config file after the job configuration page is saved.
I have tested filling out the Rundeck jobID field outside of the conditional build publisher fields and the data does persist.
On a side note the Rundeck plugin makes a call to Rundeck to verify the contents of the jobID (it takes a UUID, job ID or job/project name) and displays the full name of the job directly underneath the field. I'm not sure if this call flow is causing issues with the conditional build publisher or not.
- depends on
-
JENKINS-19494 Flexible Publish does not work with Publishers using Descriptor#newInstance
- Closed