https://github.com/kharyam/dzone-ci-demo-app

https://github.com/kharyam/dzone-ci-demo-app

Last synced: 16 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/kharyam/dzone-ci-demo-app
• Owner: kharyam
• Created: 2016-05-30T21:34:35.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2016-12-14T11:40:24.000Z (over 7 years ago)
• Last Synced: 2024-02-24T07:34:47.935Z (4 months ago)
• Language: Java
• Size: 132 KB
• Stars: 4
• Watchers: 2
• Forks: 5
• Open Issues: 0
• Metadata Files:
  • Readme: README.adoc

Lists

• awesome-stars - kharyam/dzone-ci-demo-app - (Java)

README

        
= CI Demo Application

This is a simple Java Web Application used as a demo of a Continuous Integration (CI) pipeline. A graphical representation of the pipeline is presented below.

image:images/ci-pipeline-overview.png[]

. Developer clones code from the authoritative Git repository managed by Gerrit

. Developer pushes a code change into the pending changes repository managed by Gerrit

. The team lead reviews the code change in pending changes repository

. The team lead approves the code changes in the pending changes repository

. The team lead submits the code changes into the authoritative Git repository

. Gerrit triggers the Jenkins CI pipeline via a `change-merged` Git hook.

. The `Checkout` stage of the pipeline is run

. The `Checkout` stage clones the source code from the authoritative git repository

. The `Build` stage performs a maven build of the code

. The `Analyze` stage calls SonarQube to perform static code analysis

. The `Archive` stage uploads the WAR file into the Nexus repository. It also archives unit test results within Jenkins

. The `Deploy to Development` stage deploys the WAR from Nexus into the development servers *

. Upon authorized approval the `Deploy to Test` stage deploys the WAR into the test servers *

. Upon authorized approval the `Deploy to Production` stage deploys the WAR into the production servers *

*Note that the last three steps are considered part of the Continuous Deployment (CD) process, however this can also be handled by the Jenkins pipeline. These steps are simply placeholders that can be implemented if CD is desired.