Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Amazon ECR supports pushing Open Container Initiative (OCI) artefacts to repositories. This includes Helm charts.

    However, Octopus does not support pulling Helm charts from OCI sources.

    I'd like to see this support added.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Hi team,

    Our deployment usually happen in a short off business hour window. However, the Calamari update by default will happen on deployment time and it can sometimes take half hour to finish. Admittedly, we can workaround this by manual update or wrote and schedule our mock deployment. They all are not elegant enough. Please consider adding this feature in.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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/27375

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. We have a case where we want to have a runbook to handle restoring Databases from different sources to different targets.

    To handle this we have a form sheet with prompted variables.

    But we also have the case where we want to do a restore daily to one of our databases. To do this we would need to be able set a trigger and also to set the prompted variables within that trigger.

    I understand this can be done through the API currently but would rather see this in the UI.

    My workaround for now is to duplicate the runbook…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. https://help.octopus.com/t/feature-request-variable-sets-spanning-spaces/26948/4

    We have multiple teams and have so far been avoiding spaces because we have no way that we know of to share variables and scripts between teams in different spaces.

    We have a lot of shared configuration that we wants accessible by all and with only one source of truth. For example, we have many apps that need to add whitelisting for our build/deploy servers. We store that ip whitelist in an octo variable set so all project can access it. If I need to alter that whitelist I can be confident that if I change the values in…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?