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

Not able to use a normal agent on stage when agent docker is declared globally

      When the agent globally defined is a a docker-based, then if a stage defined another agent, it seems that we are facing JENKINS-33510.

       

      PR: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/192

          [JENKINS-46831] Not able to use a normal agent on stage when agent docker is declared globally

          Adrien Lecharpentier created issue -
          Adrien Lecharpentier made changes -
          Description Original: When the agent globally defined is a a docker-based, then if a stage defined another agent, it seems that we are facing JENKINS-33510. New: When the agent globally defined is a a docker-based, then if a stage defined another agent, it seems that we are facing JENKINS-33510.

           

          PR: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/192
          Andrew Bayer made changes -
          Link New: This issue is duplicated by JENKINS-47103 [ JENKINS-47103 ]
          Andrew Bayer made changes -
          Priority Original: Critical [ 2 ] New: Major [ 3 ]
          Andrew Bayer made changes -
          Link New: This issue is duplicated by JENKINS-50897 [ JENKINS-50897 ]
          Andrew Bayer made changes -
          Link New: This issue is duplicated by JENKINS-54586 [ JENKINS-54586 ]
          Andrew Bayer made changes -
          Assignee Original: Andrew Bayer [ abayer ]
          Jesse Glick made changes -
          Component/s New: docker-workflow-plugin [ 20625 ]
          Nicholas Brown made changes -
          Link New: This issue relates to JENKINS-64874 [ JENKINS-64874 ]

            Unassigned Unassigned
            alecharp Adrien Lecharpentier
            Votes:
            9 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: