General

  1. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. When deploying project containing Deploy Release step, allow previewing steps and excluding machines from child deployments

    Currently when deploying a project containing one or more Deploy Release steps (https://octopus.com/docs/deployment-process/coordinating-multiple-projects/deploy-release-step), there is no ability to preview the deployment steps that will be executed in the child deployment, nor the ability to exclude machines from the child deployment.

    It would be nice to surface this information on the create-deployment page of the parent project.

    35 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 →
  6. terraform

    Terraform step templates for Azure deploys. Currently only AWS is supported in Octopus included step templates. It seems like an easy addition to the existing functionality

    12 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 →
  7. Rolling deployment parallelism per role

    We have an service environment right now that consists of two data centers that each contains 3 servers that host the services. These services hosts host 100+ services each and each server is hosting exactly one instance of each service; so they are in effect mirrored.

    When we deploy to these servers, we do it one data center at a time. Since there are so many services per server, we can’t just remove the server from the load balancer. Also since we do round robin load balancing and want to have zero downtime and keep consistency in our responses during…

    3 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. Display channel description when creating a new release

    The selected channel's description should be displayed when creating a new release, otherwise a user may miss important information that is not fully conveyed by the channel's name. Currently a user would have to navigate to the separate channels tab to see this, which breaks the UI flow and which they may not necessarily do.

    5 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. Support multi-package deploy steps

    Allow package deploy steps to select multiple packages that are deployed in the selected order (with the ability to change the order). We have a website where we deploy a clean copy of a vendors files (makes upgrades easier), then we overlay different 3rd party modules and our solution into the same folder. These packages together create a whole website.

    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 →
  10. Deploy to Service Fabric

    The 'Deploy to Service Fabric' process does not provide all the available security mode options available in Service Fabric, we are doing a POC around an on-premise SF cluster using a gMSA which the Fabric will run under the context of and Windows Identities to allow client-to-node communication. the option for using Windows Credentials (in this case it would be the Windows Service Account which Octopus is running under the context of) to connect to the cluster is not available! i.e.

    Connect-ServiceFabricCluster -ConnectionEndpoint <cluster-domain-name | server hostname>:19000 -WindowsCredential

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Deployment features  ·  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.

    15 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. Make variable list usable for configuring IIS bindings.

    When adding a binding to IIS in Octopus, you can only use seperate variable. Every binding needs a new variable. Some of our deployments have over 50 bindings. We create each binding separate. If we use a variable list only the last item of the list end up in de IIS binding. It would help us a lot if we could ad three generic bindings (Test, Acceptation, Production), en in the bindings use a variable list, containing all the IIS bindings.

    51 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 →
  13. Add a Deploy Feature to configure file system permissions

    When we deploy a website we need to grant the user running the IIS application pool access to the deployment directory. Similarly, when deploying a windows service, we need to grant the user running the service filesystem permissions to the deployment directory.

    It would be great to add a Feature to "Deploy to IIS" and "Deploy to a Windows Service" that would set the file system permissions for the user associated with the App Pool or Windows Service.

    We like to set file system permissions during deployments so we have one less environment-specific issue to worry about (ex: oops, the…

    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. Deployment of more than one certificate in one step

    We need to put multiple certificates into the trusted people-store, and number of certificates must be configurable in one step.

    Tried putting multiple certificates into the same scope for a variable, that only published the first one.

    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. Proget Universal Package Format Support

    It would be great if Ocotpus could support as an external package feed:

    https://inedo.com/support/documentation/upack/tools-and-libraries/upack-cli

    This is because using `upack` cross platform cli it is easy to create and publish packages containing applications, to a proget universal format feed. Octopus has an in built zip file feed, but we want to standardise our artifacts feeds to proget as it is purpose built for feed management.

    Nuget cli is not good at packaging up for example a single exe to push somewhere - like an apk file - because you first have to generae a nuspec file, and then you have to…

    7 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. Change Type-Click-Repeat Dropdowns to Type-Click-Checkbox dropdowns

    Sometimes there are 8 or 16 instances I need to manually deploy to because of a bad deployment or some other reason. For various reasons, I have to use the UI to do this and I may need to include or exclude 16 instances.

    It can be a pain to have to type in the checkbox, click on the instance, and then repeat. It would be nice if I can see a dropdown with checkboxes so I can tick them without the dropdown going away each time.

    Here is a good example:

    https://codepen.io/elmahdim/pen/hlmri

    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 →
  17. Deploy Docker Containers to Service Fabric

    Presently you only support the old and standard way of deploying to Service Fabric but not docker containers.
    Adding this as a possibility would be cool, and would also enable people to migrate their solutions into containers, which could, in turn, be used in migrating to Service Fabric Mesh in the future if needed. (Only supports container deployments and is currently in public preview)

    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 →
  18. Allow Package variable type for step template

    I would like to create a step template to run some Postman test suite. For this I thought to pass the test files and environment files to the package. Extract the package somewhere, run powershell in the extracted package and call newman (command line runner for postman).

    But I can't add a 'Package variable' to a step template (like for a deployment step.

    It would be nice to have this as variable for a step template. In the process, you would then get a dropdown with the available packages, and a dropdown with the possible packagefeeds. The script would then…

    9 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 →
  19. Add additional output variables to Terraform Plan step stating if changes required

    Terraform plan step currently only outputs "TerraformPlanOutput", however this always has values and is not easy to run conditional steps upon.

    When running terraform with the --detailed-exitcode (https://www.terraform.io/docs/commands/plan.html#detailed-exitcode), you're able to determine if there is a change required.

    It'd be good to output this as an output variable.

    Specifically, my use case is that if there are terraform changes required I want to require manual intervention (and send a slack message) for the plan to be approved. If no changes required then don't require intervention, don't run plan, dont send slack notification.

    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 →
  20. 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.

    22 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