Day 23: Jenkins Freestyle Project for DevOps Engineers.
Table of contents
- What is CI/CD?
- What Is a Build Job?
- What is Freestyle Projects ?? 🤔
- Task-01: Create an agent for your app. ( which you deployed from docker in the earlier task)
- Create a new Jenkins freestyle project for your app.
- 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.
- 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 the "docker-compose down" command to stop and remove the containers defined in the compose file.
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. Here are a few tasks that you could complete when working with a freestyle project in Jenkins:
Task-01: Create an agent for your app. ( which you deployed from docker in the earlier task)
Click on "Set up an agent"
Now, Give a node name and select "Permanent Agent"
Add details
Select "Use WebSocket" and Save
Now, Your node is ready
Create a new Jenkins freestyle project for your app.
Open your Jenkins dashboard and click on "Create a job" on the right-hand side menu. Enter a name for your project, e.g., "Todo-dev" and Select "Freestyle project" and click "OK".
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.
Add the GitHub path where your docker file is present.
In "Source Code Management" Click on "Git" and add your repository link and branch
Select "Execute shell" and add commands to execute and save it.
Now click on "Build Now" then click on #1 and check "Console Output"
Use docker ps command to check whether the container is running or not
Checking port 8000
Task-02: Create Jenkins project to run "docker-compose up -d" command to start the multiple containers defined in the compose file
Again, add a GitHub path where your file is present
Add this command to start the container
Successfully built.
Use docker ps command to check
The website is working on port 8001
Set up a cleanup step in the Jenkins project to run the "docker-compose down" command to stop and remove the containers defined in the compose file.
"Thank you for enjoying my DevOps blog! Your positive response fuels my passion to dive deeper into technology and innovation.
Stay tuned for more captivating DevOps articles, where we'll explore this dynamic field together. Follow me on Hashnode and connect on LinkedIn (https://www.linkedin.com/in/som-shanker-pandey/ for the latest updates and discussions.