When a job definition is published, triggers schedule builds on target instance. I am not sure there is any usecase when this is expected. But when target instance is mare passive result presenter, this behaviour is undesirable.

      I have not tested the scenario when the build is actually built on target instance and the build number clashes with incoming build from source instance.

          [JENKINS-25357] Remove job triggers from published jobs

          There are no comments yet on this issue.

            vjuranek vjuranek
            olivergondza Oliver Gondža
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: