Skip to content
← Please visit roadmap.octopus.com

Settings and activity

9 results found

  1. Proget Universal Package Format Support

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Deployments  ·  Admin →
    An error occurred while saving the comment
    Darrell Tunnell commented  · 

    https://inedo.com/upack

    Darrell Tunnell shared this idea  · 

  2. Run powershell scripts under an explicit .NET version

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Deployments  ·  Admin →
    An error occurred while saving the comment
    Darrell Tunnell commented  · 

    No feedback on this? Perhaps it has been addressed in an update?

    Darrell Tunnell shared this idea  · 

  3. NPM and Bower package support

    17 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Product Feedback » Integration  ·  Admin →
    An error occurred while saving the comment
    Darrell Tunnell commented  · 

    In addition to the feed types mentioned, proget's "universal format" feed offers a basic zip format feed, and cross platform cli, and I think it would be great if octopus could support that: https://inedo.com/upack

  4. Marking a release amongst release candidates

    14 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Installation  ·  Admin →
    An error occurred while saving the comment
    Darrell Tunnell commented  · 

    We achieve this using channels and semantic versioning for our package releases. When we release a stable release that can go to a customer - we have a channel I'm octopus that targets stable release numbers. For unstable / pre-release packages, we have a separate channel. Each channel has its own life cycle. So this results in pre-releases only being able to go to our Ci environment, but stable releases can go to Dev, Staging and Production.

  5. Report Unused Variables

    29 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Deployments  ·  Admin →
    Darrell Tunnell shared this idea  · 

  6. Custom Release Properties Like Team City Build Id

    24 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Product Feedback » Integration  ·  Admin →
    An error occurred while saving the comment
    Darrell Tunnell commented  · 

    - in case it wasn't obvious - i'm not suggesting octopus adds these as 3 concrete fields - i'm suggesting Octopus provides the ability for a user to define a custom set of properties held against a release, and settable at the time of release creation. I am imagining you would define this list of fields at a project level, and if you defined any, they would appear on all future release creations.

    Darrell Tunnell shared this idea  · 

  7. Environment groups

    185 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    21 comments  ·  Product Feedback  ·  Admin →
    Darrell Tunnell supported this idea  · 
    An error occurred while saving the comment
    Darrell Tunnell commented  · 

    This could help us greatly because we would be able to consolidate all our individual customer dev, uat and production environments into a "Dev" "Uat" and "Production" groups. Then with variables that we want to set appropriately depending on whether its a Dev, Uat or Production environment we would no longer need to duplicate those variables scoping them to particular environments all the time, we could just scope them at the environment group level..

  8. Monitoring and service management

    25 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Product Feedback  ·  Admin →
    Darrell Tunnell supported this idea  · 

  9. Allow multiple dashboard configurations, and users can switch between them.

    62 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    13 comments  ·  Product Feedback  ·  Admin →
    AdminProduct Team (Admin, Octopus Deploy) responded

    I’ve reset the status of this suggestion, as the requirement described is for multiple dashboard configurations per-user, which Octopus does not currently support. Apologies for the misunderstanding.

    Darrell Tunnell shared this idea  ·