General

  1. 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.

    34 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. option to Download / copy certificate files through Build Step

    We are able to manually download the certificates from octopus certificate store, it will be helpful to do the same in build step as sometimes we need to copy certificate files to the application servers.

    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. Move "Excluded Steps" above tenant selection.

    It's a hassle to scroll to exclude steps during a deployment particularly when your debugging a deployment and don't want to/can't disable steps.

    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 →
  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>
    <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…

    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 →
  16. Add repository retention feature for external feeds

    Add repository retention feature for external feeds. I'd like to be able to manage package retention on external feeds in the same way that they are managed for the internal feed automatically deleting unreleased packages after a number of days

    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 →
  17. Support freeze/blackout schedules for deployments

    With an increased release cadence, it would be nice of Octopus supported the idea of creating freeze/blackout calendars that would either (by setting) outright prevent deployments (possibly allowing with authorization by a particular team) or display a warning that the deployment is taking place during a freeze period.

    Ideally we would be able to associate these freeze calendars with projects or project groups, specify whether it is a warning when deploying or prevents deployment, and in the latter case which team or teams would be able to authorize bypassing the freeze.

    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 →
  18. Add a map of Azure App Settings as an Azure feature

    Add a deployment feature to the Azure Web App step that maps Azure's AppSettings and Connection Strings to Octopus variables. It was suggested to use a script to do this on your blog post (https://octopus.com/blog/azure-functions), but this would be much more valuable as a built-in feature since it is such a common scenario.

    I've uploaded an example image of what I imagine the UI would look like to: https://imgur.com/a/BwL4Tuh

    4 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. 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.

    6 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. Visual compare of variables between releases

    There seems to be no way of comparing variables between releases. Having this feature would give confidence that only expected variable changes make it into a release

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

Feedback and Knowledge Base