Skip to content

Product Feedback

Categories

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

1458 results found

  1. With Role based security, if the have a variable that is use by two environments within the scope the user of least privileges cannot see their variables. I propose that it is made visible and not display the other environment within the scope.

    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 →
  2. Add support for Octopack Nuget so that MonoAndroid and Portable Libraries can be packed with Octopack.

    Currently unable to install Octopack to portable library:
    Could not install package 'OctoPack 3.0.44'. You are trying to install this package into a project that targets 'portable-net45 ....... (and so forth) ..

    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 →
  3. If an OD setup uses a large number of Environment Variables, it can be difficult, and slow to use them for reference.

    i.e. #{EnvironmentPath}-#{Suffix}-#{SecondSuffix} isn't particularly helpful, especially if

    EnvironmentPath = #{ServerLocation}-#{ServerType}-#{TenantInstance}

    And if it nests further, it becomes incredibly slow to see how it will resolve on a deployment, short of deploying.

    If there was a way, during snapshots, or ideally through a "show resolved for : " button, then this would make it easier to reference urls from OD2.

    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 →
  4. iam currently doing a full deploy to a staging envoirement were i do i backup/restore of a database and then set the certain values that is depending on the deployment, thats why when you create a deploy i want to be able to have some steps "skipped" by default.

    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 →
  5. TeamCity has the concept of Metarunners. These allow you to package up a sequence of build steps into a single new step and reuse the sequence across multiple builds. We have a standard set of approvals that are required for deployment to certain environments. It would be nice to be able to define these approval steps once and share it to all of our applications instead of having to manage the entire process in each application directly.

    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. Please create a site extension (or something similar) that allows me to create tentacles in Azure that are easier to maintain and potentially free (using Free tier) to operate.

    This is not a request to allow deploying to a web app using a site extension. This is a request to create a site extension (or something similar) that is a tentacle for deploying to other resources.

    Currently, to perform database deployments to Azure SQL databases I am required to get a tentacle up and running somewhere. I would prefer a solution that operates on a Azure PaaS offering so that…

    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  ·  Admin →
  7. Our company deploys all projects to all environments to simplify the process at deployment time. The problem is we can't distinguish from the dashboard what environments actually have the code deployed and which ones do not because not all code goes to every environment based on the roles. If we could toggle between what has been attempted in each environment and what has actually been deployed, it would simplify post deployment queries. The toggle could be based off the same switch that determines when the retention policy is applied during deployment.

    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 →
  8. I want to be able to drop a nuget package and run post deploy scripts without deploying it to an application.
    In my case I want this to be just a package that contains migrations, usually for data fixes, which I can deploy without redeploy an app or have have fake apps in my servers.
    At the moment if I do that (just deploy a package), and not select a windows service/web app deploy the PostDeploy.ps1 in the nuget package never gets executed.

    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  ·  Admin →
  9. I'm running Octopus Deploy 3.1.1 and some of our Tentacles are running versions 3.0 and 3.1.

    One the Environment page, the environments that contain old Tentacles say "Upgrade suggested" which is fine as I understand any 3.0 Tentacle is compatible.

    However at the top of the Environment page the banner says "Tentacle upgrade required".

    So is the upgrade required (seeming mandatory to continue operation), or just suggested? I feel a tweak to the wording would create a more consistent reflection of what needs doing.

    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 →
  10. We have multiple solutions some contain both the c# application and the database project, some just contain the database projects and other projects contain items such as SSRS reports or SSIS packages. Each of these is deployed independently via Octopus. A particular business change may result in changing quite a few separate projects. So when we deploy to our test environment we need to deploy a series of project/versions in turn. We need to record the project/versions that have been deployed to test, so that when we come to deploy to production we can ensure that the exact same series…

    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 →
  11. I am implementing a large-scale deployment solution with Octous and TFS.

    I would like my build to trigger a deployment as soon as the packages have been built.

    We build around 40 packages in a five minute window.

    I am concerned that if I allowed the build scripts to trigger a deployment as soon as the package is concerned, we could end up with a massive amount of projects being deployed concurrently.

    I'd like to see, as a feature, the ability to set a max value per environment. Then, I can throw as many jobs at Octopus during my build…

    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. We have a multi-tenant setup, with one environment per client. Since we often have multiple minor releases in production at a time, it would be great to see at a glance which version is currently deployed to each environment on the "Deploy release" screen (/deployments/create) so that it's easier to pick the right clients to update.

    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. It would be good to have a control type of "Azure Subscription" in step templates, so that you can easily make step templates that runs under an azure subscription, rather than relying on the existing limited set.

    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 →
  14. When scheduling a future deploy, it'd be nice if the "Deploy release" button text changed to "Schedule release" (or similar) so the user is 100% sure they are scheduling a future release without having to scroll back up and double check.
    It would also be nice to also have the "The deployment will start in approximately ...." text that currently lives under the schedule date/time picker duplicated next to the button, again so the user can easily verify that clicking the scary green button is going to do exactly what they want.

    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 →
  15. Now when a deployment is active, there is only a 'spinner' visible. It would be nice to see something like step 3/9 for example instead of the busy sign.

    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 →
  16. We have an Octopus Deploy project that installs a significant number of Windows Services to a variety of servers. Quite often, we only need to deploy a partial set of the services, as a system patch.

    It would be useful to be able to define this partial deployment ahead of time so that it can be peer reviewed and signed off prior to any release.

    We tend to apply this patch to QA and then PROD environments, so this feature would potentially need to allow the user to define the subset of target machines for each environment; also ahead of…

    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. Lifecycle phases can either specify certain evironments, or they can specify "everything that's not otherwise specifically mentioned in another phase". It would be useful if a phase could specify a pattern, and only environment names matching the pattern would be available for deployment.

    Another (more powerful and flexible) option would be environment "tagging", where an environment could have certain "tags" applied to it, and a lifecycle phase could specify one or more tags, which would either be ANDed or ORed together to get a list of possible environments.

    Source: http://community.octopusdeploy.com/t/it-would-be-nice-if-lifecycles-could-specify-environment-name-patterns/470

    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

  18. Add Kerberos authentication for SSH deployment endpoints

    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. Octopus 2.6 used to put the current version of Octopus Server on the dashboard...I would quite like this back please!

    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 →
  20. Sometimes users need to deploy content to a sub directory within an Azure WebApp, but they dont want to include the complete webapp on the NuGet package. Currently Octopus will delete anything that is not on the NuGet package.

    A checkbox to avoid the files deletion and perhaps a field for "Custom Install dir" might be a good idea.

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