OctopusDeploy
Parent steps sometimes need a target tag, even when child steps are set to run on workers
Severity
2 customers reported previously
Version
2025.4.1996
Latest Version
None
What happened?
Customer's are attempting to use parent-child steps to group steps that all can be run on a worker, but since they're running this as parent-child, it's forcing the deployment tags to be added for some steps, even when this is unwanted. (i.e. Run A Script + Run an Azure Script = Needs deployment tag).
This is also odd since if you use two Run an Azure Script steps, the tag is allowed to be blank (i.e. Run an Azure Script + Run an Azure Script = Can have blank deployment tag).
Reproduction
- Go into any process
- Add a Run an Azure Script step, and set this to be run on a worker
- Add a child step to the step above, then select Run an Azure Script, and set this to be run on a worker
- Save the process without modifying the overall parent-child container, which should go through successfully.
- If you then add another child step of the Run a Script type, when attempting to save this will error stating
Please select one or more target tags that 'Run an Azure Script' step will apply to
Error and Stacktrace
More Information
Related discussion: [Internal Slack Link]
Workaround
The workaround if a customer is coming across this would be to add a tag to their deployment target that can be used as a throw away. However, this can sometimes not be feasible if they don't want the deployment mimicking that particular target.
