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

Suprizing behavior for tied jobs

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Jenkins 1.525

      I have five slaves S01 to S05.

      Put S03 into "tied jobs only" and then tied several jobs to it in the usual way.

      SURPRISE: Later I was having issues with different job on S02, so wanted to have the job run on some other system. So I restricted it to "!S02". This allowed it to run on S03 which was not a behavior I expected.

            danielbeck Daniel Beck
            fmerrow Frank Merrow
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: