Skip to content

Product Feedback

Product Feedback

Categories

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

521 results found

  1. It would be great if my deployment failed if a variable was not available in a particular environment. Currently I place a PreDeploy.ps1 with checks for particular variables (not empty) and I'm wondering if there could be a better experience for specifying that certain (or all) variables must be provided if they are used from PowerShell or elsewhere. We've had issues where our deployment went green but a variable was missing in a particular environment.

    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

    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)
  2. We have lot of tentacles, a nice feature could be to schedule the tentacles update (date and time). Select the time and date to upgrade the tentacles automatically (normally at night with low server activity)

    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

    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)
  3. Currently you can throttle the number of package aquisitions and the number of machines which will run steps in parallel.

    We see issues whereby too many steps run on the same machine causing out of memory issues.

    Can you please add configuration to limit the number of steps running in parallel on a single machine

    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

    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)
  4. We use manual interventions in several projects. Rarely (but it happens anyway) team press deploy button and go to drink a cup of tea, so when manual intervention interrupts deployment there is nobody who can agree or cancel deployment resumption.

    This issue could be easily solved if maual intervention step had timeout and fail/succeed after timeout came out.

    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

    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. I'm working on a rather large solution (client application, several windows services, several windows tasks).

    Octo has been given a Project for each component within the solution for several reasons (some services provide integration and they can be rolled by the team consuming the integration, to better track the deployment of each component, to mitigate testing of unchanged components, process and variable isolation, etc)

    We're currently rolling FEATURE based deployments... where a given deployment may involve several of the components (one rollout is to simply apply database indexes, another to tweak permissions, another for a new client feature which involves…

    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

    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. It would be cool if you all allowed for tracking of any script changes done in the script console similar to the TFS SourceControl -> View History. Without having more granular permissions for scripting, something like this would be nice to know who is doing what.

    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

    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. At present, deploy.ps1 scripts can't have 'true' PowerShell parameters, and instead have to go poking around in $OctopusParameters to see what configuration they should be using. This prevents the user from (easily) testing the deployment on their desktop.

    People have resorted to ingenious hackery to get around this (see http://www.lavinski.me/making-great-octopus-powershell-step-templates/), but whilst clever, it's more work than if parameters were just directly supported, and can't support mandatory parameters, parameter sets etc...

    Instead I think Octopus should directly support parameters on scripts, and bind octopus variables to the parameters automatically. So your deploy.ps1 could look like this:

    param(
    $databaseServer,
    $databaseName…

    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

    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)
  8. Currently it is considered best-practice to have an environment per project, if you have a stack of machines per project.
    This adds a lot of environments to the dashboard.

    I would like to be able to put a role on the environment, so that when I have DEV-CUSTA, TEST-CUSTA, PROD-CUSTA, DEV-CUSTB, ... I have roles DEV, TEST, PROD on it, and the dashboard can group by these roles

    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

    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)
  9. 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

    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)
  10. It would be good if you skip a step when deploying to the staging environment, that the release saves this skipped step somehow. So that when I promote the release to the live environment the same step will automatically be skipped.

    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

    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)
  11. If i have a variable scoped to a step that is a parent of many childs, It would be good if the childs could inherit the variable value of the parent.

    This way i could have

    • 2 variables with the same name, scoped to 2 different parent steps
    • Each Parent's child would inherit the value of their parents.
    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

    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)
  12. It is pretty easy to have an email notification sent when a deployment fails, however, it would be really nice if Octopus could send an email notification the first time a deployment succeeds after failure.

    Sending an email every time a deploy succeeds would be too much spam but sending an email the first time it succeeds after failure would let the team know that the build has been fixed in an efficient manner.

    This way the octopus server doesn't need to be monitored after each deployment.

    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

    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. This discussion started as a support thread here:

    http://help.octopusdeploy.com/discussions/questions/2571-web-package-based-parameters

    Let's say I have an App.config for a Windows Service that looks like this:

    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
      <!-- snip -->
      <system.net>
        <mailSettings>
          <smtp from="user@localdomain.org">
            <network host="smtp.local" />
          </smtp>
        </mailSettings>
      </system.net>
      <!-- snip -->
    </configuration>
    

    With the built-in transformations (appSettings and connectionStrings) I cannot replace the SMTP server host.

    For web projects in the past, I've used msdeploy (or web deploy) package parameters to do this transformation from environment to environment.

    The idea is you create a parameters.xml file locally to your project, and then each environment has a corresponding setParameters.xml…

    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

    6 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. Tentacle retention policy is executed once all deployments steps are completed. When the retention policy step starts running, it blocks any other step.
    This behavior is by design and can't be configured.

    This design can cause issues if for some reason the retention policy step encounters issues and takes a long time to complete.

    As a workaround we can add a deployment step of a dummy package at the end of the deployment process. As result the tentacle retention is executed at the last step of the deployment.

    I would like to have an option to control when the retention…

    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  ·  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. Several packages are now incompatible with FSI as it uses the old execution engine, one example is FSharp.Data and latest Newtonsoft.Json. System.Text.Json is also out of the question, basically anything targeting Netstandard 2.0.

    Switching to dotnet fsi will allow usage of said packages. It will also ensure cross platform compatibility for scripts and allows referencing packages in the script. https://devblogs.microsoft.com/dotnet/f-5-and-f-tools-update-for-june/

    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

    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)
  16. Add date, time and date/time variable types. This would validate that the input value is a valid date, time or date/time.

    Optionally provide a friendly interface (date picker control) for the respective values.

    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  ·  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. Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.

    We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.

    It would be great if you can persist the state of excluded steps to the next environments as part of same release?

    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  ·  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)
  18. Currently you can set a condition to a step so that it is only run on tenants with certain tenant tags.

    If I know want to run one step on tenants with a tag but not run a second step with a the same tenant tag (different configuration for these tenants) I have to use conditions field instead. This gives a very unclear overview of the process as it appears to that both step run on tenants with the tag.

    Ideal would be
    * Step A run on tenants with Tag A.
    * Step B run on all tenants except…

    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  ·  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. Rather than using cloud regions it would be much easier to assign a worker pool(s) to environment(s). We have a lot of security requirements and being able to use specific workers per environment would help us tremendously.

    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  ·  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. The Service Fabric Mesh deployment model is in public preview since a couple of months back and GA is expected this spring. Being mainly ARM template and container based, the SF Mesh deployment is probably possible to accompish by custom scripts today, but good out of the box support in OD would be very valuable.

    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  ·  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)
1 2 5 7 9 26 27
  • Don't see your idea?