General

  1. Allow segregated package repositories

    In a lot of companies there is a clear separation between development packages and packages approved for production. Systems like Sonatype Nexus and Artifactory provide hugely powerful examples of these catering for a wide variety of requirements, but in most cases you need a simple set of requirements:
    * The ability to push packages to one (dev) repo
    * The ability to promote packages to another (prod) repo
    * The ability to force certain environments to pick from a certain repo

    This should be a relatively simple improvement to Octopus' very awesome but very simple package management capabilities.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Scoped Tenant Variable

    Here's the scenario:

    I have a web application that is being used across 12 countries.

    Every country has its own environment, databases.

    While the current Octopus allow us to create tenant variable like Alias, it is useful but when it comes to scope variable this feature is not there.

    Example: Tenant A has a different Database credential for UAT and PROD. Currently the workaround is to create 2 tenant variable, like UAT Database, PROD Database.

    It would be useful to have this scoped as well.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Define Manual intervention on an Environment

    I'd like to assign a manual intervention, or "Approval gate", at the environment level, independent of project.

    We have many projects that can be deployed to our environments. The lifecycles these projects can deploy to have a mix of Dev, CI, Test and Production environments. Some important environments require approval before anything can be deployed to them (e.g. QA, PreProd, Production).

    At the moment I have to add manual intervention steps to every project that could be deployed to those environments. I also have to make the intervention steps are conditional based on the environments they're going to (i.e. I…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow multiple version of 'kubectl'

    Currently Ocotpus only allows for one version of 'kubectl' to be added to the Octopus server. This means that all clusters targeted by Octopus must be running the same version of Kubernetes.

    It would add greater flexibility if we could add multiple versions of 'kubectl' and then choose which version to use within the Kubernetes deployment target.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. New Release Available could take admin to release compare

    As an Octopus Deploy administrator,

    I want to see the changes that would be in my specific upgrade in a single action,

    So that I can be more quickly informed of what changes will occur on upgrade.

    Basically looking for a quick link to this: https://octopus.com/downloads/compare?from=2019.2.4&to=2019.2.7

    As is stands, both of the values in the URL above are visible in the Octopus Deploy UI (relatively close to each other)

    Under

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Deployment Pipeline as Code

    I would like to see the "pipeline as code approach" applied to projects. The main idea is to be possible to define the process of a project using a yml file in a source code repository or package.

    155 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  7. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add Auto-Logout Timeout for Users

    As an administrator of our Octopus server I'd like to assign auto-logout interval for our users after a period of inactivity.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  9. Specify Service Name in Ingress Host Rule

    Currently, when creating an Ingress Host Rule, you can only specify the "Path" and the "Service port". The Service Name appears to be calculated for you. Why not let the user specify the name?

    One use case where providing the Service Name is critical is when using Ingress Annotations for the AWS ALB Ingress. An action annotation can be provided on the Ingress to tell the ALB Ingress Controller to create a specific action on the ALB. For example, an SSL redirect action. The annotation must be named "alb.ingress.kubernetes.io/actions.my-custom-action-name". Then in the host rule you specify the desired path (for…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Display more than 3 releases in overview

    Hi,

    The overview page seems to show a variable amount of releases. On one project it is showing 4, where only the oldest and newest deployments were pushed to prod. On another project it is only showing 3, again where the oldest and newest were to production.

    Could we simplify this and just have it show a paginated list of all the releases? You could then use the filters to filter the rows down (rather than columns as it does now, which isn't a filter if we're honest!).

    By doing this it will make this screen much more usable in…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow Scheduled Deployment Triggers to not re-deploy if targets are up to date

    Currently, the Scheduled Triggers option allows setting a time to deploy, and even includes examples in the documentation for "nightly deployments." The downside currently is that it will re-deploy every single night, even if the environment was already successfully deployed to.

    It would be nice to add an option to only deploy if the environment / targets need it done. This would allow for a real nightly promotion without excess deployments and logs.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Verify a user's database permissions prior to attempting the database upgrade

    If a user runs an Octopus Deploy installer and has some of the permissions necessary to upgrade the database, but not all, the database can be left in a broken state. Verifying all the permissions are correct before making any changes would prevent this broken state, which is most likely to occur by accident.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. new user role\s

    Would it be possible to introduce a new user role\s for adding\editing\removing steps from a process?

    We would like developers to be able to add a new step but not delete or edit existing steps.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Expand All button in Task Log

    In Task Log screen, we need to click on "+" button to expand the sections for each section. A "Expand All" button would be useful when you want to expand all sections at once but do not want the verbosity in Raw tab.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support the repository attribute in package metadata

    Hello,

    OctoPack / Octo.exe currently does not support the latest nuget XSD spec, and fails to run when newer elements are used in the nuspec:

    Repro steps:


    1. Create a new nuspec file with all the defaults and inside it add a repository element inside the metadata element. Example:

    ```xml
    <?xml version="1.0" encoding="utf-8"?>
    <package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>

    &lt;repository type=&quot;git&quot; url=&quot;<a rel="nofollow noreferrer" href="https://github.com/user/repo&quot">https://github.com/user/repo&quot</a>; /&gt;
    

    </metadata>
    </package>
    ```


    1. Run OctoPack or Octo.exe with the pack command, and the following error will be shown:


    error OCTONUGET: The element &#39;metadata&#39; in namespace &#39;<a rel="nofollow noreferrer" href="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd&#39">http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd&#39</a>; has invalid child element &#39;repository&#39; in namespace

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Highlight the variable Snapshot difference while updating the release snapshot

    Whenever there is a change in the variable after the creation of the release, we used to get warning saying "Release Snapshot has been changed". But we do have only one option to update the entire release without knowing what has been changed. It would be great if you have any way to find/highlight the variables and their values that will be updated when I click "Update Variables" in the release Snapshot section. It will minimize the risk when it's comes to updating the snapshots for production deployment and it will give a transparent view of what changes are done…

    78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add variables substitution capabilities

    We keep our deployment configurations in octopus variables and use json substitution the replace them on deploy time

    This could be improved in a few ways:


    • Use the json variables substitution feature on other step templates than deploy a package (for example: run a script)

    • have to ability to substitute also yml files

    • give a variable a null value, the only option now is tho give him empty string, which influence the code.

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Obfuscate sensitive variables in deployment log in variable substitution

    We're using various steps for deployment ('Deploy a package', 'Deploy to IIS') which both have variable substitution options to substitute variables in Web.config/App.config.

    During deployment, i've noticed that these substitutions are logged. However, sometimes i see that our sensitive variables are being logged here at 'verbose' level. Other sensitive (and also non-sensitive) variables are obfuscated.

    It seems that the deployment process decides by itself based on the name of the variable. In my opinion, the sensitive option of the variabel should be considered here as well.

    An example of what we've got currently:
    We've got an appsetting in our app.config,…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Filter Environments shown in each Project Group on the Dashboard

    Filter the environments show in each project group on the dashboard. Only environments included in the lifecycles/channels for each project in the project group should be shown.

    We have many environments but most are only used by a few project groups. Some project groups only deploy to a single environment. This requires us to horizontally scroll far to the right past environments which aren't capable of being deployed to in order to see what is deployed.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Terraform support for SSH Workers

    Currently the built in terraform steps only support Windows workers. It would be good if the steps were platform agnostic and able to run on any worker.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base