|
|
_0.png) |
|
|
|
|
Issue Type:
|
 Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
domi
|
|
Components:
|
conditional-buildstep |
|
Created:
|
27/Jul/12 6:00 AM
|
|
Description:
|
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.
|
|
Environment:
|
CentOS 6 x86-64
JDK 1.6.x (latest version)
|
|
Project:
|
Jenkins
|
|
Labels:
|
rundeck
|
|
Priority:
|
 Major
|
|
Reporter:
|
Youssuf ElKalay
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
Locked
as the rundeck plugin does not provide a builder but a notifier, I assume you refer to the flexible-publish plugin in the "post-build actions" and not to conditional-buildstep plugin in the "Build" section.