• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • core
    • None
    • Jenkins v1.472

      In jenkins v1.472 when saving an existing job that had definitions of specific slaves where to run the job, it looses that definition.

      Had to revert back to previous version 1.467.

          [JENKINS-14257] Saving job configuration loses assigned node

          R. Tyler Croy added a comment -

          I'm seeing this behavior on 1.471 as well (for what it's worth)

          R. Tyler Croy added a comment - I'm seeing this behavior on 1.471 as well (for what it's worth)

          R. Tyler Croy added a comment -

          Digging through the config.xml for a job that is updated after the upgrade, it seems the <assignedNode/> tag disappears entirely from the XML.

          R. Tyler Croy added a comment - Digging through the config.xml for a job that is updated after the upgrade, it seems the <assignedNode/> tag disappears entirely from the XML.

          R. Tyler Croy added a comment -

          This is a duplicate I believe of JENKINS-14197.

          Jose, I fixed this by downgrading my "Promoted Builds" plugin version from 2.6, I was then able to save the assigned node properly on 1.472

          R. Tyler Croy added a comment - This is a duplicate I believe of JENKINS-14197 . Jose, I fixed this by downgrading my "Promoted Builds" plugin version from 2.6, I was then able to save the assigned node properly on 1.472

          Jose Sa added a comment -

          I also had to downgrade the Promoted Builds plugin as the core alone was not enough.

          Jose Sa added a comment - I also had to downgrade the Promoted Builds plugin as the core alone was not enough.

            Unassigned Unassigned
            josesa Jose Sa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: