Open ivanguravel opened 9 months ago
Just a note about the alternate test in the "Anything else?" section - That test case is not equivalent to the reported bug on this issue. By default, the "when" condition is evaluated after entering the agent. This can be changed by adding "beforeAgent true" to the "when" block. See - https://www.jenkins.io/doc/book/pipeline/syntax/#evaluating-when-before-entering-agent-in-a-stage
Jenkins and plugins versions report
What Operating System are you using (both controller, and any agents involved in the problem)?
amazon linux
Reproduction steps
create the Jenkinsfile and place the agent code inside there:
Expected Results
when env variable condition is happening then 1 task is running on the ecs side.
Actual Results
when env variable condition is happening then 2 tasks are running on the ecs side (one per agent).
Anything else?
also we have been tried to use additional step:
but we have still the choice between 2 agents (2 tasks on the ecs clusters).