kmendoza18 / game-of-life Goto Github PK

This is an introduction, demo, and workshop of DevOps. Today we will be working with some common tools found in industry hopefully giving you better insight on what can be done with modern software engineering tools.

• Pull down, update, and deploy a functional web application via the tools commonly used in a continuous integration pipeline
• A working pipeline will also demonstrate a continuous delivery process by automatically promoting your application to a live, production environment within minutes of committing code to a source control repository

1. Break up into small teams of 2-4 individuals
2. Fork and clone application code from GitHub
3. Get the application working and commit it back to GitHub
4. See your app deploy to an app server

1. Break up into small teams of 2-4 people
2. Look at the failing build at jenkins.chico.liatr.io Login credentials will be provided.
3. Review the exercise documentation together and decide how to proceed
4. After reviewing, you may install project dependencies that are required to build/test/run your application
   • Select your OS from the list of README's below then return to this page after installion is complete.
     • Mac OS X using Homebrew *Recommended.
     • Mac OS X manual install
     • Ubuntu
     • Windows

1. Get a copy of the code for the exercise
   1. Fork the application repository at http://github.com/liatrio/game-of-life to one or more of your team members' Github Accounts
   2. If you don't have a Github account you should create one now
2. See your repository build on our build server
   1. Browse to jenkins.chico.liatr.io and sign in using the information given to you
   2. Create a new Jenkins job with your repository
      1. Click New Item on the left hand side
      2. Enter the name of your job
      3. Click Maven Project
      4. Scroll down to Source Code Management, select Git, and enter the link to your repository.
      5. Scroll down to Build Triggers and click Poll SCM and enter "* * * * *"
      6. Scroll down to Build and add "clean install" to Goals and Options
      7. Click Save
3. Verify that your job is added to Jenkins start a build
   • It should fail like the original application

1. Pull down the code from your forked repository
   1. Install a Git client if you don't have one already
   2. "Clone" the repository to your computer
2. Build and test the application locally
   1. Follow the instructions located in the application's README.md file located here
3. Determine what is breaking and change the applications code
4. Build again and fix the errors until they are completely gone
   1. This may take a few attempts
   2. You should be able to solve them by looking at the console output
   3. Roughly the last 50 lines will have information that will help you
5. Commit the working code back to your forked repository
6. See that your build is kicked off again and that is builds successfully

When the application is building correctly on Jenkins, the application will deploy to an application server