General

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

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

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

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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

    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 →
  11. Have option to use LINQ pad for script steps

    LINQ pad is adding a full command line experience and though it would be a good idea to suggest to include. Then we can code in C# as power-shell does my head in some times.

    http://www.linqpad.net/lprun.aspx

    Might not be possible but worth a suggestion

    Aaron

    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 →

    Thanks for voting on this feature. I believe that this is more about supporting C# script steps rather than specifically linqpad. As such, I’m happy to share that support for C# is available in Octopus 3.3 and later. F# support is available in Octopus 3.4 and later.

  12. "Create Release" crashes if there are too many packages in project

    If the number of packages in a Project is too high, the Query-string posted to /api/feeds/feeds-1/packages/versions?packageIds=... is too long, causing the javascript to crash in the ajax-call on line 63 in Edit.js

    This could be solved by breaking the call up in smaller pieces, or performing (although not best practice) a POST with the PackageIds in body instead of querystring.

    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 →
  13. Have the ability to link teams to AD groups, so that group membership can be managed via AD

    Our IT operation staff would like to minimize the overhead of maintaining different systems. Ideally, they would like to be able to setup Octopus once with the correct permissions associated with groups, and then manage group memberships via Active Directory.

    75 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. Feedback progress of a release to teamcity

    The teamcity plugin that triggers a release simply polls ocotpus for completion. It would be very useful for us to have the log results of the currently running release returned by the ocotpus server to teamcity. This would allow us to use a single component (ie teamcity) to monitor the progress of the release. If the release fails (failing the TC build) then the resulting email with teamcity logs would then contain all teh details needed to diagnose the problem.

    Current output in TeamCity log:

    [09:12:03][Octopus Deploy] Successfully scheduled release 1.5.0.88 for deployment to environment Dev01
    [09:12:03][Octopus Deploy] Deployment has…

    39 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 →
  15. Feature Request - Remote Location Deployment Idea

    My name is Adam and our company Chatham Financial is thinking about using Octopus to deploy our software. I would love to see one feature implemented that would greatly increase the usefulness of Octopus for us.

    We have a lot of remote locations that we currently deploy to. Due to this, we will be setting up multiple NuGet Repositories to host the files to deploy and keep them synced. The model I would like to create is to deploy to each location using the correct NuGet Repository so it has the least latency. Could you add a feature to Octopus…

    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 →
  16. Choose hosts / tentacles to deploy to

    Octopus deploy would show a checklist of hosts you choose to deploy to.

    With this feature it is possible to deploy only to the hosts you choose.

    You could use it to deploy to only 1 host, or some hosts if you wish to do a gradual deploy.

    You could also resume long deploys, if something went wrong in a previous deploy.

    17 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. Email step "To" field should allow variables

    Email step 'To' field should allow variables

    4 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 →
  18. Ability to run a powershell script **once** before and/or after the deployment

    Sometimes you need to run a script notify other systems before or after a deployment, such as monitoring systems load-balancers etc. (currently we ping NewRelic when we deploy).

    To do this in the current powershell script model you have to be creative by somehow running the script on one of the tentacles. Though there are several ways of doing this they all lead to annoying management issues since you essentially have to choose a tantacle to run the script on. One issue could be that if the tentacle is decommissioned the script stops running (without warning). It would be nice…

    98 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 →
  19. Combine "Create a Release" and "Deploy to <Env>" if successful

    It would be handy to say "Create a Release and Deploy..." instead of Create a release...waiting for it to finish and then saying Deploy to...<Env>

    Our scenario is we Build and Release to Dev several times a day.
    We then Promote a good dev release to UAT and then onwards as needed.

    This can be scripted but it would be nice to just click a button during development of the Steps.

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

Feedback and Knowledge Base