General

  1. When adding a new Machine, check that the Thumbprint of the new machine does not already exist

    We utilize Amazon AWS instances heavily and take a lot of Snapshots. Recently I've discovered that if I add a create a new AWS instance based on a Snapshot of a machine that has a Tentacle already installed, when I add that Machine (via Hostname) to the Octopus Server, the Octopus Server will not warn me that there already exists a Machine with the Same Thumbprint.

    This has caused a problem since Octopus seems to utilize the Thumbprint as an Identifier when deploying and I've accidentally deployed Code to the Wrong machine since the machine I was trying to Deploy…

    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 →
  2. Configure Default Deploy Options

    It would be nice if you were able to configure defaults for deploy options. Currently they are all false by default. I never really had a need to check any on a regular basis until Guided Deployments are introduced but now I find myself checking this option with every deployment, which isn't optimal. I'm not sure if it would be best to be able to configure these on a per project level or perhaps project group level but it would be nice to configure their defaults somehow.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Upload attachments to manual build steps

    Would be cool to be able to upload documents (e.g. test reports, approvals etc) to a manual build step and have these stored against a release for traceability and audit purposes.

    3 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. Implement a full nuget server (support for VS integration) with caching and plugin-arhcitecture to support data retention

    Implement a full nuget server (support for VS integration) with caching and plugin-arhcitecture to support data retention.

    This could perhaps be a seperate product. The key is that it should supports internal hosting, is fast, manageable and queryable via an API.

    Yes we can look at the Nuget Server source code and build it ourselves, however managing open-source package deltas is not part of our core duties

    6 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. Ability to set appSettings and connectionString values that don't exist already

    I make extensive use of appSettings values in my app, but I do not want to include every single value that can possibly be set in my source repository. I would like Octopus Deploy to allow me to set appSettings and connectionString values that will get inserted into the config if they don't exist already.

    12 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 →
  6. Guided Failure Mode

    The guided failure mode is a very nice feature and we use it a lot. One improvement that our Ops guys would like is better visibility on when a failure occurs.

    For example, we have 30 steps and as the deploy is progressing the top of the page is not visible.So, when a failure occurs that needs to be addressed you don't really know about it until you scroll to the top, because when the top of the page is off the screen there is nothing that indicates a problem.

    The only way you know there's an issue is by... …

    8 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 →
  7. Export per environment/project release calendar (ical)

    It would be nice, if it is possible to export all release dates to an iCal export.
    This would allow to bind those release to Outlook or any other systen supporting iCal.

    Currently we would like to have the export per environment but could imagine, it's also very common to have a per project view. The item must not include that many details:
    - Time of release
    - Release name
    - Project
    - Environement
    - Link to octopus release page
    - Maybe owner?

    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 →
  8. Show the total duration for a task when the log is collapsed

    When collapsing a log entry/header for a task it would be great if the total duration was displayed. That way it would be easy to spot slow tasks in a full deployment.

    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. Global deploy.ps1 or have a tentacle deploy.ps1

    We have created a deploy script that we use as standard on all of our projects. However we do have to include it in all of our projects. The only difference is the variables we pass to each project.

    It would be great if deploy.ps1 could live on the tentacle and execute that if the project doesn't have one. Or possibly chain them, tentacle executes its deploy.ps1 (if one exists - maybe a project option to skip it), then execute the project level deploy.ps1 (if one exists).

    This would save us time having to include it (ok its not a…

    1 vote
    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 →
  10. Allow specifying which Project Groups have access to Environments

    I have different applications that deploy to different sets of servers. I could create unique environments to handle the separation but it could get ugly pretty quick. If a project group was tied to a set of environments it would make it easier to know what environments apply to that project and prevent me from selecting the wrong environment to deploy to.

    5 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 →
  11. Keep track of the task expansion view (all, interesting, errors, etc.)

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

    The page should remember:

    - Whether you like to look at the summary or output
    - Which expansion option you are using

    And default to it

    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 →
  12. Add release quality properties

    Add a concept of release quality. One should be able to define (per-project) a number of quality dimensions (e.g. regarding unit tests, performance tests etc.). Values in each dimension should have absolute order. Than, for each environment one should be able to define a minimum quality level for each dimension that a release need to have in order to be deployable e.g. for UAT environment both unit and integration tests need to pass and for PROD also the performance tests need to be OK. The build quality would be editable via UI (e.g. by a QA person) and via the…

    5 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 →
  13. Ability to queue deployments or lock them

    When setting up vpn access for a deployment, it can cause issues if multiple users attempt to setup access concurrently. One way to stop this would be the user checking if any deployments are currently going on, but users don't always have access to other projects.

    It would be nice if there were rules setup to limit the number of concurrent deployments, or even just limit certain deployments so that they cannot run concurrently, adding it to a queue.

    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 →
  14. Add richer dashboard experience by allowing user to promote, create releases and detect changes.

    On the dashboard, when hovering over a successful build an arrow should appear next to it with the word 'Promote' clicking this button should start the deployment to the next environment in the chain.

    On the dashboard, when OD detects there is a new version available on the nuget feeds, a small + symbol should appear next to the project name, clicking this should take you to the create release screen.

    15 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. Access control to edit Library by environments

    I've setup global libraries. One is named Global which defines settings (across all environments) while i have other libraries named Dev, QA, Staging, and Prod. I'd like to be able to allow QA users have access to only edit the QA library similarly how they currently can only deploy to QA environments. They would be able
    to define new variables that override the global variables for their environments to validate their testing needs.

    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 →
  16. Enable rpd connection creation, Amazon style

    Enable double click or something like that on a Tentacle machine in the environment overview. When you click/doubleclick/other then adownload is started with a preconfigured rdp file.
    Just like you do on amazon.
    This way its easy to open a connection to a specific tentacle and octopus only has to create a downloadable rpd file, with server name and possible pre filled domain/user,
    VERY nice feature for handling your servers and apps :)

    5 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 →
  17. Add extensibility to UI and data layers

    Add support for custom pages or widgets that can be added to the Octopus Server installation along with custom fields that can be assigned to Project and Release. An example would be a NUnit widget that could use API to fetch NUnit test results artifact and format it nicely on release page. Other example could be storing 'build quality' property along each release. The value would be updated e.g. by the build server after executing unit tests or integration tests or a QA person after doing some exploratory testing

    7 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. Allow users to view detailed output log without deployment or enviroment permissions

    The current readonly roles do not let a user to see the detailed output of deployments.

    In larger enterprises, the dev teams can't deploy to production. However, they need to be able to see the output.

    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. View/edit permissions from users and groups view

    Right now, we have to add/edit/view permissions at the permissions view. The test feature is pretty cool, but sometimes I need to quickly check a user's permissions. Right now I have to search all the groups to see what groups they belong to, then switch to permissions view to check the group permissions.

    It would be much nicer to see the list of permissions when I view the user or the group.

    Additionally, permissions have to be added one at a time and then re-ordered.. it's very tedious when setting up a new project!!!

    3 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 →
  20. Make Tentacles auto configure the disable flag on shutdown.

    When the tentacle service shuts down, the polling tentacle would change the machine.isdisabled = true. When the service starts it would set the isdisabled=false. this allows cloud based infrastructure to dynamically turn off machines without having the deployments fail because the machine is turned off.

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

Feedback and Knowledge Base