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

Rundeck JobID doesn't persist when used as build publisher

    XMLWordPrintable

Details

    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 or not.

      Attachments

        Issue Links

          Activity

            buildscientist Youssuf ElKalay created issue -
            buildscientist Youssuf ElKalay made changes -
            Field Original Value New Value
            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.
            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.
            domi Dominik Bartholdi made changes -
            Component/s flexible-publish [ 16130 ]
            Component/s rundeck [ 15941 ]
            Component/s conditional-buildstep [ 15947 ]
            Assignee domi [ domi ] bap [ bap ]
            bap bap made changes -
            Assignee bap [ bap ] Vincent Behar [ vbehar ]
            ikedam ikedam made changes -
            Link This issue depends on JENKINS-19494 [ JENKINS-19494 ]
            ikedam ikedam made changes -
            Assignee Vincent Behar [ vbehar ] Youssuf ElKalay [ buildscientist ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 145282 ] JNJira + In-Review [ 191418 ]

            People

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

              Dates

                Created:
                Updated:
                Resolved: