Reece Walsh on 18 Jan, 2018 05:10 AM
Thanks for getting in touch, I greatly appreciate your patience in this matter.
It's not currently possible to include deployment target level scoping to Tenants.
This does, however, sound like a great idea to make Octopus even better!
I've included below a link to our User Voice area, feel free to leave your vote and thoughts it would be valuable to get your insight on how this would help your deployment process, the User Voice area is our main avenue when considering new features/enhancements like this based on community support.
There is, however, is a workaround available.
In this scenario you would be to create a new role for the second server deployment target, this role would then need to be specified against each deployment step within the XML Project, removing any existing roles that target the DFG Server.
By implementing this method you will be able to ensure that all applicable steps for the XML project run solely against the specified deployment target within the environment.
In order for the DFG project to deploy against both servers each step within the DFG project would also need to include the newly created role.
If I've misunderstood in any way or if you require any additional assistance or clarification please let me know :)
Thanks for your reply. I'm okay with creating XML project or DFG project specific deployment target roles, but about Tenants ? In other words, As I explained in the above post,
(i): when I deploy DFG for Tenant1, Octopus job should deploy on Server1 and Server2 (ii): when I deploy XML for Tenant1, Octopus job should deploy only on Server1 (iii): when I deploy DFG for Tenant2, Octopus job should deploy on Server1 and server2 (iv): when I deploy XML for Tenant2, Octopus job should deploy only on Server2
are you saying that I can achieve this b having different roles ? Could you please elaborate in detail ? Thank you.
Reece Walsh on 25 Jan, 2018 12:47 AM
Thanks for getting back to me regarding this,
I've included below some screenshots to highlight this,
To make my examples more applicable to your data I've also included a key below;
Gold Octopus = Tenant 1
-- See Attached "Tenant 1" to see in this example that Project 3 (DFG) will deploy to both Environments Testing & UAT, whilst the Project 4 for this Tenant will only deploy to the UAT Environment.
Purple Octopus = Tenant 2
-- See Attached "Tenant 2" to see in this example that Project 3 (DFG) will deploy to both Environments Testing & UAT, whilst the Project 4 for this Tenant will only deploy to the Testing Environment.
Project 3 = DFG
Project 4 = XML
To have steps within the project run against specific targets this can be accomplished using roles, you will also need to scope each step within the Project to a particular deployment target, I've included how this looks below also.
-- See "Project 1"
In contrast, you will need to specify the role of the deployment targets as shown below;
-- See "Deployment Target Roles"
If I've misunderstood in any way, please let me know :)