Child Step Run Condition Blocks Upgrades to Step Template

[dgschmitz]

Is there a known issue with child step run conditions causing failures to step template upgrades?

My team and I have been experiencing issues updating step templates since Run Conditions became available on child steps which as our run conditions get more complex is often quite painful. I recently upgrade our server to the latest build 2020.4.11 and haven’t seen the issue go away.

Steps to Replicate:

1. Create simple step template
2. Create project with a single parent step and multiple child steps based on step template
3. Add Run Condition to each child step
4. Do simple modification to step template code (ex. add write-host) and Save
5. In step template usage, attempt to Update All which will result in failure

Our current work-around is as follows:

1. Update step template and save
2. Remove project process child step run conditions
3. Go back to step template -> Usage and update all
4. Re-add child step run conditions

Any help on this would be greatly appreciated.

Thanks,
Dave Schmitz
dgschmitz@symplr.com

[donny.bell]

Hi Dave,

Thank you for contacting Octopus Support.

It looks like you are experiencing this bug:

Child step based on custom template can't be updated if it has a variable run condition

The good news is that the bug has already been addressed in 2020.5.X. From the information I have, it looks like this version should be publicly available either this week or next.

Let me know if you have any questions about this or anything else. We’re here to help.

Regards,

[dgschmitz]

Thank you for the quick response. I look forward to the fix.