General

  1. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. Support creation of releases in child projects during "Deploy a Release" step

    The new "Deploy a Release" step is great! However, it was unclear to me at the time of setting up the steps that the "Deploy a Release" step does not actually support creation of a release before deployment--the release must already be created in the child projects before deploying.

    While this step is definitely headed in the right direction, in my opinion, I would think this feature would be even more useful if it also supported the ability to create a release in the child project(s) before deploying.

    The package versions are already supplied to the projects when creating the…

    19 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. Version rollback, or viewing of previous versions in Step Templates

    Hi OctoDeployers! My team have been working on standardising a lot of the work we do in Octopus, and its great that the step template function allows us to create and edit standardised steps, and then roll them out to our projects.

    One challenge this has presented however, is that if you introduce a defect when updating the version of the step template, there isn’t a way of:

    Seeing the previous version of the step template to confirm your changes
    The ability to roll back to a previous version of the step template.
    You can perform some of this functionality…

    9 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 →
  9. Allow deployment to Google Storage buckets (without gsutil)

    We serve some of our content from Google Storage Buckets - its nice and simple and avoids the cost of running VMs
    However, we have to write post deployment scripts that run gsutil in order to get our "apps" into the bucket
    Would be great if this was supported natively in Octopus Deploy

    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 →
  10. rpm

    support RPM package format for linux. specifically, (a) deploy RPM packages as-is (via native commands such as rpm, zypper, yum, etc.), and (b) query rpm database so that deployment status (i.e. current version) for any tentacle is kept in sync with reality (i.e. don't just assume that last version deployed from Octopus is what is currently deployed)

    7 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 →
  11. Tentacleless deployments using WinRM

    Now that Octopus Deploy can do deployments via SSH, it seems like it would be fairly simply to implement the ability to do deployments by connecting over Windows Remote Management (WinRM).
    Agentless deployments is a selling point used by other deployment tools, and now that Octopus Deploy can do "agentless" deploys via ssh, it would make sense to enable the same support for Windows machines as well using native Windows functionality.

    This would provide several potential advantages depending on the deployment infrastructure:
    - No service needs to be running on each deployment machine
    - No additional firewall port needs to…

    18 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. Deselect Tenants under Preview and customize

    When deploying; If selecting "Include all applicable Tenants", and there is a issue with one of the included tenants you have to deselect all, and add them one by one.

    I suggest that when "Include all applicable Tenants" is clicked, the possibility to deselect a specific under tenant under 'Preview and customize' tab would be much wiser.

    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 →
  13. Add Let's Encrypt support to the Certificates Library functionality

    I love the Let's Encrypt integration with the OD server. Setting up SSL for the server is so simple, and I don't even have to worry about renewals as this is taken care of for me.

    Now imagine this same functionality for all of your IIS sites.

    This is how I envision it could work

    - I go to Library > Certificates > Add certificate
    - I'm given the option of importing a cert (i.e. the current functionality), or I can chose to use Let's Encrypt
    - After picking Let's Encrypt, I'm prompted for a bit of info- domain, email…

    68 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. Allow configuration transforms for JSON files

    Currently the Configuration Transforms runs configuration file transforms on XML formatted config files.

    It would be useful to enable config transforms on JSON files as well, e.g. an appsettings.json file.

    25 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. import variables from json

    Ability to import project variables from a JSON file under the Project page.

    54 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 ability to loop a deploy step where multiple roles and role scoped variables are present

    Have a scenario where I need to deploy the same package multiple times **on the same set of servers** under different custom directories and different IIS web applications. There are role scoped variables which get picked up for custom installation directory and also appsettings.

    I understand that the documentation under https://octopus.com/docs/key-concepts/machine-roles clearly states:

    "This means that the step will only execute on Tentacles with at least one of those roles. This does not mean that if the step is scoped to multiple roles that it will run for each role. Instead it will run that step for all machines that…

    44 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 →
  17. Support deployment of Azure Function projects

    Support deployment of Azure Function projects

    192 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 →
  18. Add option to run Powershell script via -Verb runAs (i.e. right click, "Run as Administrator".)

    We ran into this problem because as a part of our deployment process, we need to stop a service (which isn't a part of our deployment), clear a cached file that the service was holding onto (which IS a part of our deployment), and then restart the service.

    Even though the Octopus tentacle has admin rights, and can start/stop a service via the control panel (i.e. log on as the Tentacle user, open the Services cmdlet, and you can start/stop services), to do so via a *Powershell* script requires you to right click on it and selected 'Run as Administrator',…

    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 →
  19. Add tenant tag to project link on a tenant

    I would like to be able to add a tenant tag to a project link on a tenant. Our tenants have 2 projects associated with them QA and Dev. Currently when I use a tenant tag the QA tester using that tenant will get access to the feature the developer using that tenant gets. This will in most cases cause the deployment to fail because the QA tester for that tenant may be completely unrelated to the developers project.

    If I could put tags on a project link it would allow me to say the developer using tenant 25 gets…

    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 →
  20. Support Required Variables

    It would be great if my deployment failed if a variable was not available in a particular environment. Currently I place a PreDeploy.ps1 with checks for particular variables (not empty) and I'm wondering if there could be a better experience for specifying that certain (or all) variables must be provided if they are used from PowerShell or elsewhere. We've had issues where our deployment went green but a variable was missing in a particular environment.

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

Feedback and Knowledge Base