Zachary Sims
My feedback
-
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 Zachary Sims
supported this idea
·
-
20 votes
An error occurred while saving the comment Zachary Sims
commented
This, we'd also love this functionality as there's no way to tell what changed between releases. We've even reverted to putting the release number in our release notes, e.g.
for release 1.4.0.0 the notes would be:
1.0.0.0
* Initial version1.2.0.0
* Added a great new feature
1.3.0.0
* Fixed the great new feature1.4.0.0
* Removed the great new featureZachary Sims
supported this idea
·
-
11 votesZachary Sims
supported this idea
·
Jenkins has recently gone down this path. The (plugin) idea spawned out of Netflix: https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin
Basically it supports describing everything + scripts + whatever.