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

Pull Request and pipeline agent

XMLWordPrintable

      • I have a Jenkins node master "master" (on Windows) + 1 agent called "Alpha" (on Windows)
      • I have an Github Enterprise Repository configured in Jenkins.
      • I use a JenkinsFile for the pipeline with this :
      pipeline {
	options {
		skipDefaultCheckout(true)
		disableConcurrentBuilds()
	}
	agent {
		label 'Alpha'
	}
        ....
}

      All works well when:

      • I start a build manually in Jenkins -> the build is executed with the "Alpha" agent
      • I commit on Git => Trigger a build on the "Alpha" agent

      But when I create a pull request, the build is executed on the "master" agent

          [JENKINS-52216] Pull Request and pipeline agent

          frederic larde created issue -
          frederic larde made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          frederic larde made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-model-definition-plugin [ 21706 ]
          Component/s Original: pipeline [ 21692 ]

          Andrew Bayer added a comment -

          That is deeply weird - I can't reproduce it. Any chance you could zip/tar up the build directories for a build that does the right thing and one that does the wrong thing? I'm talking about the directories like JENKINS_HOME/jobs/repo-name/jobs/branch-name/builds/123.

          Andrew Bayer added a comment - That is deeply weird - I can't reproduce it. Any chance you could zip/tar up the build directories for a build that does the right thing and one that does the wrong thing? I'm talking about the directories like JENKINS_HOME/jobs/repo-name/jobs/branch-name/builds/123 .

          frederic larde added a comment -

          I'm sorry, this issue didn't appeared again. It seems that it has been fixed between 2.131 and  2.138

          frederic larde added a comment - I'm sorry, this issue didn't appeared again. It seems that it has been fixed between 2.131 and  2.138
          frederic larde made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            lardef frederic larde
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: