Overview of the acceptance stage
- Run infrastructure automation code to install/configure operating systems, application/web servers, etc.
- Run infrastructure automation code to install/configure database server(s). Also, run database code to establish a small database and dataset capable of running through all longer-running tests
- Deploy the software packages (from the commit stage) onto the environment created in previous steps of acceptance stage.
- Create a small database in acceptance stage
- Deploy monitoring tools
- You’ve gone through the steps of setting up a Jenkins server and its pipeline.
- Launch Jenkins
- Go to the create-environment-acceptance-dsl job and go to Configure
- Go to https://github.com/stelligent/honolulu_answers/blob/master/pipeline/build-and-deploy-vpc.sh
- Go to https://github.com/stelligent/honolulu_answers/blob/master/pipeline/config/honolulu.template
- Open OpsWorks
- Go to https://github.com/stelligent/honolulu_answers_cookbooks/tree/master/honolulu/recipes
- Go to https://github.com/stelligent/honolulu_answers/blob/master/pipeline/bin/monitor_stack.rb
So, there are a lot of automated activities that occur in this step of the acceptance testing stage of the deployment production line. The reference implementation uses CloudFormation, OpsWorks and Chef. You saw how the various components fit together as part of the overall architecture and how this sets things up for the steps in the acceptance testing stage.