Sorry if this has already been discussed.
I was creating some powershell modules and I noticed there is no option to set dependencies on other modules.
This would be great. Right now I am using the description to track the dependencies, but is not ideal.1 vote
Currently, OtcoPack considers a project a web application if a web.config file is found in its root. My stand-alone ServiceStack service project needs to have such a file when working with Razor support to enable intellisense support in VS. The web.config is never deployed however but OctoPack now deploys the project in web-style. That is, copying all binaries to the 'bin' sub directory while they should really go into the root. See https://github.com/OctopusDeploy/OctoPack/blob/fa2bbe0ce4b489316e090bf35f4d7d74d1d3a92a/source/OctoPack.Tasks/CreateOctoPackPackage.cs#L4631 vote
For PowerShell scripts it would be good to know the deployment start time.
This way later scripts can report how long a deployment took up to that point.
(A current workaround is to have a script run at the start that sets a variable for later use by other steps)1 vote
- Don't see your idea?