How akiltipu/jenkins-aws-java-maven-app works
This repository’s product is a Jenkins-driven CI/CD pipeline for a Java application: it versions the project, builds a package and container image, publishes the image to ECR, deploys it to an EC2 host with Docker Compose, then commits the version update. The application sources are present, but no source excerpts were supplied; relationships below rely on the README’s pipeline description, not inspected implementation.
Main entry points: Jenkinsfile Deploy stage · pom.xml Maven · Dockerfile Image instructions · web-deploy.sh Deploy script
Components 15
Pipeline stages
- Jenkins pipeline
Jenkinsfile - Version increment
Jenkinsfile - Commit version
Jenkinsfile
Build and image
- Maven package
Jenkinsfile - Maven
pom.xml - Build image
Jenkinsfile - Image instructions
Dockerfile - Amazon ECR
Deployment
- Deploy stage
Jenkinsfile - Deploy script
web-deploy.sh - Compose services
docker-compose.yaml - EC2 host
Application
- Java application
src/main/java/com/example/Application.java - Static page
src/main/resources/static/index.html
Other components
- Git repository
Connections 14
- Jenkins pipeline → Version increment: runs first
README.md - Version increment → Maven: increments version
README.md - Version increment → Maven package: then builds
README.md - Maven package → Maven: packages with
README.md - Maven package → Build image: then builds
README.md - Build image → Image instructions: builds from
README.md - Build image → Amazon ECR: pushes image
README.md - Build image → Deploy stage: then deploys
README.md - Deploy stage → Deploy script: copies and runs
README.md - Deploy stage → Compose services: copies to host
README.md - Deploy stage → EC2 host: connects by SSH
README.md - Deploy stage → Amazon ECR: deploys pushed image
README.md - Deploy stage → Commit version: then commits
README.md - Commit version → Git repository: pushes version update
README.md