General

  1. 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 →
  2. Tenant (Project) variables UI improvement - toggle linked environments

    We have around 50 Tenant project variables that differ per each linked environment (Dev, Test, Uat, Stage, Prod)
    So imagine the current UI, we have to scroll down the list endlessly until we find the variable.
    Tenant variables UI improvement suggestion:
    1. Toggle linked environments project variables- meaning use accordion or panel widget for each linked environment, so when I click on one linked environment I would expect to see the Tenant Variables only for that linked environment. Currently all linked environments variables are displayed.
    app#/tenants/Tenants-61/variables?activeTab=projectVariables

    2. Add filtering / searching for project variables on the same page
    app#/tenants/Tenants-61/variables?activeTab=projectVariables

    4 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 →
  3. Add 'latest' option on Octo.exe -package overrides

    When using Octo.exe's --packageversion to specify a version for all packages, and then --package to override one package, it would be helpful if --package would let you specify 'latest'.

    Example:
    --packageversion 6 --package SomeSinglePackage:latest

    Currently if a script is sending --package SomeSinglePackage:2 and there is a new version, you have to remember to change the script to version 3.

    This scenario occurs when you are trying to release a specific version of your application, but one package is shared across many projects and won't have the same version number as the project being 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 →
  4. 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 →
  5. 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 →
  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.

    139 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. 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.

    14 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 →
  9. 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 →
  10. 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 →
  11. 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>
    <repository type="git" url="https://github.com/user/repo&quot; />
    </metadata>
    </package>
    ```

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

    ```
    error OCTONUGET: The element 'metadata' in namespace 'http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd'; has invalid child element 'repository' in…

    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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. Cleanup Application folder for versions that have no corresponding release any more

    We noticed that the automatic cleanup of C:\Octopus\Applications apparently does not cleanup versions where no corresponding release exists any more (e.g. because we only played around and afterwards deleted the release without manually cleanup up the C:\Octopus\Applications folder).

    It would be really cool if the cleanup would also cleanup versions for which there is no corresponding release.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow machine policies to be set for Azure WebApps

    I would like to be able to customize the Health Check of Azure WebApps deployment targets. For example I would expose an endpoint `/health` that must be queried on an ~hourly basis. In the case of a Tentacle this is possible using Machine Policies, but I can't assign one to a Azure WebApp deployment target.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Production Deployment Notification

    I would like to receive an email notification when a PRODUCTION deployment is taking place.

    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 →
  19. Tag AWS ECR (Elastic Container Registry) images from a feed with a deployment tag

    Amazon's ECR (Elastic Container Registry) is a docker-compatible registry that you can configure as a first-class package feed in Octopus. Part of the ECR product (in AWS) is to set up lifecycle policies so it can automatically delete old images (since it takes up space for each image). This is a similar feature that Octopus offers on its own built-in package registry, but the ECR is obviously an external registry so the purging has to managed by AWS (and no Octopus). But ECR has no way of knowing which images are used (so they won't get deleted), except if you…

    2 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 →
  20. Approval Role

    I'm not seeing things specifically, but it would be nice if there was a role which was Release Approval Only Role. To allow a certain set of users to just approval releases to go to the next environment in the life cycle.

    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 →
  • Don't see your idea?

Feedback and Knowledge Base