Loading
peterkaras
This is a live streamed presentation. You will automatically follow the presenter and see the slide they're currently on.
Build & Unit Test
Developer makes change to code and pushes to GIT
Jenkins detects change in GIT and pulls new code onto CI Server
Jenkins executes Maven command to build code and run unit tests
If build fails Jenkins Mails team.
If build succeeds Jenkins archives succesfull build.
Prepare Acceptance test environment
Run Acceptance tests
Publish Results
Jenkins triggers Acceptance test environment build
Jenkins
Maven
Docker
GitHub
Developer Workstation
DockerHub
CI Server
Build & Unit Test
Production
Docker downloads image from DockerHub with OS + database installed
Docker installs build tools (git, maven, firefox etc), products (Tomcat, JDK) into image.
Docker Pulls latest version of test framework from GIT and downloads latest version of Application from Jenkins and installs on Tomcat
Docker Saves image ready for testing.
Build & Unit Test
Prepare Acceptance test environment
Run Acceptance tests
Publish Results
Jenkins
Maven
Docker
GitHub
Developer Workstation
DockerHub
CI Server
Production
Prepare Acceptance test environment
Jenkins starts Docker image and runs Acceptance tests using Concordion and Selenium WebDriver
If Tests fail email sent to team
Build & Unit Test
Prepare Acceptance test environment
Run Acceptance tests
Publish Results
Jenkins
Maven
Docker
GitHub
Developer Workstation
DockerHub
CI Server
Production
Run Acceptance tests
Jenkins runs Maven site to generate test reports
Test report copied onto intranet
Build & Unit Test
Prepare Acceptance test environment
Run Acceptance tests
Publish Results
Application is verified ready for Release (Release Candidate)
Business decides to release and deploys verified artifact from Jenkins Server
Jenkins
Maven
Docker
GitHub
Developer Workstation
DockerHub
CI Server
Production
Run Acceptance tests