General

  1. Delete files when Octopus Deploy is uninstalled from a machine.

    Normally, Windows Uninstall removes all program files, except those that have changed since the install (like config files and data files).
    Currently the installer does not do this.

    1 vote
    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. Make Octo.exe trace logs to the console

    It would be great if Octo.exe could trace log output to the console window - instead of waiting for deployment. We integrate into a Continuous Delivery server (not Team City), and it would be good to be able to view errors in one place.

    1 vote
    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 →
  3. When creating a new release, default the Releases Notes from all of the checkin comments since the last release.

    When creating a new release the Release Notes field is empty.

    The way that we use Octopus, when someone is making a Release it is their job to manually copy across all the checkin comments (from Team City) for all the build versions since the last Release was made.
    One per bullet (using markdown) so we get a nice list.

    Sometimes a checkin comment doesn't need to go in the release notes, or it needs to be elaborated, ... no worries. That is part of the manual job.


    So what this idea is about is: how wonderful it would be…

    25 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 →
  4. Add setting to project to indicate that the packages should all be the same version

    Our project deploys multiple packages and always uses the same version across all the packages per release. It would be nice to have a setting at the project-level to indicate this. This setting could allow the user to select the version once when creating a release and help prevent the user from accidentally entering a different version for one of the packages.

    3 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 →
  5. List variable names from .config and .ps1

    If octopus could scan packages for variables from Web.config, app.config and xxxDeploy.ps1, looking for appsettings and connectionstrings and $OctopusParameters[]. Then when adding variables it could suggest variable names. But also when creating a release it could warn about new settings/variables that have been added since last release and for which there was no variable?

    Maybe it would actually be octopack that scanned for variable names and provided it as metadata in the nuget spec?

    1 vote
    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 →
  6. Allow deployment to SQL via SQL Project inside Visual Studio

    I use a SQL Project in Visual Studio using SQL Data Tools, it would be nice to be able to deploy to SQL using the DACPAC file it creates, as it can update the database using that file

    47 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 →
  7. Add CCTray Support to monitor deploys from the CCTray tool

    CCtray the Cruise Control.Net Notfication Tray tool is a tool that polls a well known xml format and displays notifications on success or failure of builds. Team City now supports this format out of the box, and deployments in octopus actually follow a similar state pattern, where you could notify of a deployment by environment that is currently running, and report on the result of the deployment as success or failed.

    10 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 →
  8. Show date the deploy was successfully completed, not started

    Currently the Dashboard shows when a deploy was initiated but it turns out what most of us want to know is when the deploy completed.

    Suggestions:
    * Add a Octo variable so we can choose whether to show initiated or completed date on dashboard
    * Add a Step type that sets the date shown

    Scenario:
    * Multi-step deploy including a manual approval step
    * A developer queues a deployment late Tuesday evening.
    * The deployer has gone home and returns the next morning to approve the deploy.
    => The Dashboard will show Tuesday evening and confusion ensues when the manager…

    5 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 →
  9. Role dashboard

    It would be nice to have a Role dashboard.
    Eg. application 1 = role 1 and an overview where all applications (roles) will be shown in a grid

    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 →
  10. Component centric dashboard versus release centric

    Currently we have a couple ways to deploy. A main deploy which deploys our entire system 20 components (a service, website, etc) in one release. And adhoc deploys, deploys one component at a time. It would be nice to have a component view versus a release view the main point would be to show the state of each component and what version they are on.

    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 →
  11. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 24 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 →
  13. Allow for providing more details than just "Deployment failed"

    For example, if an integration/selenium step has failed, it's nice to know the number of tests that failed. In order make this generic, having special messages in the build log (similar to how Teamcity does things http://confluence.jetbrains.com/display/TCD7/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-ReportingMessagesForBuildLog) would be very helpful!

    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 →
  14. 3 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 →
  15. Bulk NuGet package version selection on create release screen

    I have 30+ steps in my project. It would be great to be able to bulk change the nuget package version for each version drop down list.

    2 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 →
  16. Pivot dashboard on version number

    Have an optional view of the dashboard (or a separate page) that pivots on version number. We have a lot of environments, and it gets hard to quickly view the dashboard and see which environments are out of date and don't have the same version. Having a list of Project->Version->Environment would help

    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. Improve User Group Administration

    User Group administration is cumbersome.

    On the group administration screen add the ability to select multiple users at once instead of typing in user names.

    On the user profile page show the groups a user is a member of. Administrators should be able to add users to groups from the profile page.

    3 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 →
  18. Ability to do swing site deployment between staging and production role

    We can deploy a release to staging and then promote it to production, it would be great if as part of the promote, we could swing the existing production deployment to staging and then promote the new release to production and also give an option to rollback to previous release.

    10 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 →

    This is a really interesting suggestion and topic. What I’m not sure about is exactly what Octopus would need to do.

    Normally for these kinds of things, you deploy the site, then change the load balancer to send requests to the new servers (the swing).

    What exactly does Octopus need to do? Should we automatically migrate the machines in the environment that we deployed to between the staging and production environments, and move the deployment to production too (or, should we just rename the staging and production environments?)

  19. Upgrade of tenticals to support Interactive Mode

    We run Tentical.exe in interactive mode rather than the service so that it can run selenium ui smoke tests after deployment.

    When we update the tentical through octopus it doesnt seem to update tentical.exe and also restarts the service.

    It would be great if deploying tentical updates from the octopus server would also update tentical.exe, idealy it would understand that tentical.exe is running interactivly and start this rather than the service after upgrade!

    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 →
  20. Start, stop, status actions

    3 new powershell scripts, start, stop and status that will you be able to trigger from the web on each project in a machine and environment.

    the status will tell you if the project is actually running or not (zero not running, 1 running) and will be probably be called every x minutes.

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

Feedback and Knowledge Base