Real-time Use Case of Poll SCM
Suppose a situation where the development team is working on a web application using Git as the version control system and Jenkins for the continuous integration.
Use Case
Project Nature: The project mainly involves normal addition of features and bug fixing.
Poll SCM Configuration:
- Jenkins Job Setup: Jenkins job is to configured using Poll SCM for every 5 minutes (H/5 * * * *).
- Source Code Repository: The project source code is hosted on a Git repository.
Workflow
- Now throughout the day developer make changes in the code and then commit them to the Git repository.
- Jenkins configured with Poll SCM will going to check the repository in every 5 minutes.
- If changes are detected Jenkins will initiates a build
- If there is issues with the integration or if tests fails then developer will receive feedback immediately within the 5 minute of the polling interval.
What Is Poll SCM Jenkins ?, And How To Configure Poll Scm ?
Jenkins is one of the most popular open-source automation servers that provides an interface for building, testing, and deploying code. One of its essential key features is that it can trigger builds automatically based on the changes made in the source code repository. This process is known as polling SCM (Source Code Management). In this article, we will be going to discuss Poll SCM and how we can configure Poll SCM in Jenkins in detail.