Skip to content

Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

521 results found

  1. Debugging a deployment step failure can be difficult when there is no way to make sure the values passed in are what you expect. I currently have to update the step template with debug out-put statements to verify them. If there was a way to expand of view the values at the time of the step failure it would help.

    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

    0 comments  ·  Deployments  ·  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)
  2. We have a scenario were we do not want deployments which interact with the same set of servers (since we have LB draining and rollbacks) to be able to deploy at the same time.

    We would like the ability to create "Pre-Deployment' steps which can "block" a build with a user-friendly message rather than (a) failing the build or (b) forcing the user to comb through logs.

    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

    0 comments  ·  Deployments  ·  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. Warning: the term 'release' is a bit overloaded in this description. :)

    A Release (in its most general sense, not how it is defined in OD), may contain many applications, each with a specific version to be deployed during a given window to an environment.

    So, you would have something like this for any given release window:
    - Application A - v1.1
    - Applicatoin B - v2.1
    - WebService Z - v1.2

    Currently the concept of an OD release is at the application layer and I would have to track externally the connection between applications and/or versions.

    So, what I'm…

    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

    0 comments  ·  Deployments  ·  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)
  4. Octopus replaces the place holders for the plain values, even when they are sensitive, in the release descriptions.
    I discovered this when I sent my passwords to my slack channel :P

    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

    0 comments  ·  Deployments  ·  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)
  5. For linux deployments, packages are currently uploaded to $HOME/.octopus/...

    For some customers this can cause problems if the home directory is stored in a remote data centre or if the home directory has limited space.

    It would be good to allow customisation of the location where these packages are uploaded.

    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

    0 comments  ·  Deployments  ·  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)
  6. We have two environments and auto-deploy to staging in a lot of our projects. We have a release per CI build, CI builds correspond to a PR merge so usually a deployable feature.

    Current flow: Some feature or features are approved for release, I go to the overview screen and memorise which version is deployed in production, then I go to the releases screen, scroll down the last release deployed to production, scroll up checking the release notes to see if there is anything that can't go out to production.

    In a lot of cases we have 4-5 new releases…

    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

    0 comments  ·  Deployments  ·  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. We have a robust step to do ARM deployments in Azure. We are just missing the a similar step to test the template deployment. Currently we have an ugly 2 step workaround - deploy the package to the server and run azure powershell to run this command using SPN (password as a var :( ).

    It would be great to have a replica of the actual deployment step to Azure resource group - but with one command changed (test).

    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

    0 comments  ·  Deployments  ·  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. I've not used Octopus Deploy that much, at present, but I have found that the variables and the configurable nature of the steps to use these variables is key to what I have done so far, and what I'd like to do and use more efficiently going forward.

    At present, I find the variable screen/page a "problem" to work with if there are more than about 20 or 30 variables.

    In my view, requirements of this "Variable" screen/page would include:

    • Be able to filter the variables to a specific "Scope" so you can see what attributes will apply for a…

    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  ·  Deployments  ·  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. Allow for the creation of a "Channel Group" which contain existing channels. This would allow for a release to be sent to multiple channels, and allow for finer filtering of steps in a deployment. For a given project I have 10 prep steps, 8 potential pkg deployments, and 10 cleanup steps. Being able to group a prep channel, a cleanup channel, and subset of deployment channels would be handy.

    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

    0 comments  ·  Deployments  ·  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. setting "Create or update an IIS Web Site and Application Pool" is currently True/False. Would be nice to have a 3rd option which is check the settings and error if they're not as expected, but don't try to change them.

    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

    2 comments  ·  Deployments  ·  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)
  11. We should be able to check compatible version numbers on a lifecycle.

    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

    0 comments  ·  Deployments  ·  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)
  12. When creating a Release, at the stage where Octopus checks for latest Package version for a Step, first check whether we've already got the latest version for that Package.

    See this Question and associated screenshot for more information:

    http://help.octopusdeploy.com/discussions/questions/8191-when-creating-a-release-why-does-octopus-repeat-the-process-to-get-latest-version-from-teamcity

    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

    0 comments  ·  Deployments  ·  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. I have rolling step with multiple child steps in my deployment process. I would like to scope some variables to all of the child steps in rolling step. Now to do that i have to specify every child step in variable scope.
    It would be much easier if i could set scope just to rolling step (parent step) instead and it would be applied to all child steps in the rolling step.

    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

    0 comments  ·  Deployments  ·  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)
  14. Define a minimum time delay between phases in a lifecycle.

    In our situation, we do a limited deployment to a small number of targets, and then wait a few days for a bit of real world soak testing.
    It would be great to be able to define a time delay between phases to enforce and standardise the minimum length of time to wait between deployment to different environments

    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

    0 comments  ·  Deployments  ·  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. We need to drop a number of files across multiple VLAN sections. What we'd like to do is to drop push one or more packages to a tentacle deep inside the VLANs which will then do the final package drop.

    Having the tentacle perform the drop would allow us to keep the Octopus server very isolated from it's deployment targets and we'd be sure that all communication happens using the existing security protocol enforced by Octopus and that we'd be able to forego domain trusts and other messy solutions to allow the Octopus server to deploy from one network segment…

    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

    0 comments  ·  Deployments  ·  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. Currently Octopus do not have capability to capture drift in Content and Configuration. Can we add it leveraging DSC

    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

    0 comments  ·  Deployments  ·  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)
  17. It would be nice to be able to read / see the deployment steps of an older release.

    Example:

    • I've 3 steps defined in a project A
    • I create a release 1.0.0
    • I add a 4th step to the project A
    • I create a new release 1.0.1

    I this case I can check the process of 1.0.1 just by clicking on the project configration process tab but if I would like to see the process of 1.0.0 I'm unable to do so. I don't know what to expect from relase 1.0.0 because maybe too much has passed from the release…

    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  ·  Deployments  ·  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)

    Currently this feature is available via the BlueFin Chrome plugin created by David Roberts. We at Octopus are fans, and are happy to support and promote it. The only problem would be those who can’t use Chrome. Could I get some feedback on anyone restricted from using Chrome?

  18. When I setup to deploy an Azure WebApp, if I have specified the Name as a custom expression, when ever I open the step, it sits there retrieving the list of apps from Azure when it doesn't need to.

    Can you make it so it only retrieves if the Name is not a custom expression or if the user toggles back from a custom expression

    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

    0 comments  ·  Deployments  ·  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)
  19. Octopus 3 provides a lot of good features, like unpacking and repacking cspkg files. But there are a couple of features that I feel are missing:

    1. Set VMSize per environment (and step) without hacking in variable sub feature
    2. Set instance count per environment (and step)
    3. Set certificate thumbprints directly from the step (i.e. without custom powershell script)
    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

    0 comments  ·  Deployments  ·  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. There are times when I have one machine that failed a step and I want to retry that step for that machine only, then continue to deploy the rest of the steps for all machines.

    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

    0 comments  ·  Deployments  ·  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?