Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. The Octopus Deploy for JIRA plugin (currently Cloud only) is a nice feature, but a lot of companies use on-prem versions of JIRA. It would be nice to have a server version of the plugin that can be installed so we can properly integrate Octopus Deploy and JIRA, especially for the capturing and tracking release notes.

    3 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)
  2. atm we are working with multipule people on multipule projects without any common agreement about naming convention and categorys. the problem is wild growth of varibales. The more we use octopus the more we see overlap of commonly used values. if u want to merge is is dumb work copy pasting form one side to the other side.

    the feature i realy like to see is variable manager:
    - var set names are labels/category
    - filter option on labels/category
    - filter not used
    - overview where the variable is used in projects

    3 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)
  3. After using Octopus Deploy for the last 4 years. I love the product, but I hate using the API, The current octo.client pretty much mirrors the rest api and using it is cumbersome and clunky. We have gone down the path of 100% automation and because of it, we have run into edges of the api where we end up hard coding guids for variable identification into our code base. Our current path has lead us down trying to automate the setup of tenants and setting their variables. Its painful and we have spent a lot of hours trying to…

    3 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)
  4. Octopack can parse AssemblyVesion attributes to extract version information, which is great. This enabled me to control the version of the generated NuGetPackage at the time when I check in my project. I like that. My build server generates new packages for every commit to out repository (even though the version might now have changed). Therefore I would like to be able to append the build number to the package Id. This could be done using an OctoPack parameter "OctoPackBuildNumber"

    Example: AssemblyInfo.cs: [assembly: AssemblyVersion("3.5.0.1")]
    then the buildserver passes in: /OctoPackBuildNumber -build%build.number%

    Result:

    MyProject.3.5.0-build5551.nupkg

    3 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

    2 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. 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)
  6. It would be great to add multiple headers in octopus subscription payload requests. Atm, it looks to be limited to just one.

    Thanks to this, it would be possible to better control the logic through the application that rewrites/parse the payload and send to a specific webhook

    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)
  7. Allow the json payload used when setting up Subscriptions to be templated in the same way as config.
    If you could specify the json with embedded octopus variables you could integrate with many many other tools without the need to add a custom step at the end of each deployment. (eg. MS teams)

    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)
  8. Deployment trigger options are currently limited. It would be nice to trigger a deployment by executing Azure Function which would queue the request using Azure Service Bus. In this case Octopus Deploy would listen for a queue message to start a deployment.

    This solution would allow for various creative integrations within Azure.

    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)
  9. Can we please have support for the DNS-01 challenge type for LetsEncrypt. We don’t want to have to expose a server to the open internet just to validate a certificate domain. DNS-01 solves this by querying the DNS provider directly for the challeng token to ensure you own the domain in question.

    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)
  10. Currently, Variable Conditionals as documented here:
    https://octopus.com/docs/deployment-process/variables/variable-substitutions#VariableSubstitutionSyntax-Conditionalsconditionals

    Does not allow for evaluation of more than one condition, which makes the syntax really ugly and dificult to read when workaround/hacks are implemented to evaluate more than one condition...

    For example, currently only this is allowed:

    {if Octopus.Deployment.Tenant.Name == "PreProd"}prod#{else}uat#{/if}

    Make is easy to do OR/AND and evaluate more than one condition, like this for example:

    {if Octopus.Deployment.Tenant.Name == "PreProd" || Octopus.Deployment.Tenant.Name == "Production"}prod#{else}uat#{/if}

    To get an idea of the issues review this post (describes workaround for AND but OR is not possible so far!):

    https://help.octopus.com/t/run-condition-variables-two-conditions/1585

    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

    1 comment  ·  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)
  11. At present, all API keys for a user (service account user or 'real' user) do not have an expiry date.

    As a result, non-required API keys can potentially leave access open via this key.

    The suggestion would be to:
    - allow users to specify the duration of the API key/token
    - allow admins to specify the possible durations available to users/roles (e.g. administraters can stop users selecting 'unlimited' duration, and only allow 30, 60 or 90 days, for example)

    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)
  12. Using a virtual environment would be much more secure, and it would potentially give the opportunity for admins to modify the environment without changing the configuration on the servers directly.
    Also, it would give Octopus the ability to package Python as part of Calamari rather than the admins having to install Python on all the Tentacle servers.

    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)
  13. We would like to include build information (commits) from GitLab into our packages so that we can automate the release notes creation from packages.

    The https://octopus.com/docs/packaging-applications/build-servers#build-information page states that "The recommended way to supply the build information is to add the Build Information step" but there is no GitLab step.

    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)
  14. I'm working on code for a Terraform module for modifying Octopus Deploy configuration, and when we have variables with the type set to Sensitive (or IsSensitive=true), Octopus understandably does not return the value of the variable.

    However, this means it is impossible to determine if the value is set correctly.

    One workaround would be to provide a hash (even a salted hash) of the value when it is set. Then we could compare our hash against the hash in the API, and if they don't match then update the sensitive variable.

    E.g. A new field called ValueHash which is sha1(Name

    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

    1 comment  ·  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)
  15. I would like to register a webhook after a new environment is created or when a new release is created. I am currently auto creating environments when a new feature branch is created, but we do not have a great way to auto deploy new releases to the appropriate environment yet. We currently have to poll all the releases and inspect the release notes to determine if we should deploy the release to a specific environment. Having a webhook for a release creation will allow us to support our GitFlow workflow.

    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

    1 comment  ·  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)
  16. Currently octopack supports either msbuild override, AssemblyInformationalVersion, or AssemblyVersion and does so in a predefined way. It would be useful if this selection was customisable/controllable.
    E.g. If AssemblyInformationalVersion (which supports string) does not conform to a valid Major.Minor.Patch.Build scheme I would like to specify either AssemblyFileVersion or AssemblyVersion.

    I cannot specify the value of these to octopack via msbuild arguments because the version scheme itself is controlled/applied by a TFS pre-build script.

    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

    3 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)
  17. We use Azure DevOps and the Use Octopus CLI tool installer. Right now we hard code a version of the Octopus CLI (at Octopus' suggestion) to a known working version. This has caused two issues over the last three months where the CLI version wasn't compatible with the Server. Instead of us guessing at the correct CLI version, the server should suggest one.

    The server could respond in multiple ways, e.g.

    8.* => Install latest in major version.
    7.3.* => Install latest in major and minor version.
    8.0.1 => Install exact version.
    * => Install whatever is latest.

    This way…

    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  ·  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)
  18. Now that we can store git credentials in the library, we would like to use those centrally stored credentials for GitHub Repo feed settings as well.

    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  ·  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)
  19. Kubernetes likes to consume hashed values, e.g. for Ingress basic auth we need to provide a secret where the password is already hashed, e.g.: "admin:$apr1$QVF90yb6$JxGT0BWDpw0negAzDy3YT."

    This forces us to have two variables: one for the password and the second for its hash

    And that may become a problem in the future when we will update one and forget about another

    In an ideal world will be so nice to just add something like #{Password | Bcrypt} as a value for a Kubernetes secret

    Also, it is a good spot for other algorithms like Md5, Sha-X, ...

    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  ·  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)
  20. 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.

    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  ·  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?