Skip to content

Product Feedback

Categories

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

1458 results found

  1. Would it be possible to update the releasenotesfile switch on octo.exe to allow for HTML files? My build server currently creates an html report for the releasenotes, which i would like to attached to the release via the "octo.exe -releasenotesfile" switch but it always displays an blank section. If I attach a plain text file is works, but I would like to be able to format the report.

    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  ·  Integration  ·  Admin →
  2. With really complicated deployments (55+ steps w/ 30+ package steps) having the ability to set the deployment up and save all of the desired steps and packages would be great. It can take some time to 'get everything right' set up all the steps.

    So doing this and 'Saving' the deployment would mean this can be taken care of in advance and then just having to hit the deploy button on actual deploy time.

    Source: https://octopusdeploy.uservoice.com/admin/tickets/2663

    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

  3. we are constantly switching branches that we install to our different environments. Noticed the disk are running full and realized it is because packages from old branhces are never automatically removed with current retention policies.

    Teamcity has the feature of cleaning out "More than X days older than the last 'build'" and "Older than the X-th successful 'build'"

    As I'm writing this I realize it might be quite hard to figure out if a deployment is still in use.. maybe if no current octopus project maps against the packages installed on the tentacle, it can remove the packages/applications from the…

    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  ·  Admin →
  4. Disabling a feature from a step should either remove the configuration (clear out the fields) or provide a visual queue that there is configuration that that will affect the step that is not visible.

    I had a step performing an xml transformation. I removed the transformation feature, created a release and deployed but the transformation still occurred. I had to re-add the feature and clear the transformation fields to stop the step from performing it.

    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  ·  Installation  ·  Admin →
  5. On the environments page, enable desired state configurations to be created and applied to roles. The desired state could be achieved using script templates (similar to deploy process). The desired state could be applied on a schedule or on drift.

    There would need to be a way of updating the desired state configuration when something is modified in the deploy process ie. adding a new web site.

    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  ·  Admin →
  6. In addition to displaying the project release version on the dashboard, it would be nice to see the associated package versions as well.

    e.g.
    Dashboard
    Dev
    myServices 1.0.1 (myWebservice1.0.2 + myWindowsservice1.0.3)

    At present, if you want to find out what package version is associated to a project release you need to drill into the project.

    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  ·  Admin →
  7. Not too often, but occasionally we have to update a project or variable library with a lot of changes. It would be great if there was a way to lock the variable set so after someone spends 30 minuets updating the variables they don't get a message stating that they can't save because another user made a change during this time.

    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  ·  Admin →
  8. 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  ·  Admin →
  9. On the tentacle manager screen, we currently see the 'Home directory' and 'Logs directory'. How about also showing the default 'Application directory' to which the tentacle deploys?

    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  ·  Installation  ·  Admin →
  10. on the dashboard, if you hover a deploy, you will get more information on that deploy in a little info-box. We would like to see the same behaviour but for the environments. If you hover "dev" it will list you what servers it contains, and a little icon for if it's up and running or disabled/not healthy)

    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  ·  Installation  ·  Admin →
  11. 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  ·  Admin →
  12. 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  ·  Admin →
  13. We have a host that controls UAT and production. They manually promote sites by hand currently but are open to something automated that they control.

    Internally we have a CI environment and test server but don't want to give access to the host to our intranet or active directory or expose our octopus deploy to the host.

    We would like to see the state of releases in UAT and production on the same board as our CI 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  ·  Installation  ·  Admin →
  14. Sorry if this has already been discussed.

    I was creating some powershell modules and I noticed there is no option to set dependencies on other modules.
    This would be great. Right now I am using the description to track the dependencies, but is not ideal.

    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  ·  Integration  ·  Admin →
  15. It will be really helpful to be able to enable/disable PC/Tentacle environment wide.

    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  ·  Installation  ·  Admin →
  16. 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  ·  Admin →
  17. 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  ·  Admin →
  18. 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  ·  Admin →
  19. Currently, OtcoPack considers a project a web application if a web.config file is found in its root. My stand-alone ServiceStack service project needs to have such a file when working with Razor support to enable intellisense support in VS. The web.config is never deployed however but OctoPack now deploys the project in web-style. That is, copying all binaries to the 'bin' sub directory while they should really go into the root. See https://github.com/OctopusDeploy/OctoPack/blob/fa2bbe0ce4b489316e090bf35f4d7d74d1d3a92a/source/OctoPack.Tasks/CreateOctoPackPackage.cs#L463

    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  ·  Integration  ·  Admin →
  20. Octopus Deploy has the feature to allow getting sign off/approval after a deployment completes, which is awesome! It would be even more awesome if there was an integration between Octo and TFS, where Octo would be able to retrieve the backlog items from the changesets in the release, and show their acceptance criteria. Furthermore, linked test cases to each backlog item should also be displayed.

    So something like a TFS acceptance test step, with child steps specifying each backlog item with their acceptance criteria. Then for each backlog item child step, assign child steps for the test cases linked to…

    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  ·  Admin →