Script Step Templates need editing to be backward compatible

Legacy Uncategorised
1

I’ve imported a Script Step Template (Windows Scheduled Task - Create) and it worked fine on development server running Octopus 3.3.17. Then I’ve imported it on production server running Octopus Deploy 2.6.5.1010, and, when creating release, it asked to provide package.
When trying to deploy it returned a warning:
Scheduled Task - Create
Warning: there are no enabled machines in the roles specified by this step, in this environment. This step will be skipped.

I’ve compared the structure of Script Step Template on old and new server and found that JSON in new step has a few extra properties

“Octopus.Action.Script.Syntax”: “PowerShell”,
“Octopus.Action.Script.ScriptSource”: “Inline”,
“Octopus.Action.Script.ScriptFileName”: null,
“Octopus.Action.Package.NuGetFeedId”: null,
“Octopus.Action.Package.NuGetPackageId”: null

Once I’ve deleted them fromJSON and re-imported the template, old server processed Step Template correctly.

This info may be useful to someone, who still running old version of Octopus.

2

Hi Michael,

Thanks for getting in touch! As we continually make changes and improvements backwards compatibility is just not something we can provide between major versions.
Thanks for pointing out the fix for any others who are going to be in this situation.

May I ask why you are running both versions, and if the 2.6 will be upgraded?
Vanessa