Generally, once a deployment is triggered I tend to change browser tab and continue with other work. Sometimes, I miss a failed deployment due to continuing with work and assuming everything has been successful. It would be great to have a sound that is triggered from the browser tab when a successful or failed deployment has happened. It would really help me cut the feedback look and notify parties of success / failure.

When a deployment has failed, it shows on a tenanted dashboard as the latest release, when I'm wanting to know which version was last deployed/currently active (our deployments rollback if unsuccessful), but right now there's no way on showing only success deployments.

It would be a great feature for this to be one of the Advanced Filters options.

Also, maybe as a side and could be a bug, that latest release number, even if failed, actually shows up as the current released version when doing a multi deployment i.e. using the Deploy To window

We've had multiple teams running into this problem in their deployments/runbooks.

When starting up a long running process (i.e. Start-Process Some.exe), Octopus deployment step never completes until the process on remote target ends.

Currently, the recommended workaround is wrapping the server process in a Windows scheduled task.

As described here:
https://help.octopus.com/t/long-running-console-applications/10408

It would be helpful if this functionality was added as out-of-box.

Thanks,

Ge

I have successfully set up an AWS ECR package feed and can find the Helm charts I have pushed there when I test the feed. However, ECR feeds do not show in the dropdown for package source in the Helm step.

I also tried using the oci:// address of the ECR as a Helm Feed, but receive the message "Only 'http' and 'https' schemes are allowed. (Parameter 'requestUri’).”

It would be great to be able to use at least one of these as a source for the chart.

Use Case: we have used CloudFormation StackSets to deploy common resources to several accounts that are part of the same Org in AWS.

We are now developing a project in Octopus Deploy to deploy these resources and would like to have the ability to deploy CloudFormation StackSets instead of single Stack.

The audit log is made significantly more difficult to use as edits to a value (in my case, a variable in a variable set, but this likely applies to any array of objects) moves the updated value to the end of the array (deleting and recreating, I would guess).

Ordering the JSON by id before serialising it would make the audit log significantly easier to read, and thus more useful.

A thought just occurred to me. Being able to pause for manual intervention after every step could be an option in the advanced settings of a deployment or runbook execution. This would assist in testing runbooks/deployment processes meaning you can check state at each stage. Maybe not a manual intervention, perhaps just a "next step" or "proceed" button or similar.

in order to determine if a worker can safely be terminated it would be good to have a rest api for this. The closest thing we get today is this script https://github.com/OctopusDeploy/OctopusDeploy-Api/blob/master/REST/PowerShell/Workers/GetWorkersUsedInTasks.ps1 which uses string matching in task log output - very rudimentary, and with tons of failure modes.

I know there's a "worker lease" table, a rest api endpoint covering that table would be great.

It would be nice if we could install our octopus instances as a PWA and integrate desktop notifications for things like deployment events, failures, and possibly manual steps needing approval

Provide ability to reorder target environments in a lifecycle, just like you can reorder steps in a process. Currently, we have to delete all subsequent environments when adding a new environment, then re-add all those deleted environments. Being able to simply reorder these in the UI seems a quick win.

We were recently audited, and asked to provide screenshots showing which users had "DeploymentCreate" permissions.

please add a new Permissions Audit screen that allows selecting one or more permissions and spaces, and then showing all users who have that permission.

I would assume* it's mostly a case of adding linux-arm64 as a runtime argument.

Octopus is the /only/ thing that's preventing me from moving my TeamCity agents to Amazon t4g instances. I can accept that the plugin for TC maybe more involved but can we atleast get a build of the cli supporting ARM so that I can manually post manually to Octopus.

Octopus-API/Octopus-Client works on Project Id or SlugId, However, there is no way to see these values in the web app. It would be intuitive if they are included in the project settings (albeit read-only) for usage across Octopus tools.

Usage:
https://help.octopus.com/t/can-we-see-the-project-id-in-octopus-web-app

when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run.

idk what you call this icon with the orange square and white lightning bolt

but when the lifecycle is in this state, the save button really means, “go ahead and run”.

When running a deployment and showing its status, specially on longer deployments, the TeamCity agents will be on hold for the duration of the task. On deployments where guided interruption is enabled this is specially taxing on agent licenses.

Since 2020.2.4 TeamCity has introduced agentless builds, where an agent can be detached during the execution of a build, and requires the running process to call TC back via api and inform the build has finished.

This is currently not possible on the plugin and, using powershell, I've found hard to establish the whole deployment status at X point in time.

This would be useful for replacing values especially in the values-file from Chart Package or Additional Package. With this feature we don't need to have variable replacement syntax in our source-files.

Currently when a new variable set is created, it has to be included in projects individually. When there are many projects that should include the variable set, it would be much more convenient if the set could be included in projects via the 'usage' tab.