General

  1. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  8. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    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. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Default "Deploy to:" to blank.

    In Projects/Releases/Deploy Release, the "Deploy to" should default to blank, forcing the user to select an Environment. This will prevent deployments to the wrong environment.

    13 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 →
  12. Deploying user as a built-in variable

    For emails, it'd be nice to have the deploying username/email available for something like email steps and others.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Use 24hr HH format in the tentacle logger

    Because of time-zone differences between the Octopus server and one of our tentacles it took me a long time to realize that the wacky timestamps I was looking at were just 12 hour clock formatted, without the AM/PM suffix.

    I'd most like 24hr format, but I'll be content if the AM/PM designation was added to the existing format. But what's there right now is confusing and easily misleading.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. add email notifications for failed deployments

    I have found that one more than a few instances, a deployment to a environment failed and it has gone unnoticed until we go to manually deploy or promote to an environment. Since we use build automation in some cases a deployment fails after passing tests and the first environment deployment that was automated from our build. When we go to manually promote a build, we see the red icon on the dashboard. It would be great to get emails on any deployment failures so we can address the issue in a more timely fashion. It seems like this has…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow the API to return XML instead of JSON if requested in header

    I would like the option to return XML instead of JSON for all /api calls.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Show popup for variables values

    When you have a long value in a variable it is difficult to see the whole value. It gets cut off in the grid and I have to inspect the HTML to see the whole value.

    I would be nice if there was a hover popup or tooltip with the full value.

    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 →
  17. Red/Green/Yellow deployment status codes

    Currently, octopus deploys are either successful (green) or unsuccessful (red). We did an octopus deploy the other day to our two node web farm. Node1 deployment was successful while Node2 deployment was semi-successful (files were deployed but app pool and virtual app did not exist). Would be nice to have a yellow status code to indicate partial success (success with warnings).

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Improve the User Experience for the Octopus Variables - Realtime multiple user edit.

    If 2 users edit the Octopus Variables for a project and click save they should not overwrite the other users items.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Enable multi-select when configuring permissions

    Configuring anything other than a trivial permissions setup is horribly time-consuming. Granting a specific group a specific set of permissions, for a specific set of environments requires the creation of multiple permission grants, each of which has to be created from scratch since there's no 'copy' button next to the existing permissions.

    Changing the select permission/environment/group drop downs to multiselect would fix this in one fell swoop, and make the intent of otherwise disparate permission grants much easier to divine.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Limit max concurrent uploads

    When a project contains several steps and each step has a sizable package, we get timeout errors when uploading to the server.

    i think this is largely due to our connection speeds, but to get around this we have to retry the release in several stages by skipping all but a couple of packages at a time.

    It seems that because it is trying to all packages at once, they don't progress on enough in the given time limit.

    This could be solved in one of two ways:
    1) limiting how many packages are uploaded concurrently, if set to one…

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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