-
Bug
-
Resolution: Unresolved
-
Major
-
None
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
- is duplicated by
-
JENKINS-54586 Cannot mix dockerfile and non docker agents in a pipeline
-
- Resolved
-
-
JENKINS-50897 Running a project outside docker after specifying a dockerfile results in jenkins trying to run docker on the non-docker host
-
- Closed
-
-
JENKINS-47103 Parallel stages in declarative pipelines don't work with docker agents
-
- Closed
-
- relates to
-
JENKINS-64874 declarative pipeline post do not execute in agent
-
- Open
-
[JENKINS-46831] Not able to use a normal agent on stage when agent docker is declared globally
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 |
New:
When the agent globally defined is a a docker-based, then if a stage defined another agent, it seems that we are facing PR: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/192 |
Link |
New:
This issue is duplicated by |
Code changed in jenkins
User: Adrien Lecharpentier
Path:
pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AgentTest.java
pipeline-model-definition/src/test/resources/agentDockerGlobalThenLabel.groovy
http://jenkins-ci.org/commit/pipeline-model-definition-plugin/5db16c00a2e8e44dabed4905614342081374be2d
Log:
JENKINS-46831 Link to the issue declaration