Multiple Deployments on the same machine

Av's Avatar


16 Oct, 2017 09:17 PM

I have 2 IIS Sites on the same machine and I want to be able to deploy to both of them in different ways. One is stage and one is prod, both for the same code base, and obviously, each will have it's own set of variables. How can this be done? I know that I can create a second tentacle for the same machine, and dummy it up that way, so-to-say, but that's a lot of overhead. And, if I were to take that route, suppose I wanted to add a third or fourth configuration? I'd then need to add additional tentacles to the machine for each IIS site. Sounds complicated. Is there a more simple way of doing this?


  1. Support Staff 1 Posted by Kenneth Bates on 17 Oct, 2017 08:32 PM

    Kenneth Bates's Avatar


    Thanks for getting in touch! While multiple Tentacles would work, it doesn't sound necessary. I think the easiest solution would be to take advantage of roles. You can use the same machine, but with multiple roles which can each be targeted for specific steps. Combining this with variables scoped to these specific roles, and I think that may be a good option.

    Let me know what you think and if you have any additional questions going forward. :)

    Best regards,


  2. 2 Posted by Av on 16 Nov, 2017 03:27 PM

    Av's Avatar

    But the same step needs to be run for 2 different roles, based on how I want to deploy it. So I'm not sure how that would work...I need to be able to deploy it to a specific target only to be determined at the time of deployment, and I won't want to have 2 steps that are identical. On the deployment page, there's an option to only deploy to specific machines or environments but not to only deploy to specific roles.

  3. 3 Posted by Av on 22 Nov, 2017 04:22 PM

    Av's Avatar

    Any updates on this?

  4. Support Staff 4 Posted by Kenneth Bates on 23 Nov, 2017 04:46 AM

    Kenneth Bates's Avatar


    Thanks for getting back to me, and I'm terribly sorry about the delay in replying! You're correct that you can't limit which machines will be deployed to by role at deployment time. You can only include or exclude specific machines individually. This feature idea may be a good one to suggest up on our UserVoice site. This is the main avenue we take when considering new features/enhancements for future releases.

    That being said, there may be a way around it. You could take advantage of the channels feature (introduced in Octopus 3.2) which would allow you to scope your steps to an individual channel. When you create your release, you select the appropriate channel for it, and that would determine which steps are run. Would that be a possible solution for you? You can refer to our comprehensive documentation around the channel feature as well if needed.

    I hope this helps! Don't hesitate to reach out if you have any further questions. :)

    Kind regards,


  5. 5 Posted by andrew.timson on 24 Nov, 2017 06:51 PM

    andrew.timson's Avatar

    Isn't this what environments are for? You can have the same machine in both the stage and prod environments, and scope the variables to those environments. Then, depending on which "mode" you want to deploy it in, you deploy to that environment

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

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