Just like in the UI, it might be useful for some users to update releases from Octo.exe for things like:
- Package(s) Version(s)
- Release Notes
- Release Version
Worth considering if it should also update the Release's variables (in the UI that functionality is set in a dedicated button)
Possible commands could be:
Octo.exe Create-Release --updateExisting1 vote
Recently discovered the quick navigation shortcut in TeamCity and use it constantly! Would love to see this feature implemented in Octopus Deploy as well, including the type ahead functionality and arrow keys support, for quick navigation.1 vote
1) Highlight channel name (make it bold and/or different color) on the project's overview page.
2) Add channel name to deployment status on Dashboard (next to release number and date).1 vote
When setting up an external Package Feed we'd like to be able to pin the SSL certificate thumbprint of the external feed to make it even more unlikely we'd accidentally fetch packages from a source through DNS poisoning, redirect or or man-in-the-middle attack.1 vote
Octopus was born out of a desire to help .NET developers, why not have someone try this...
Create a custom project type for Visual Studio for Octopus Projects that incorporate these json files.
That would allow a GUI that can easily and ready be documented, it would allow us to integrate them with our source control tools, and more closely align our Octopus projects with our work.
I wish I had those skills, I'm more of a DBA/BI Developer, but I think this idea could work, thoughts?
There does not seem to be a direct way of requesting more than one DeploymentProcess from the API. I am working on a tool that needs to determine all projects that have deployment processes that have steps with a specific TargetRole. As it is, I have to iterate over every project (hundreds of them in our case) and request each process individually to interrogate the step information. I would be better if I could paginate over the processes directly and only request the projects I care about.1 vote
It would be useful to be able to set up notifications after each step. In our case, specifically, we would like to notify Slack after each completed step.
I've seen the library script that you can use to add a step to a deployment process to notify Slack, but that would mean notifying Slack only after a deployment is complete. Some of our deployments take a long time and we would like to be able to follow their progress in Slack, i.e. get OctopusDeploy to notify Slack after each individual step.1 vote
Add support for Octopack Nuget so that MonoAndroid and Portable Libraries can be packed with Octopack.
Currently unable to install Octopack to portable library:
Could not install package 'OctoPack 3.0.44'. You are trying to install this package into a project that targets 'portable-net45 ....... (and so forth) ..1 vote
Would it be possible to update the releasenotesfile switch on octo.exe to allow for HTML files? My build server currently creates an html report for the releasenotes, which i would like to attached to the release via the "octo.exe -releasenotesfile" switch but it always displays an blank section. If I attach a plain text file is works, but I would like to be able to format the report.1 vote
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?