Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14597

Rundeck JobID doesn't persist when used as build publisher

XMLWordPrintable

      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.

          [JENKINS-14597] Rundeck JobID doesn't persist when used as build publisher

          Dominik Bartholdi added a comment -

          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.

          Dominik Bartholdi added a comment - 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.

          Youssuf ElKalay added a comment -

          Makes sense - I was indeed using the conditional build step and the Rundeck plugin within the flexible build publisher.

          Youssuf ElKalay added a comment - Makes sense - I was indeed using the conditional build step and the Rundeck plugin within the flexible build publisher.

          Capn Keelhauler added a comment -

          Similar problem to JENKINS-14454

          Capn Keelhauler added a comment - Similar problem to JENKINS-14454

          bap added a comment -

          The DataBoundConstructor in the Notifier does not correctly construct the object.
          The reason this is working when configured from the UI is that the Notifier's descriptor contains a newInstance method which is used in this case.

          The solution is to fix the Notifier by removing the DBC (in which case it will not be available in felible-publish) or remove the newInstance method from the Descriptor and fix the DBC to make it correctly configure the Notifier.

          bap added a comment - The DataBoundConstructor in the Notifier does not correctly construct the object. The reason this is working when configured from the UI is that the Notifier's descriptor contains a newInstance method which is used in this case. The solution is to fix the Notifier by removing the DBC (in which case it will not be available in felible-publish) or remove the newInstance method from the Descriptor and fix the DBC to make it correctly configure the Notifier.

          ikedam added a comment -

          It should be fixed in Flexible Publish 0.12 (JENKINS-19494).
          (I could not verify for I do not know how to use Rundeck).

          Please try it.

          ikedam added a comment - It should be fixed in Flexible Publish 0.12 ( JENKINS-19494 ). (I could not verify for I do not know how to use Rundeck). Please try it.

            buildscientist Youssuf ElKalay
            buildscientist Youssuf ElKalay
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: