Andrew McClenaghan
My feedback
-
40 votes
-
47 votes
-
292 votes
-
251 votes
Thanks everyone who provided feedback on this ticket. We published a blog post yesterday showing how to do PowerShell DSC with Octopus – everything from deploying DSC scripts, detecting drift, getting email notifications when drift occurs, and automatically fixing the drift:
https://octopus.com/blog/octopus-and-powershell-dsc
With that in mind, I think many of the comments on this suggestion are “done”. But there might be some areas of DSC support that we still don’t do. I’d really appreciate if you could read the post, and let us know of any scenarios we’ve missed. If it looks like we’ve done nearly everything, I might close this UserVoice suggestion and we can open new, more targeted suggestions for any gaps.
-
126 votes
-
48 votes
There is another idea that would solve this as well.
http://octopusdeploy.uservoice.com/forums/170787-general/suggestions/5492563-add-xmlpoke-feature-for-setting-random-config-valu -
98 votes
We are going to implement this soon. To track progress subscribe to https://github.com/OctopusDeploy/Issues/issues/4159
The Workers (https://github.com/OctopusDeploy/Issues/issues/4158) feature is related and covers some of the use cases described in the comments.
There could be a few options for this. Once per deployment for this exact case which could be ran on the Octopus Server itself. Though there is another option once per role where a script might get ran once on a database server or once on a web server. Ideally both options would be great as sometimes your Octopus server can only talk to the tentacles via 10933 and not via SQL or file shares.
-
225 votes
Thanks for the suggestion and for voting everyone. I’d like to get feedback on where we should go with this.
There are a few things in Octopus that already help with this – first, it’s possible to package your NUnit tests and run them as part of a package test (we do this ourselves), or to write a PowerShell step that pings your website to see if it is online. So the actual process of performing the tests is pretty easy. Do we need to write more blog posts/documentation to show how it can be done?
The next part is viewing the test results – in Octopus 2.0 you can “attach” files to a deployment via PowerShell which are then uploaded and available on the deployment page.
Viewing NUnit results XML isn’t that nice though, so I guess it would be nice to be able to render those NUnit test…
This would be great if we could upgrade from the WebUI. Similar to how some other windows packages do it like PRTG.