Tom Langeraet
My feedback
-
123 votesTom Langeraet
supported this idea
·
-
250 votesTom Langeraet
supported this idea
·
-
1 voteTom Langeraet
shared this idea
·
-
568 votes
Thanks everyone who voted on this. We’ve spent a lot of time thinking about how best to version control Octopus configuration, and came to an approach that is a little different to what was imagined in this blog post. I just published an RFC post with our plans – I’d really appreciate if you could take a look and leave a comment!
An error occurred while saving the comment -
10 votes
An error occurred while saving the comment Tom Langeraet
commented
I am referring to the following log item, which originates from Octostach:
`The following tokens were unable to be evaluated: '#{aaa}', '#{bbb}'`
Tom Langeraet
shared this idea
·
-
25 votesTom Langeraet
supported this idea
·
An error occurred while saving the comment Tom Langeraet
commented
I am also struggling with a similar issue, where the idea is practically the same. When we create step templates for others to use, they shouldn't know about the underlying dependency on script modules.
So your idea is good, but it might be better to make it somewhat more generic, so all (no matter what type) step templates can depend on script modules ...
Adding "PreDeploy.ps1", "Deploy.ps1" or "PostDeploy.ps1" scripts to your NuGet package will trigger the Octopus built-in hooks and execute your custom scripts, which you can store in source control ...