Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. I've been looking through the REST Api,

    GET /api/variables/names HTTP/1.1

    Seems to show you the names of the variables in use. But there is no existing way to get a definition of what these are through the REST API. This would be highly useful for automated testing.

    Some of these system variables are also used inside of the deployment variables. It would be nice to be able to have access to the system variables, in order to resolve the environment variables.

    This way a tester could read from Octopus deploy REST API, and execute specified tests.

    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. I'd like to be able to 'tag' an environment with one or more variables and then be able to use these variables in my release process.

    My specific use case is that I'm deploying to Azure and want to set the slot based on the environment being deployed to (Production or Staging). This works nicely with the use of #{Octopus.Environment.Name} if my environments are specifically named "Production" and "Staging", but I'd like to be able scope my environments to project groups and this requires them to have unique names. So I name my environments something like "<project>-Production" and "<project>-Staging", unfortunately…

    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. Add an option to create a deployment package just like a zip file with parametrizable powershel script file and all packages as a single setup step for non-octopus driven deployment from the deployment steps.

    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. While we make great of environments and machine roles for our production servers and devices, we still find it difficult to manage certain test scenarios without having to maintain a very large collection of test environments in order to mimic each distinct production environment. It would be nice to have an option, at the deploy time, to override or set certain variables, allowing a single test environment that can be dynamically configured to use various settings.

    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. Some of our services have large config files and we will allow some settings to be defaulted (not configured through the Octopus UI) and others must be configured. I would like a Project Level setting to be included that if enabled would decorate the deployed config file with some indication that Octopus overrode the setting. This would help tremendously to be sure which settings were defaulted and which were set by Octopus.

    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)
  6. Step template should not run if minimum power shell version is not met.

    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. I want to use Octopus to deploy an application without having to store a nuget package or create a release for it. The reason for this is that some of my automated tests are end to end tests that I run against a deployment in my WiP environment. If these tests fail, I don't ever want to be able to deploy that version of the application. The best was I see to do this is to be able to directly deploy a package through Octodeploy. Once these pass I could potentially create a release from what I just pushed or…

    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. When creating a release the user is given three options to configure a package version for each step, Latest, Last, Specifc. The default is Lastest.

    Allow the user to specify the package version default behaviour in each step.

    The user could then ensure a package stays at a particular version without having to set the version each time they create a 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

    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. Create an Octopus variable that contains the last installed directory paths for the steps in the project. This becomes useful if you have one step that deploys and another that works on the previously deployed step, but for some reason you deployed one set of steps first and later the remaining steps.

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

    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)
  11. We have a project existing out of 60 packages.
    In every package the in a appsetting in the config file.
    We now need to have in 1 specific package another value for the appsetting.
    Now we need to create a new appsetting in the config file and do some coding to read another appsetting for that 1 specific package.
    If it would be possible to scope a variable to a spefic step/package would be nice.

    0 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. On the deploy release page (the one that shows just before actually deploying a release) the channel (if any) is not shown anywhere on the page. Would be very useful to avoid mistakes when deploying.

    0 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. It would be useful to be able to run a deployment in "Debug Mode", where it would execute one step at a time, pausing after each step, so a developer can verify that it is operating correctly.

    0 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)
  14. It would be configurable and we could leverage the existing functionality of how the Health Check steps take targets out of the list for future steps.

    0 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)
  15. When a deployment is being executed, there may be some value in providing access to account credentials that have already been stored and managed in Octopus Deploy.

    While the primary motivating factor for creating the accounts section has been to provide access to deployment targets, some users may get value from using them to access or control other parts of their deployment process that sit behind some authentication mechanism. This would allow OD to better manage all the resources needed to fully complete a deployment with authentication details being securely managed in one place.

    The biggest concern with this approach…

    0 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)
  16. Enable a way to make a changes (add/remove environment, add/remove role) to multiple tentacles at once.

    0 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. Over time, older releases that are no longer in use just crowd up the release screen. I want to retain their history, so do not want to delete them.

    It would be nice to be able to hide releases.

    0 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 22 23 24 26 Next →
  • Don't see your idea?