General

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

    16 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. 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…

    8 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. 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 →
  4. 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 →
  5. 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 →
  6. 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…

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

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

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

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

    39 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 →
  10. 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 →
  11. Support deployment of Azure Function projects

    Support deployment of Azure Function projects

    180 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 →
  12. 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 →
  13. 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 →
  14. Complete the step even thought deployment was cancelled

    Sometimes, developers cancel the onging release deployment. In some cases, the deployment is interrupted in the middle of step execution and changes cannot be reverted easily afterwords. For example, there is one step to restore the database and run some cleaning sql queries. The deployment was cancelled right in the middle when powershell script turned the database in a single user mode and started to restore it. Deployment was cancelled and the database was left in that state. It was required manual intervention to login and revert changes.

    My idea is to add possibility to mark the step as atomic…

    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. Allow for specific files that were added by OctoPackEnforceAddingFiles, to be excluded in package

    I cannot not use /p:OctoPackEnforceAddingFiles=True with MSBuild. This parameter is absolutely indispensable. It is not even an option.

    However I do not want all the files in the build to be included in the package.

    The nuspec file and the exclusions ability therein does not allow to exclude files that were added by OctoPackEnforceAddingFiles.

    The effect of this is that I can’t use one of the best features of Octo : deploying to IIS.

    Because of a few files that I can’t exclude from the build, I need to deploy to a folder, remove the files that I want, and…

    30 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. Allow new IIS step to just create IIS resources without necessarily deploying a package

    Currently the new IIS step (introduced in 3.4.7) allows you to create Sites, Apps and Virtual directories, but you always have to deploy a package.

    It might be useful for some users to be able to take advantage of the IIS functionalities, without having a deploy a package.

    Source: http://help.octopusdeploy.com/discussions/questions/9702

    231 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Apply rention policy to custom install directories

    When deleting a release from a target machine according to retention policy, option to also delete the custom directory (and its contents) that release was installed to. This is for custom install directories that are named with {Octopus.Release.Number} as part of the name.

    13 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 the use of C# script (.csx) using .NET Core

    ScriptCS will no longer be supported under .NET Core.

    Please enable support for dotnet-script (https://github.com/filipw/dotnet-script) so that C# scripts can be executed under .NET Core

    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 →
  19. Allow named variable sets to be defined at the Project Group level and optionally shared between all projects in that group

    Within a project group it would be good to be able to define sets of variables (like in the library) which can be optionally shared between any project in the same project group. This will allow variables to be shared between similar projects and will allow easy grouping of related variables.

    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 →
  20. Allow cloning of tenants

    It should be possible to clone a tenant including it's current configuration in a similar way to that you can clone whole projects.
    Tenants tend to be similarly configured with only minor changes to each one so it would save time rather than having to configure each one from scratch.

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

Feedback and Knowledge Base