Details

    • Similar Issues:

      Description

      After updating to latest Jenkins version, can't restrict nodes on any Inheritance Project task, either newly created or already existing. Autocompletion of nodes is not offered, and forcing a node name won't simply stay saved.
      It works fine on Freestyle projects.

        Attachments

          Issue Links

            Activity

            Hide
            mattmoor Matthew Moore added a comment -

            The fix has been merged, not sure what release it will make it into.

            Show
            mattmoor Matthew Moore added a comment - The fix has been merged, not sure what release it will make it into.
            Hide
            alghe Alexandru Gheorghe added a comment -

            Seems it went under: release v1.589

            Show
            alghe Alexandru Gheorghe added a comment - Seems it went under: release v1.589
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Just a notification Jenkins users...
            Please be aware about JENKINS-25533

            Show
            oleg_nenashev Oleg Nenashev added a comment - Just a notification Jenkins users... Please be aware about JENKINS-25533
            Hide
            mhschroe Martin Schröder added a comment - - edited

            Hi everyone.

            Maintainer of the "Inheritance Project Plugin" speaking here, which was the reason for this workaround.

            The root-cause has been fixed on our side, and the code from the plugin has been aligned with the code from LTS 1.596.x.

            We are currently preparing the full release of the updated plugin, which should arrive within a week (wk.26/27). It took longer than expected to move all of our internal plugins from 1.509.x to 1.596.x, which has significantly delayed upstreaming the complete set of fixes into the OSS community.

            We sincerely apologize for the delays and the resulting necessity for this ugly workaround in the Jenkins core.

            Show
            mhschroe Martin Schröder added a comment - - edited Hi everyone. Maintainer of the "Inheritance Project Plugin" speaking here, which was the reason for this workaround. The root-cause has been fixed on our side, and the code from the plugin has been aligned with the code from LTS 1.596.x. We are currently preparing the full release of the updated plugin, which should arrive within a week (wk.26/27). It took longer than expected to move all of our internal plugins from 1.509.x to 1.596.x, which has significantly delayed upstreaming the complete set of fixes into the OSS community. We sincerely apologize for the delays and the resulting necessity for this ugly workaround in the Jenkins core.
            Hide
            danielbeck Daniel Beck added a comment -

            Apparently long since fixed.

            Show
            danielbeck Daniel Beck added a comment - Apparently long since fixed.

              People

              • Assignee:
                mattmoor Matthew Moore
                Reporter:
                seb_p Sebastiano P
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: