we are using octopus deploy currently to deploy 2 web sites to Azure Web Apps across multiple projects.
Currently we are setting up environments for each project so it is like “ENV-PROJ1-DEV”, “ENV-PROJ1-TEST”, “ENV-PROJ2-DEV”, “ENV-PROJ2-TEST” and so forth. Then we have roles like “Web” and “Admin” assigned to each azure web app deploy step so it deploys the proper package to the proper web apps based on roles. Each of the environments have different deployment targets associated with the proper roles.
As the number of projects grow the amount of environments becomes un-maintainable, not to mention the overview becomes impossible to read.
In an ideal world we would like to simply have only 2 environments like “DEV” and “TEST” and only 2 roles like “Web” and “Admin” and uses those across all projects, but we are not really sure how we can associate different deployment targets with this setup. We would like:
PROJ1 -> environment “DEV” in role “Web” first deploys to “TARGET1” and in role “Admin” to “TARGET2”, then when the release is promoted to “TEST” environment it will deploy role “Web” to “TARGET3” and role “Admin” to “TARGET4”
PROJ2 -> environment “DEV” in role “Web” first deploys to “TARGET5” and in role “Admin” to “TARGET6”, then when the release is promoted to “TEST” environment it will deploy role “Web” to “TARGET7” and role “Admin” to “TARGET8”
and so on with all the other projects. Is this something that is possible to do or are there other recommended ways of doing this? All projects are seperate projects, because of different codebases and packages, but concept is the same.