Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. nuget.exe can be autodownloaded or installed on the build server. I'd like to see OctoPack.Tasks.dll either autodownload, or provide a variable that I can use to point to an installation on the build server.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    OctoPack 3.0 no longer requires anything to be checked in. Thanks for the suggestion!

  2. Often package steps can be run in parallel, which would speed up deployments when there are lot of steps. However, not all steps can be run in parallel, my suggestion is that you should be able to edit the ordinal for a step, and if two steps have the same ordinal then they will be run in parallel.

    For example:

    1. Deploy Foo.Web
    2. Deploy Foo.ServiceA
    3. Deploy Foo.ServiceB
    4. Deploy Foo.ServiceC

    The steps for Foo.ServiceA and Foo.ServiceB will be run in parallel, Foo.ServiceC will run after they have both finished.

    27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Right the project screen displays the history of deployments for a project across all environments. It would also be nice to have a environment-centric view of deployment history. I should be able to select an environment, and see the history of the deployments of different projects on that specific environment.

    For example, being able to quickly see all of the deployments into just the Production environment would be valuable. This is especially true during active development cycles with lots of builds and noise to filter out.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    Done!


    Thanks for the suggestion everyone. I want to get some clarification before we implement it.

    The dashboard makes it pretty easy to see the current deployment in a given environment (e.g., what is currently deployed to production).

    So I’m assuming this suggestion is to be able to see what was deployed to production, is that right?

    In the Tasks tab, if we added the ability to filter by environment (and/or project, and/or task type e.g., Deployment), would that help? It should then make it pretty easy to see all deployments for environment X.

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

  4. I've done a few deployments to new environments which have failed because I've got a variable wrong (e.g a drive letter) etc. If I fix the variable, I then have to a re-deploy and increment the release number which puts it out of sync with the version of the packages I'm releasing.

    It would be great if I could hit "Try Again" and have an option to re-snapshot the variables thereby picking up any changes I might have made.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    Thanks for the suggestion – Octopus has had this ability for about 6 months now (on the release page, you can see the variables snapshot, and refresh it). We also warn you if you are attempting to deploy and the variables have changed since.

  5. The variables screen could use a number of improvements, especially when editing. The width of the value column is too small and it makes it very frustrating to use when working with long strings, i.e. connection strings. Same problem in read-only mode for long value strings, the small size of the value column makes it difficult to scan all the entries and see what the values are set to.

    A quick fix would be to allow for resizable columns and word wrap. A better/more complicated fix would be change the layout of the page from a simple grid.

    Other ares…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    Thanks for the suggestions. Variable editing got a huge overhaul in 2.0 – hopefully you’ll find it much more usable!

  6. It would be convenient if a link was provided in the Octopus Server to download the matching installer for the Octopus Tentacle.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. I'd like to be able to run an arbitrary PowerShell script on a tentacle as part of a deployment step. The script would be uploaded to the tentacle like a package and executed.

    This would make pre- and post- deployment tasks easier (stopping/starting services, redirecting load-balancers etc).

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. To prevent accidental deployments to a production environment, please could you introduce something that allows a user to schedule a deployment, but one that requires a different user to authorise that deployment?

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Released  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Schedule a deployment of a release for a date and time

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

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Can you perhaps store the hash/checksum of a package and only reupload if it changes? It would save 20+ minutes for us each time we get a failed deployment.

    Also, the ability to pre-upload those packages would be very beneficial as we can upload during the day and perform the deploy during our given window - which would minimise the down-time

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    See comment – both of these features are now supported. If you think the implementation needs to work differently please raise on help.octopusdeploy.com or create a new suggestion here.

  11. When you check Force redeployment of packages it has to re-upload the packages. Would like to force the package to be "re-executed" but using the .nupkg that was already uploaded.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    This is supported now – there are two different checkboxes on the deployment screen.

  12. We would like the ability of managing deployment in a dynamic infrastructure. Example: A scaling group on amazon EC2 spawned a new instance and installed tentacle on it. It would be nice to be able to write scripts to config the tentacle with pre-defined fingerprint, and then add the new tentacle to the octopus.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. This feature would make it possible to execute multiple deployments of releases to multiple environments simultaneously.

    The UI would allow you to select multiple releases from different projects, and for each release, choose an environment to deploy to. This feature would solve:

    http://help.octopusdeploy.com/discussions/suggestions/154-select-multiple-environments-to-deploy-to

    http://help.octopusdeploy.com/discussions/suggestions/174-parallel-batch-deployments

    http://help.octopusdeploy.com/discussions/questions/247-project-groups-deployment

    82 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    In Octopus 2.6, we added the ability to select multiple environments to deploy to. While this doesn’t allow you to deploy multiple releases simultaneously, it does allow you to deploy a release to multiple environments easily, which is what many people in the comments were asking for. Since it’s hard to separate the two, I’m going to close this item to release the votes.

  14. My goal is to remove our deployment scripts from competitors eyes.

    Since the tentacle runs PreDeploy.ps1, Deploy.ps1, PostDeploy.ps1, DeployFailed.ps1 - i would like to tentacle to be responsible in deleting these files on a successful deployment. If it fails having those scripts will benefit if we need to debug through a tentacle using run-script.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Released  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Potentially create some kind of SDK to allow for hooking into various parts of Octopus. e.g.: permissions/users could be given a custom implementation and provided by active directory.

    Example plugins we should build:
    
    https://github.com/OctopusDeploy/Issues/issues/511
    https://github.com/OctopusDeploy/Issues/issues/312
    
    28 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Email/sms/etc hooks on step/deployment success/failure

    63 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    18 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    Now that step templates make it easy to reuse scripts between projects, and the deployment process means you can put steps that run on failure or on success or both, I think this suggestion can be closed as “done”. There’s even a HipChat step template available to use right now:

    http://library.octopusdeploy.com/#!/step-template/actiontemplate-hipchat-notify

    I’ll close this since I don’t think we’ll do much else around this for the time being – that will free up some votes. Thanks all!


    Thanks for this suggestion everyone! I’d like to get some input on how notifications should work.

    Implementing a special notifications feature is tempting, but I think it could become a hugely complicated feature, especially when people want to only run notifications when deploying to certain environments, or only on failure, or to skip a notification just this once, etc..

    I’d like to find a way to support this, without requiring months of dev…

  17. Log output from deploy scripts as it is written. We run a backup script before updating that can take a while, but we have to wait until it is finished to see what was happening.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    Thanks for the suggestion Keiran, this is now implemented in versions 1.1.3 and above.

  18. I think it would be a nice feature to be able to add release notes after the release package has been created. If you are working in a CI environment, you will not write those notes on every build. When you decide that the build that was just built should be the one that should be release it would be nice to be able to log into octopus and update the release package that was created with a release note before promoting it to a new environment.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Released  ·  Paul Stovell responded

    Thanks for the suggestion everyone. You can edit release notes via the API or via the UI just by clicking on edit release.

  19. Scenario:
    FEED1 populated by the output from the build system
    FEED2 populated by QA choosing version required from FEED1
    FEED3 populated by QA approving a version from FEED2

    A project draws from the FEEDs as follows
    Integration from FEED1
    QA from FEED2
    UAT from FEED3
    Producton from FEED3

    Could be done as part of project configuration, so when setting up a project you define the feed for each environment

    Or could be done at point of deployment, but this potentially allows incorrect feeds to be used

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Released  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. If you use environment in a "progressive" fashion, you deploy the version to an environment, then promote the package to another one, etc.

    Currently, octopus download the nuget package for each step, beside the fact that it should not have changed.

    We have our nuget feed hosted near our build server (inside organisation) and octopus portal outside. Our package is 20MB, and it takes 5 minutes to upload it to octopus. We don't want to move our nuget feed outside, as we deploy as a build step, and there are more builds than octopus deployments.

    Octopus portal could use a…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Released  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?