Offline Package Drop centralised variables

gavin.burke's Avatar


22 Feb, 2016 11:56 AM


We have a deployment that consists of deploying 3 different packages and runs a custom powershell scripts against 2 of them. When outputting to a package drop, the variables live in 3 different long and messy JSON files which don't look pretty sending on to a customer telling them to find line 88 and 89 and replace the variables there for step 1, then find lines 88,89,90 for step 2 and find line 88 for step 3 - it;s a bit cumbersome and very very prone to error from the customers point of view.

Is there a way to have the Offline Package Drop grab the user set variables from one single file that has just these 6 variables in so the customer can just see those and only have to set those?


  1. Support Staff 1 Posted by Rob Erez on 23 Feb, 2016 02:10 AM

    Rob Erez's Avatar

    Hi Gavin,
    It's great to hear that you are making use of the offline drop feature provided by Octopus Deploy. If I understand your problem correctly you are trying to create a drop package that you can provide to a user who can just run the deployment. As part of this process however there are some customer specific variables that you wish for them to modify so it deploys using their relevant values. Is this analysis correct?

    If this is the case then might I suggest you take a different approach. We tend to think of the Offline Drops as the "final location", like a website or azure endpoint. The package that is "deployed" to the location on the filesystem should be ready to run without much further customisation.
    For this reason a design that more closely mirrors the results you are trying to achieve would be to create multiple offline drop targets for your specific customers. Each one could be configured to point to a different folder and, by naming them in a format matching your customer, (e.g. Offline-Apple, Offline-Microsoft) you can then include machine scoped variables to your deployment plan.

    When the deployment takes place a package will be produced for each customer, all with their own custom variables already set without having to touch the variables file. Each customer then just gets their own package to deploy and you can maintain the correct values with confidence, through the Octopus Deploy pipeline.
    Does this sound like it will do what you are trying to achieve?

    If this still has some problems for your scenario, or you would like some further clarification please just let me know.

  2. 2 Posted by gavin.burke on 23 Feb, 2016 08:39 AM

    gavin.burke's Avatar

    Hi Rob

    Your analysis is correct yes, we have an application that can be hosted by the customers themselves but they won't allow our tentacles to slither into their network so the offline drop is our only option.

    I will go back to the products Product Manager with this suggestion that we control the variables so they aren't needed to be changed by whichever customer.

    Thanks for the suggestion

  3. Paul Stovell closed this discussion on 04 Jan, 2017 08:19 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac