General

← Feedback & Support for Octopus Deploy

I suggest you...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Composite Step Templates

    There are sets of common steps that we very often want to "bookend" all of our deployments with. One concrete example would be: sending out a Manual Intervention to confirm when all servers are confirmed live before stamping a new deployment in NewRelic.

    Right now, everyone has to bake these steps into their own projects by adding the Manual Intervention step followed by the NewRelic Deployment Stamp step. If it were possible to create what I would call "Composite Step Templates" then I could define a reusable step template that was made up of other step templates. That way, instead…

    901 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  39 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  2. Hide the "un-tenanted" release goup

    It would be nice to hide the "un-tenanted" group of releases shown on the dashboard and project overview, if the project is configured as "require a tenant for all deployments". We don't want to delete these old releases, but they are no longer relevant to us and interfer with the information shown on the dashboard.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

  3. Parallel deploy throttle

    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

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  4. Machine policies cleanup unavailable machines days or hours?

    User interface shows hours and minutes, however the API is returning a time span of days, so for example I've set 99 hours, but the time span from the API is 2376 hours or 99 days.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  5. Deployment Machine Index

    Currently every step is running for every machine.

    When you are deploying multiple machines, If you have a step that needs to run only one time per deployment like a global task for whole environment (for example; executing some database scripts before or after deployment.)

    But we need to determine machine index to run some script only at first machine...

    Regards, best wishes...

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

  6. Allow people to write plug-ins/add-ons with an SDK

    Potentially create some kind of SDK to allow for hooking into various parts of Octopus. e.g.: permissions/users could be given a custom implementation and provided by active directory.

    Example plugins we should build:

https://github.com/OctopusDeploy/Issues/issues/511
https://github.com/OctopusDeploy/Issues/issues/312
    58 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    15 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  AdminPaul Stovell (Founder, Octopus Deploy) responded

    We’re going to start on this very soon. I’d love to collect more examples of what people want to do with plugins (not so much how the plugin would work/what kind of extensibility, but the actual problem you want to solve)

  • Don't see your idea?

General

Categories

Feedback and Knowledge Base

(thinking…)