I'm looking for recommended practice that addresses my particular issues: - we are a new project in phase 0 building out our engineering environment; - we automate our windows virtual server infrastructure-as-code with chef; - we now support windows server 2012 and 2008R2; we will support windows server 2012 R2; and - we have deployment targets for dev, qa, staging and prod environments.
What I have so far is: - given an IP address and operating system -- e.g., 2012 or 2008R2 -- I can run a job that builds out that VM; - I can pass that IP address to concurrent jobs that build, lint, unit- and integration-test, and create the binary distributions for the web and services apps that run on that VM; - I can finally pass that IP address to concurrent jobs that deploy the web and services binary distributions to that VM. What I'd like to achieve is to automate the build-out of the dev, qa, and staging environments for all our supported operating systems such that, whenever code is committed, I execute the build-test-deploy cycles to dev. Whereupon successful deployment to dev, I promote the binary distributions to the qa environment for exploratory testing. Finally, when the app passes muster on qa, I wish to promote the binary distributions to staging. I'm not sure what the recommended approach to orchestrating such a deployment pipeline on Jenkins should be. Any guidance would be greatly appreciated. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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/groups/opt_out.
