General

  1. Manage/edit variables in variable sets from the project level

    I would like to be able to manage variables in variable sets from both the variable set page and from the project level, when there are cases where I have included a variable set in my project. This will help reduce the back and forth navigation that is needed to make the necessary edits when I find I need to modify the variables that are in the set as I am maintaining my project.

    1 vote
    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 →
  2. Expand Variable Conditionals to include OR/AND statements

    Currently, Variable Conditionals as documented here:
    https://octopus.com/docs/deployment-process/variables/variable-substitutions#VariableSubstitutionSyntax-Conditionalsconditionals

    Does not allow for evaluation of more than one condition, which makes the syntax really ugly and dificult to read when workaround/hacks are implemented to evaluate more than one condition...

    For example, currently only this is allowed:

    {if Octopus.Deployment.Tenant.Name == "PreProd"}prod#{else}uat#{/if}

    Make is easy to do OR/AND and evaluate more than one condition, like this for example:

    {if Octopus.Deployment.Tenant.Name == "PreProd" || Octopus.Deployment.Tenant.Name == "Production"}prod#{else}uat#{/if}

    To get an idea of the issues review this post (describes workaround for AND but OR is not possible so far!):

    https://help.octopus.com/t/run-condition-variables-two-conditions/1585

    1 vote
    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 →
  3. Divide deployment targets between required and optional

    My environment has servers that sit in reserve and are only started when needed. A deployment right now consists of bringing these up, waiting, and pushing the deploy button, but this doesn't always go smoothly.

    Sometimes the Octopus service has a hiccup on boot, or AWS takes longer than usual. This gets reflected in releases that fail which leaves me with either running it multiple times and either explicitly including or excluding servers or stopping and starting an instance until it resolves.

    Being able to communicate to Octopus that as long as a core group of servers is communicative, the…

    2 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. Integrate Octopus with ServiceNow

    the ability to integrate ServiceNow form approve or change approve to trigger octopus deploy

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Deploy Release step should prevent picking releases from a different lifecycle

    When creating a deployment 'parent' that utilizes the "Deploy A Release" step 'child', it's possible to create a 'parent' release with a 'child' release version that uses a different lifecycle. When attempting to deploy, the following cryptic error is returned:

    The step failed: Activity <Child Step Name> on the Octopus Server failed with error 'The release has unresolved defects and cannot be deployed to this environment.
    Once you have corrected these problems you can try again.
    If the problem is related to a variable you will need to update the variables for this release or recreate the release for 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. Negative tenant tag condition for deployment steps

    Currently you can set a condition to a step so that it is only run on tenants with certain tenant tags.

    If I know want to run one step on tenants with a tag but not run a second step with a the same tenant tag (different configuration for these tenants) I have to use conditions field instead. This gives a very unclear overview of the process as it appears to that both step run on tenants with the tag.

    Ideal would be
    * Step A run on tenants with Tag A.
    * Step B run on all tenants except…

    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. View related infrastructure of a project

    When viewing the page, /app#/projects/--project_name--, add a navigation link called Infrastructure which when clicked shows all of the related infrastructure for roles for the project.

    I know this data can be viewed on another page, but it would be easier if I am already viewing the project to see where it is running without loosing focus on the project and needed to navigate to the infrastructure and filtering my roll.

    1 vote
    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 →
  8. Show the Project name on HTML Title instead of "Overview - Octopus Deploy"

    When you navigate to a project, you get to the Overview page as a start. When you open up many projects at once (cause a change triggered multiple CI for example, which should be deployed) all of them will show "Overview - Octopus Deploy" in the HTML title and as such it's also what's displayed on the browser tabs:

    You loose the ability to distinguish between these tabs. It also means that if you bookmark multiple projects then you'll have to change their title manually to have a valuable label for them. You have to click around them to figure…

    10 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 →
  9. Add an option to the IIS deploy step that, when checked, restarts the app pool

    As an Octopus project builder, I need an option on the IIS deploy step that will allow us to restart the app pool after the deployment of the new web application so that code changes within the application can take immediate effect when deploying.

    7 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 →
  10. Allow linking of the Enabled checkbox to a variable

    For various steps it would be nice to allow the "Enabled" checkbox to be linked to a variable. For example in the "Deploy to IIS" step template.

    This would work just like it does in the website bindings popup, each binding can be linked to a variable.

    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 →
  11. Add "Download latest version"-button to Octopus Manager GUI

    As a step towards automated upgrade of the Octopus Server (https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/3033637-upgrade-of-octopusserver-through-octopus), I'd suggest that you add a "Download latest version"-button in the server GUI. This would make the upgrade a lot faster, instead of having to navigate to the Octopus web site and find the latest version manually.

    3 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 →
  12. Scheduled deployments allow select release versions

    Hi,
    We would like to select certain release versions in the scheduled deployment triggers similar to how we create a new release and can select a release version
    Currently it doesn't seem to be possible and it uses only the latest release
    Hope this can added in the next Octopus release
    Thanks,
    KK

    16 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. Improved variable grouping in UI

    Hello!

    While working with variables in octopus I thought it would nice to “group” variables so that it’s easier to navigate. This would allow someone to organise and reason about the variables easier.

    Anyways, here goes:

    A.B.C[Foo] = 42
    A.B.C[Bar] = 3.14
    A.B.C[Foobar] = 256
    The above naming of variables would imply that they are related in some way. Therefore it would be nice if the UI could display them as such

    A.B.C[]

    Foo = 42
    
    Bar = 3.14
    Foobar = 256

    Obviously this is fairly arbitrary in the use of the [] but I think the idea is clear…

    2 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 →
  14. Performing dry run with octo.exe push (--whatif)

    Looking at the documentation for “octo.exe push” (https://octopus.com/docs/api-and-integration/octo.exe-command-line/push), but I cannot see any option to perform a dry run. The ‘create-release’ command has a ‘whatif’ param, and it would be really handy to have this on the ‘push’ command as well.

    24 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. Enable worker pool support for 'Deploy a Package' step

    We have nearly a dozen client/WPF projects that primarily consist of backing up a directory and then overwriting it with an updated package (size ranging from 20-350MB). Each of these projects push their packages to 20 remote servers, but the servers cannot host tentacles due to our security policies, so we run the steps from one of our Octopus hosts (via tentacle installed alongside the manager service). This is slow and expensive on the Octopus host, especially when there are many other deploys underway. Worst of all, it forces steps to deploy in serial versus parallel because all steps are…

    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 →
  16. Add a Python Modules feature to script modules and script templates

    Adding the ability to have modules pre-installed gives much more flexibility to the Python scripting feature.
    Having this available the same way "Referenced Packages" is available to PowerShell scripts would be very helpful.
    Having it apply to Script Templates as well as Script Modules would be the best.

    1 vote
    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 →
  17. Use Python Virtual Environment instead of root Python

    Using a virtual environment would be much more secure, and it would potentially give the opportunity for admins to modify the environment without changing the configuration on the servers directly.
    Also, it would give Octopus the ability to package Python as part of Calamari rather than the admins having to install Python on all the Tentacle servers.

    1 vote
    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. Output more info alongside NativeCommandError

    Rather than throwing a standard PowerShell error stack (which is only helpful in a PowerShell script), there should be some kind of log output from the Calamari that gives an indication as to what the error is (in the case of Python, a full stack trace would be nice).
    NativeCommandError's are almost always unhelpful because the output is always truncated after &quot;${env:TentacleHome}\Calamari\[version]\Calamari.exe&quot; run-script

    1 vote
    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 →
  19. hide/retire/disable step template

    It would be great to be able to hide/retire/disable step templates from the Installed Step Templates view, so that our user would not be able to add the specific step anymore.

    1 vote
    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 →
  20. Notes for Project Variables

    Have another column for the project variables for notes/documentation. This would allow for information about what the variable is for, possible lists of valid choices, what those settings do. Most are self explanatory, but some do need additional documentation and it is better than keeping this info in a separate location.

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

Feedback and Knowledge Base