diff --git a/EC2 Instances(Jenkins,Nexus,Tomcat).png b/EC2 Instances(Jenkins,Nexus,Tomcat).png new file mode 100644 index 0000000000..d7748cac96 Binary files /dev/null and b/EC2 Instances(Jenkins,Nexus,Tomcat).png differ diff --git a/GitHub Repository Checkout.png b/GitHub Repository Checkout.png new file mode 100644 index 0000000000..997fe03702 Binary files /dev/null and b/GitHub Repository Checkout.png differ diff --git a/Jenkins Pipeline Job Configuration GitHub Source Checkout.png b/Jenkins Pipeline Job Configuration GitHub Source Checkout.png new file mode 100644 index 0000000000..05e7bf2a27 Binary files /dev/null and b/Jenkins Pipeline Job Configuration GitHub Source Checkout.png differ diff --git a/README.md b/README.md index 55f8b727bb..dac903b3a5 100644 --- a/README.md +++ b/README.md @@ -1 +1,78 @@ -# one \ No newline at end of file + +Project: End-to-End CI/CD Pipeline for Java Web Application using Jenkins, GitHub, Nexus, and Tomcat on AWS EC2 + +-->Built an automated CI/CD pipeline using Jenkins Pipeline on AWS EC2 + +-->Automated Java application build using Maven with SonarQube quality checks + +-->Stored build artifacts in Nexus Repository Manager + +-->Deployed WAR files automatically to Apache Tomcat + +-->Reduced manual work and improved build reliability + + +EC2 Instances(Jenkins,Nexus,Tomcat) +three running AWS EC2 instances used for a CI/CD pipeline: +- Jenkins for CI +- Nexus for artifact repository +- Tomcat for application deployment + jenkins server + nexus server + tomcat server + +pipeline job creation + +Jenkins Pipeline Job Configuration GitHub Source Checkout +Jenkins Pipeline job configuration where the pipeline script pulls source code from a GitHub repository using the git step in a declarative pipeline. + +GitHub Repository Checkout +Jenkins pipeline stage logs confirming a successful clone and checkout of source code from a GitHub repository during the CI build process. + +Maven Build +where source code is cloned from GitHub and built using Maven (mvn clean package) as part of the CI process. + +Console Output – Maven Build Execution +This displays the Jenkins console output showing a successful Maven build (mvn clean package), where dependencies are downloaded and a WAR file is generated as part of the CI pipeline. + +Build, Nexus Upload Tomcat Deployment +enkins declarative pipeline script that builds a Java application using Maven, uploads the generated WAR file to Nexus Repository Manager, and deploys it to an Apache Tomcat server automatically. + +Nexus Repository +This is the successful upload of a Maven WAR artifact to Sonatype Nexus Repository Manager. +The artifact is generated by Jenkins after a successful Maven build and stored for version control and deployment. + +**Artifact Details:** +- Group ID: `in.javahome` +- Artifact ID: `myweb` +- Version: `8.6.9` +- Packaging: WAR + +Nexus Artifact Upload Successful +Jenkins console output confirming the successful upload of the myweb-8.6.9.war artifact to the Nexus Repository using the Nexus Artifact Uploader plugin. + +WAR Deployment to Tomcat Successful +Jenkins console output confirming the successful undeploy and redeploy of the myweb-8.6.9.war application to a remote Apache Tomcat 9.x server using the Deploy to Container plugin. + +Tomcat Manager Deployed Application Running +Apache Tomcat Web Application Manager confirming that the deployed web application is running successfully after Jenkins-based WAR deployment. +web application +tomcat manager details + +all pipeline builds sucess +pipeline stages + +pipeline job + + + + + + + + + + + + + diff --git a/index.html b/index.html index 5e1db93027..141c7ab78c 100644 --- a/index.html +++ b/index.html @@ -1,4 +1,4 @@ -hello buddy +heyyy buddy this is automation work with jenkins we are implementing webhooks for making automation thanks diff --git a/pipeline job creation.png b/pipeline job creation.png new file mode 100644 index 0000000000..d39a588aa0 Binary files /dev/null and b/pipeline job creation.png differ