General

  1. Audit trail and report for permissions\role changes of users

    Recently we have been audited and one of the questions asked of me was to provide a control for how permissions are managed. At the same time provide me with evidence that you periodically review permission changes using a system generated report. This would be very simple to implement using the same audit structure currently used for the deploy process and it would make auditors happy.

    7 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 →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  3. "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
    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. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    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. 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
    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. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Email step "To" field should allow variables

    Email step 'To' field should allow variables

    4 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 →
  9. 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
    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. 9 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. Store configuration transformation files in environment specific subfolders

    We found that Keep environment configuration transformation files in the root folder just differ by extension (like  .<Environment>.config) is not convenient if you have many environments and config files. Instead  we keep related files in separate subfolders named
    <Environment>&lt;application>&lt;filename>.CTT

    E.g. 
    Test\Website\web.ctt
    Test\Website\EnterpriseLibraryLogging.ctt
    Test\MyWinService\MyWinService.ctt
    Test\MyWinService\EnterpriseLibraryLogging.ctt

    Staging\Website\web.ctt
    Staging\Website\EnterpriseLibraryLogging.ctt
    Staging\MyWinService\MyWinService.ctt
    Staging\MyWinService\EnterpriseLibraryLogging.ctt

    We are using RunCTT.cmd batch similar to the following
    @rem see http://geekswithblogs.net/mnf/archive/2011/12/04/using-ctt-to-modify-config-files-for-different-environments.aspx
    @rem set cttPath=C:\webjet\Common\installs\tools\ConfigTransformationTool\CTT.exe
    set cttPath=CTT.exe
    %cttPath% s:..\Website\web.config t:Website\Web.CTT d:..\Website\web.config
    REM @pause
    attrib -r ..\Website\EnterpriseLibraryLogging.config
    %cttPath% s:..\Website\EnterpriseLibraryLogging.config t:Website\EnterpriseLibraryLogging.CTT d:..\Website\EnterpriseLibraryLogging.config

    @goto end
    :End
    @pause

    Could you consider to support similar structure in Octopus additionally to the current  <filename>.<Environment>.config ?

    11 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. Project Templates

    It would be very nice if admin could setup a project template that has common steps for every project. For example, create template that has manual intervention step for prod 1st, common variables used by every project(global variables solves this as well), powershell step for final actions and email step.

    This template saves time and allows devs to initiate prod deployment w/o creating a potential sox violation.

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the suggestion everyone. Octopus 2.1 reintroduced “clone project” functionality – you can set up a disable project (and hide it from the dashboard) with the common steps and variables that you need, and clone it when needed.

  13. Secure or Empty Variables

    Clearly we shouldn't be storing passwords in clear text in the Octopus database.

    If a user attempts to deploy a project, and a variable is empty (ex: Service Account Password), Octopus should prompt the user for the missing value/password.

    A further enhancement would be to have Octopus send an email to a person that knows the value/password, prompts them to enter the value, and then continues with the deployment.

    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 →
  14. Better support for rollbacks

    Currently (unless I am missing something), the way to do a rollback is to
    * know/remember which version was the last good one
    * navigate to that particular relase in a potensially long list of relases
    * redeploy it

    It would be easier if the product had
    * a way to mark a version as good
    * a shortcut button per app/environment for rollback. When pressing this button, Octopus should find the lastest good deployment and deploy that.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We’ve made a few UX changes that make it easier to find the old release to roll back to, and it gets better in 2.6. Closing this item to release the votes.


    Thanks for the suggestion everyone. We’re going to make some UX changes – firstly to show the previous deployment per environment (so when looking at a project, you can see that 1.1 is currently deployed to DEV, but also that 1.0 was the previous successful deployment to DEV).

    Secondly, when looking at the result of a deployment, we’ll also show the last successful deployment to that environment.

  15. Add read only Guest Account

    Add the concept of a readonly Guest account (with a blank/known password). This would enable people to see the dashboard and release notes and nothing else.

    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 →
  16. Secure variables at rest

    There are a number of suggestions for adding authorisation for access to variables through Octopus. Whilst this is absolutely needed, it does not go far enough. Especially for organisations with a low risk appetite.

    Variables - which contain credentials and other sensitive information - need to be secured at rest. The fact that they are stored as plain text in a single DB and backups presents a very significant level of risk to an organisation. Should a backup or databse copy be accessed, all credentials are lost.

    Further, no sensitive variables should be stored or logged on the tentacle. As…

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Branch support for deploying older app versions

    As a enterprise developer, who deploys with 2 version of the application (8.0 for QA and 9.0 for dev) I would like an ability to easily create release for version 8 or version 9, without manually selecting version for each package.

    That is it for a brief description. Here is a full set-up:
    1) Octopus project consists of 5 packages
    2) Each package is being built with TeamCity CI Server twice (from trunk and from branch)
    3) For deploying on different environments (dev/QA) I am using same project and environments and server role features.

    The problem is, that each time…

    191 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. non-tentacle nuget package step for custom deployment scenarios

    This seems to have already been done with the Azure service deployment step.

    I would like to have all the power of the nuget deployments but without requiring a tentacle or relying on the creation of additional service specific step types.

    One scenario this solves is EF migrations against a SQL Azure database. The current documented method requires a tentacle installed on the sql server. I could solve this with powershell and migrate.exe run from the octopus server.

    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 →
  19. capture the position of powershell errors

    When you run a powershell script it would be helpful to get the position if the error. You can do this by catching RuntimeException and then appending "ex.ErrorRecord.InvocationInfo.PositionMessage" to the error message you log.

    7 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 →
  20. Add artifacts to release

    I would be nice to be able to attach various artifacts to a release, which can be viewed/downloaded. This could be code coverage / unittest reports, script files to be reviewed by dev ops, etc. The files could be contained in the nupkg file(s) itself and identified in the project configuration as 'artifact' and hence displayed in the web ui.

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

Feedback and Knowledge Base