Skip to content
← Navigate to roadmap.octopus.com

Settings and activity

3 results found

  1. Octopus server "linking"/clustering

    9 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

    0 comments  ·  Product Feedback » Deployments  ·  Admin →
    Dafydd Giddins supported this idea  · 

  2. Deploy without storing a package or release

    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

    0 comments  ·  Product Feedback » Deployments  ·  Admin →
    Dafydd Giddins shared this idea  · 

  3. Store XML transformations in Octopus

    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

    6 comments  ·  Product Feedback  ·  Admin →
    An error occurred while saving the comment
    Dafydd Giddins commented  · 

    This would be really useful for me. My situation is that I have a lot of transforms I need to run on my config (NSB Queue machine names, lots of DB strings) that don't sit in applicationSettings section or connectionStrings section. I don't want to store environment config in source control and storing as many variables as I have in the big long variables list in Octopus would be hard to maintain.
    If I could simply define the different transforms in the correct XML structure it would be much easier to maintain.

    Dafydd Giddins supported this idea  ·