Deployment-CI-CD-pipeline-for-jave-maven-built-web-application

created a repository for sample application on GitHub.( i have done a spring boot application maven built.) sample application:image postman:image

Created a Dockerfile for the application that includes all the dependencies and packages needed to run the application. Created a new workflow java using maven .github/workflows directory in repository and added a maven.yaml file inside it. Added the workflow in the maven.yaml file. This includes specifying the trigger events, jobs, and steps! Defined a job for the code build step in the workflow. This includes checking out the source code, installing dependencies, and running tests. Defined a job for the Docker build step in the workflow. This includes building a Docker image, tagging it, and pushing it to a Docker registry and configured the necessary environment variables, such as the Docker hub registry login credentials.image

Maven.yml file:) image image cmd prompt.txt image Screenshot (66) Screenshot (64) As a result, established a CI-CD pipeline for a spring boot application built using Maven and use the CI-CD tool Github Actions. The pipeline now includes a code build and a docker build step. cmd Prompt: image image image build: image deploy: image image

There are multiple steps to this process, but it can be summed up as follows: Written code is uploaded to a GitHub repository. Using GitHub Actions, a workflow is made that outlines the procedures required to develop and release the code.The workflow is triggered and the specified actions are carried out when code is pushed to the repository. The process involves creating the code, testing it, creating a Docker image, and deploying it to a container registry. After that, the deployed image is downloaded and used in the target environment and runned via local host at post 8080. where we taken basic spring boot java maven built appplication, Acontinuous integration and continuous deployment (CI/CD) pipeline is used throughout this process to automate the creation and deployment of code. Code changes set off the pipeline, which makes sure that they are tested, built, and delivered in a repeatable and dependable manner.