I am attempting to build a new pipeline and make it very modular and re-usable. I would like some feedback to tell me if i am going completely down the wrong path or if there are better ways to do it, so feel free to offer suggestions. Anyway, i have two initial stages, the first "prepare-app" which just pulls all the prefixed env vars from the pipeline config and then puts them into an apache vhost file ready to be deployed. The next stage "apache setup" will take that file and push it to the servers for "development pipeline" in this case.
Atm, the switch between "1, prepare-app" and "2, apache-setup" will override the previously created and configured vhost file. So, i was thinking that i can use artefacts to pull the prepared-vhost into my stage 2 apache setup, and do this for anything i want to re-use i.e a tarred version of the codebase. So, I guess a few questions would be : 1. how do i reference the path to the artefacts in code using go-cd environment variables 2. is this how i should be doing it? Environment: * My build is currently using ansible for the scripts. Reasoning: * I am thinking that having a dev pipeline, test and prod will allow this to be completely re-usable across applications with a simple pipeline clone. Hopefully that is clear ;). -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
