1452 results found
-
Grouping variables in Octopus UI
As a project leader I should be able to group variables on Octopus UI. This can be just logical separation.
This solve the problem with linked variables and help mange them.
For example It could collapse elements that are in structure - for example: db.username and db.password can be collapse as elements of root db or by labeling variables and then can be filtered by using specific label, for example - db.
4 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 -
TeamCity plugin agentless deployment
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.
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 -
Calculate estimated completion time on the server
Currently the estimated completion time is displayed in the Octopus UI. If I'm understanding the response I got on the support forms correctly that value is calculated in the client and not pulled from the server. It would be really useful that that value was calculated on the server and the estimated completion time was exposed as an Octopus variable.
https://help.octopus.com/t/get-estimated-completion-time-programmatically/273752 votes -
Built-in Azure App Service/Function Restart
I find that deployments to Azure Functions and standard app services will occasionally fail due to files being locked. This usually requires stopping the app service, re-running the deployment, and then restarting the function or app.
This can be scripted with Powershell, but since this is such a common scenario, I’d love a checkbox built into the Azure App Service step that provides this ability. Something like “Stop App Service prior to deployment and restart after deployment”.
3 votes -
Add Deployments link to Worker View
Add Deployments link to Worker View like what exists for deployment targets
Deployment target link path example: /app#/Spaces-1/infrastructure/machines/Machines-xxxx/deployments
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 -
Expose a generic OpenID Connect authentication provider
Octopus Server already has a lot of oAuth/OpenID integrations built in (AzureAD, Okta, Google Apps etc) but all of them are provider-specific. It would be great to have a generic authentication provider for third-party identity servers (such as Keycloak) to expand on this even further. Considering all of the current implementations are already based on a common class (https://github.com/OctopusDeploy/OpenIDConnectAuthenticationProviders) I imagine this shouldn't require much work. Although generic provider could expose more customization on how to extract user information from ID token, for example. We are using AzureAD integration to cover this for now (Keycloak integration) and it…
3 votes -
Please support deployment to Azure Cloud Sevice (Extended Support) targets
Microsoft opened up a preview for ARM base Azure Cloud Service, which is probably hinting on them moving away from a Classic cloud service deployment model:
https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/overview
Please add support for this type of targets.14 votes -
Show ProjectId or SlugId in Project settings
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-app1 vote -
Upload artifacts via UI
Please add support for uploading artifacts also via the user interface.
Uploading reports/approval documents or other files to a release is currently not possible via an upload button. We have to do a workaround using a script that uploads files from a specific folder or using the API to attach files to a release.
Especially during Octopus approval steps people need to upload documents.
14 votes -
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
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”.
1 vote -
Deployment Email Preferences by User
Allow each individual determine what deployment emails they want to receive. Users on multiple teams, or large deployment teams, are bombarded with hundreds emails a day. Giving the user the ability to tell the system they only want to receive failures, or no emails at all, would provide a better user experience. Alternatively, if this is not possible, allowing the system to have a single designated email for deployment notifications. This would allow the users to designate something like a Teams Channel to receive the notifications, and cut down on the amount of emails being sent in general.
12 votes -
Allow variable set assignment through variable set
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.
1 vote -
I need to Set a Project variable from a PowerShell step so that i can use the variable in an arm template parameter file as a substitution
I need a step A that set a project level variable #{COLOUR} from powershell and/or bash such that when I run an arm template step within the same deployment the parameter file correctly substitutes the value of #(colour} during the arm template deploy.
1 vote -
Add support for Keyfactor (Security and SSL) Certificate management
We use keyfactor (https://www.keyfactor.com/platform/certificate-lifecycle-automation/) for Certificate lifecycle Automation. It would be great if Octopus could integrate with this keyfactor to allow for issuance, renewal, inventory, import and storage of new certificates.
1 vote -
Add tenant tag support to runbook scheduling
Instead of only allowing explicit tenant selection, add the ability to select the tenants to execute the runbook for by their tenant tags when adding an new scheduled trigger.
10 votes
- Don't see your idea?