Saving configuration wipes assignedNode

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Any saving of the configuration for a job removes the assignedNode from the config and sets canRoam to true. This is causing builds to run on nodes that can't support them and fail.

            Assignee:
            Unassigned
            Reporter:
            Steve Schwaller
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: