General

  1. Renew or upgrade your Octopus Deploy license should always be https

    The octopus upgrade page can be used with http, this page should require https.

    http://octopusdeploy.com/licenses/upgrade

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Compact view for environments

    I have a lot of servers in a lot of environments and the current design can only show about 3 environments on a 1920x1080 screen.

    I'd like a narrow/compact view that uses less screen estate and can fill more computers maybe with less details.

    All I need is the Icon & name. Move the description on the same line as the Environment Name and reduce the padding/margins.

    https://github.com/OctopusDeploy/Issues/issues/837

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Ad-hoc customisation of variables when creating a deployment

    Sometimes a release requires tweaking of the project variables to cope with some kind of one-off event, or possibly a custom build to Test. This is painful in Octopus: one has to edit the variables, then either create a release or refresh an existing one, do the deployment then set the variable back at the end. Yuck.

    TeamCity handles this very well: click the ellipsis for a custom build and any of the project variables can be overridden as a one-off for that build. I'd love to see that kind of functionality in Octopus.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Reference Octopus step variables using step name/id and not index

    Currently you can reference step variables using an index, like so:

    Octopus.Step[0].Package.NuGetPackageId

    We would like to be able to reference these variables using step names or IDs, since the steps are easily reordered and this can lead to errors in variable replacement.

    Our main use case is that we want to reference the custom installation directory of another step, but feel that referencing by step name would be safer.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. have 3 different deployment results

    currently you show deploy results as success as green, success with warning as yellow and failure as red for deployments. The issue is that people that are colorblind would not really notice this, plus in my opinion (I'm not colorblind), I would still like to see a text change in addition to a color change for warnings. I would never consider anything but green as a success. if there is a warning it probably means something failed to work somewhere and it is usually something I want to fix. I see there being two possible solutions:


    1. change the warning text…
    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Enhance octo.exe to accept steps to skip

    It would be great to be able to provide octo.exe with a list of steps that you could skip.

    For instance we now have separate CI and Acceptance projects with the releases being created in each from the same TeamCity build configuration, just because we do some extra steps in CI we wouldn't want to do on our Acceptance environment.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Export deployment steps as script

    As a user
    I want to be able to export the deployment steps for a project
    So that I can deploy a release locally on my development machine

    With OctopusDeploy, it's extremely easy to perform continuous deployment to continuous integration, testing, and production environments.

    However, deploying a project on a developer machine becomes non-trivial. It's trivial enough to script building and packaging to a file but deploying on a local machine is impossible without duplicating the entirety of what OctopusDeploy does in a standard deployment (variable substitution, etc.)

    It would be ideal if we could export the deploy steps to…

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Select/deselect all steps

    Make it possible to select/deselect all steps to skip/run during a deployment with one click.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add more detail to the Releases page in 2.0

    The projects/manufacturing/releases page needs to show a bit of detail. In particular: which releases have been deployed.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Option to disable all steps

    In Octopus 1.6 we were able to disable all steps and then select only the steps we wanted. We have 30 steps and on any given release we want to only run 5 to 10 steps. It would be nice to have the disable all steps option again.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. When embedding release notes, in markdown syntax, in e-mail, parse to simple text format or html

    We embed the JIRA's resolved in this sprint into the release notes, in markdown syntax to get hyperlinks to issue and changeset. We also send e-mails out to testers, etc, to let them know what is included in the current release and they can promote to their test environment based on the fixed issues. I would like to embed the release notes in the e-mail, however no e-mail clients (besides gmail of course), support rendering mark down.

    So the feature could parse the markdown to either plain text or html, based on the setting in the e-mail step

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Reinstall packages that failed in previous releases *without* force redeployment

    At present package installations are skipped if the same version of the package has previously been installed. However this check appears to be really dumb, not accounting for when the previous deployment failed. As a result, subsequent installs skip over that step, and the package will not be re installed until its version changes.

    The current workaround is to select 'force packages to be reinstalled', but for a complex deployment this causes everything to be done again (taking time). Or, you manually select which steps to skip.

    That's all fiddly and tedious, given the 'pit of success' state would…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Scriptable Tentacle health check

    Currently the Tentacle health check seems to consist of only "Is the service running?". It would be very useful to make the Tentacle run a custom PowerShell script on health check.

    Alternatively make it possible for the health check to check for diskspace, which is what we currently need.

    60 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Environment email notifications

    I'd like to be able to send an email (the same, templated email) for all deployments to a specific environment. This way I wouldn't have to create an email notification step per project.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Automatically select "Specific Version" if user enters a specific version

    The radiobutton to select "specific version" for each package of a release should automatically be selected when the user types (or pastes) a version number in the textbox.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. When a new server is added to environment have option to deploy current version of software

    Hi,

    In cloud environments you add and remove servers. Ideally it would be great if we could add a server and its relevant role and octopus would deploy the version of each project currently deployed to that environment and role to bring it up in line with the other servers in that role.

    Cheers,
    Andrew

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the suggestion. Octopus 2.3 makes it possible to deploy a release to a specific subset of machines. When you bring a machine online, you can use this to deploy the release to just that machine.

  18. Tentacle pulling from server

    We have environments that are isolated environments consisting of VM's sitting in their own networks. The only way in/out the isolated environment is via a management server (or jumpbox) Having the Server calling Tentacles forces us to set up port forwarding on servers.

    It would be great if a Tentacle could query the server instead of server calling it. All communication would be going out of the isolated environment.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add a step that allows a powershell script to be run on the server.

    I want to deploy octopus release notes. My octopus server is internal only. If I could just run something on the server I would be able to query the api, do any formatting and put it on my server.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Mark single variable as sensitive

    We have defined a rule, that only our Ops team can see ProductionTest and Production environment and this gives a bunch of headaches.
    - Not being able to define global variables
    - Forgetting to set dependent variables i ProdTest and Prod
    - Not being able to see non-sensitive variables in ProdTest and Prod
    - Overhead for Ops, setting up non-sensitive variables

    Suggestion: Add the possibility to mark a single variable as sensitive.

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base