Skip to content
← Please visit roadmap.octopus.com

Settings and activity

2 results found

  1. Preview Transforms for an Environment

    57 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

    5 comments  ·  Product Feedback » Installation  ·  Admin →
    Nithin Shenoy supported this idea  · 
    An error occurred while saving the comment
    Nithin Shenoy commented  · 

    Based on this discussion (http://help.octopusdeploy.com/discussions/questions/7680-previewing-transforms-and-substitution), I went ahead and sort of created my own tool. I created a little powershell script that will take in a variable JSON file from a drop target, a web.config, and a web.foo.config transform file and spit out a transformed file with the final substitutions. Here's a link to the GitHub Gist: https://gist.github.com/nshenoy/79ac16c84edcc65485dff263d1e2781f . This is just an initial stab at it, but seems to work ok for what we need. Hopefully someone may find this helpful. If something like this was native in Octopus, it would be incredibly helpful (and probably more stable than this hacked up script).

  2. Save Step Templates as Powershell instead of JSON

    21 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

    3 comments  ·  Product Feedback » Installation  ·  Admin →
    An error occurred while saving the comment
    Nithin Shenoy commented  · 

    Another idea would be to have templates as folders. The folder would have the script and a sibling json metadata file. This would be somewhat similar to hubot scripts or VSTS extensions. Bottom line, the scripts need to be in a format that is readable and easily reviewable by a human outside of Octopus (e.g. windiff, GitHub diffs, etc).

    Nithin Shenoy shared this idea  ·