Adam
My feedback
-
41 votes
Adam supported this idea ·
-
231 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…
-
639 votes
Work has begin on providing a tool to evaluate variables before deployment
https://github.com/OctopusDeploy/Issues/issues/4221At the moment we don’t have further plans to apply config transforms before a release but this should help solve the bigger question of “what will my all my variable values actually be at run time”
An error occurred while saving the comment -
141 votes
An error occurred while saving the comment Adam commented
I would suggest checking out the Microsoft bot framework: https://dev.botframework.com/
It would allow you to integrate with several sources, including slack and teams, from one code base and seamlessly integrate natural language into the interface if desired. We built one recently for our customers and as a .net development shop it was a dream.
Adam supported this idea ·
"- Ability to preview the evaluated variables for an environment/step/machine/tenant combo"
I would love to see this available from the API. That would enable us to speed up our migration considerably. We have scripts to parse our existing configurations by env and add to octo api, but they dont have the ability to check env specific values across library sets.
"we are thinking of either creating a tool,"
I would expect to see this as a new command in octo.exe