Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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  ·  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 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  ·  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. 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  ·  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. 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  ·  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. 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  ·  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 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  ·  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. 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  ·  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. 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  ·  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. True. Powershell scripting is a powerful way of achieving more customized deployments. But not all will be well versed on scripting. Instead provide them with a UI which transforms their actions into powershell scripts used in deployments. And users can add more and more value to add by adding more actions thus making anything possible with respect to deployments. Scenarios might include taking machines out of load balancing and deploy set of services/applications and then joining them again and redo ing it for other machines. Improved and custom logging

    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. We would like to see all the releases that contain a specific version of a package, therefore able to track what environments they were deployed to as well as its history. When we may be debugging you can get the version of a binary and then be able to track the package and when/where it was deployed.

    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. Our deployment targets encompass 100+ tenants, so our deployment process encompasses multiple products within a consistently versioned suite of products.

    When we upgrade a client, they receive all components within our suite. However, some of our products support the ability for styling customizations that we like to flow through our standard/normalized release process -- these customizations get versioned in a distinct nuget package and can be redeployed within a release version. This means that our product version is redeployed multiple times for a given client if a new customization is created for a client.

    So our deployment process for this…

    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. For debugging purposes it would be extremely useful if you could have a list of variables use for at given deployment or what variables were present at creation of 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

    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. We are using Octopus and different platforms with different environments.
    we have 4 platforms, each platform has 8 QA environments and 1 production environment.

    I would like octopus to implement the "Platform" concept. So you create at platform, in that platform you create environments. Projects are living inside the platform(Like today). You should be able to scope variables to a platform.

    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. In the step templates, show which version of PowerShell the scripts work on, be useful to look at a glance and see which version they work against - the MSMQ - Create Transactional Queue only works on PowerShell version 4 and higher.

    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. The same user may be assigned to different teams, and would like to have the set of projects and environments that are displayed on the dashboard to be filtered by which team the user is currently acting as a member of. For example, user Bill is a member of the Sustaining Team and also the New Development team. He would like to log in and then choose the Sustaining team as the team he is operating under for that login session, so that he then only sees projects and environments that are relevant to Sustaining Team members.

    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. Pass an environment variable to deployment PS scripts that lists the names of sensitive variables. We would like to mask these in our file logs and currently only have the choice to output NO variables or worse, log the sensitive variable values.

    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. 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  ·  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. 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  ·  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. 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  ·  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. 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  ·  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?