Day23:Jenkins Freestyle Project for DevOps Engineers.
Here is part-2
What is CI/CD?
CI or Continuous Integration is the practice of automating the integration of code changes from multiple developers into a single codebase. It is a software development practice where the developers commit their work frequently into the central code repository (Github or Stash). Then there are automated tools that build the newly committed code and do a code review, etc as required upon integration. The key goals of Continuous Integration are to find and address bugs quicker, make the process of integrating code across a team of developers easier, improve software quality and reduce the time it takes to release new feature updates.
CD or Continuous Delivery is carried out after Continuous Integration to make sure that we can release new changes to our customers quickly in an error-free way. This includes running integration and regression tests in the staging area (similar to the production environment) so that the final release is not broken in production. It ensures to automate the release process so that we have a release-ready product at all times and we can deploy our application at any point in time.
What Is a Build Job?
A Jenkins build job contains the configuration for automating a specific task or step in the application building process. These tasks include gathering dependencies, compiling, archiving, or transforming code, and testing and deploying code in different environments.
Jenkins supports several types of build jobs, such as freestyle projects, pipelines, multi-configuration projects, folders, multibranch pipelines, and organization folders.
What is Freestyle Projects ??
A freestyle project in Jenkins is a type of project that allows you to build, test, and deploy software using a variety of different options and configurations.
Task-01
Create a new Jenkins freestyle project for your app.
Log in to Jenkins and navigate to the main dashboard.
Click on the "New Item" button to create a new project.
Select "Freestyle project" and give the project a name.
Click on the "OK" button to create the project.
In the project configuration page, you can specify the details of the project, such as the source code management system, build triggers, and build actions. In GitHub project write your GitHub project repository URL.
In the "Source Code Management" section, you can specify the repository location, such as Git and Select branch name "main"
In the "Build" section of the project, add a build step to run the "docker build" command to build the image for the container.
Add a second step to run the "docker run" command to start a container using the image created in step 3.
Click on the "Save" button to save the project configuration.
Build the project: You can manually build the project by clicking on the "Build Now" link in the project's main page. This will start the build process and execute the steps specified in the project configuration.
After a build is completed, you can view the console output by clicking on the "Console Output" link in the build page. This will show the output of the commands that were executed during the build
You can see image and container is created. also project from GitHub deploy to ubuntu EC2 instance at location /var/lib/jenkins/workspace/jenkins-project-name.
Task-02
Create Jenkins project to run "docker-compose up -d" command to start the multiple containers defined in the compose file
Set up a cleanup step in the Jenkins project to run "docker-compose down" command to stop and remove the containers defined in the compose file.
1)Create docker-compose.yml file inside your project
2)In the "Build" section of the project, add a build step "docker-compose down" command to stop and remove the containers defined in the compose file. then add "docker-compose up -d" command.
3)Build the project.
4)After a build is completed, you can view the console output.
5)You can see container is created.
Browse ip:8001
Thank You for reading!! I hope you find this article helpful.
Happy Learning!!
Sayali✨