Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
Description
It is not clear from documentation that you are not supposed to mix stage agents with top-level agents when using declarative pipeline (or perhaps you can now?).
Examples of documentation that mention nothing about this restriction:
A ticket that implies this is unsupported although not validated: JENKINS-51891
Attachments
Issue Links
- is related to
-
JENKINS-51891 Pipelines which need a node with a specific label do not proceed after adding label to a node
-
- Open
-
-
JENKINS-66442 Unable to override agent per stage
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is related to |
Summary | Clarify usage of multiple agents in pipeline | Clarify usage of multiple agents in declarative pipeline |
Description |
It is not clear from documentation that you are not supposed to mix multiple agents with top-level agents when using declarative pipeline (or perhaps you can?).
Examples of documentation that mention nothing about this restriction: - [https://www.jenkins.io/doc/book/pipeline/syntax/#agent] A ticket that implies this is unsupported although not validated: JENKINS-51891 |
It is not clear from documentation that you are not supposed to mix stage agents with top-level agents when using declarative pipeline (or perhaps you can?).
Examples of documentation that mention nothing about this restriction: - [https://www.jenkins.io/doc/book/pipeline/syntax/#agent] A ticket that implies this is unsupported although not validated: JENKINS-51891 |
Description |
It is not clear from documentation that you are not supposed to mix stage agents with top-level agents when using declarative pipeline (or perhaps you can?).
Examples of documentation that mention nothing about this restriction: - [https://www.jenkins.io/doc/book/pipeline/syntax/#agent] A ticket that implies this is unsupported although not validated: JENKINS-51891 |
It is not clear from documentation that you are not supposed to mix stage agents with top-level agents when using declarative pipeline (or perhaps you can now?).
Examples of documentation that mention nothing about this restriction: - [https://www.jenkins.io/doc/book/pipeline/syntax/#agent] A ticket that implies this is unsupported although not validated: JENKINS-51891 |
Link | This issue is related to JENKINS-51891 [ JENKINS-51891 ] |
Labels | documentation |
Component/s | core [ 15593 ] |