1454 results found
-
There should be a "table" view of tenants.
There should be a "table" view of tenants. Table columns should be customizable and and there should be the ability to filter. This way I can easily modify variables.
Lets say I have a variable indicating which web server my app is assigned to. And I get a new web server. I could look at this table, sort or filter on the web_server variable and assign tenants/apps to the new webserver.
1 vote -
Add restrictions to prompted variables.
I have a prompted variable to ask the deployer to enter a ticket number. If they enter anything other than a number my automation breaks. So I would like to restrict the user input to being only a number.
2 votes -
Github app integration
It would be very helpful if you provided an octopus github app in the github marketplace as a way to auth when using github feed/github credentials.
Azure Devops and Terraform cloud currently provide this functionality and it is very helpful as it acts as an organisation service account rather than any 1 individuals account.
Currently if I create a PAT token for octo to use and then I leave the company that puts the other development teams in a bit of trouble, not to mention the security implication of any other user in octo being able to act as me.
…
13 votes -
Container image name variables
The ability to use variables exists in so many different places when setting up Kubernetes deployments, but one place I would think would make the most sense is the container image name.
When creating step templates, I found this one field a barrier from allowing me to use the templates because we use that image name for checking logs for various debugging.
2 votes -
Users with a scoped Tenant Manager role should have created tenants added to their role scope
Currently if I have a user or team that is assigned the Tenant Manager role that is scoped to specific tenants they are unable to view any of the tenants they create. Instead they could create the tenant but would then need someone to add the new tenant to the role scope
1 vote -
Support opentelemetry exporters
Both TeamCity and Jenkins have plugins that allow exporting opentelemetry data to any collector service supporting the OTLP protocol. It would be nice if Octopus Deploy also supported this as well, so we could get a full picture of the pipeline, and have metrics on time to deployment from commit to deployment.
2 votes -
Basic ANSI escape code support
Octopus is getting used more and more with Linux and CLI tools in the Linux ecosystem. Those tools often output ANSI codes, particularly for color.
Most of the time it's possible to turn the color output/ANSI codes off but the lack of color can make deployment logs much less readable.
Other tools in the CI/CD process do support basic ANSI codes (color), eg. Github Actions, Gitlab CI, Jenkins etc.
As an example of log output that is much more difficult to read without color: terraform plan
4 votes -
Support for GIT external feeds
We currently have files inside our git repository, in order to use them in Octopus, we have to create a build in jenkins just to zip it up and upload it to Octopus built in packages
It would be nice if we could just target my bitbucket repository instead of having to create jenkins builds, but more specifically GIT as that would support more than specific version control
1 vote -
Audio Notification of Successful / Failed Deployments from Browser Tab
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.
2 votes -
Add status filter to dashboard
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
2 votes -
starting up long running process holding off deployment process
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/10408It would be helpful if this functionality was added as out-of-box.
Thanks,
Ge
1 vote -
Support for AWS ECR as package feed for "Upgrade a Helm Chart" step
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.
1 vote -
ability to deploy AWS CloudFormation StackSets using Octopus Deploy Templates
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.
2 votes -
Order JSON before serializing
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.
1 vote -
Pause for manual intervention after every step for testing deployments/runbooks
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.
1 vote -
API to determine if worker is busy or idle
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.
1 vote -
Integrate PWA features and Desktop Notifications
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
1 vote -
Reorder Lifecycle Environments
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.
2 votes -
Permission Audit view
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.
1 vote -
Octo CLI Support on ARM
I would assume* it's mostly a case of adding
linux-arm64as 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.
6 votes
- Don't see your idea?