pasupuleti2 created the topic: SCM polling stopped to work
Rajesh,
Recently I’m having problems with a Jenkins 1.57 builds, for some reason after a while Jenkins stops to poll the SCM (the Git (Bitbucket) polling log seems to contain the last _successful_ check and that’s all), also periodic building seem to suffer from the same problem. Are you aware of any known issues that could cause this problem? Where should I look for possible causes? (in my setup I have several slave nodes, but the vast majority of the jobs are being built on the master node)
Our Server is Windows server 2012.
Any help would be appreciated.
Thanks
-Saritha
rajeshkumar replied the topic: SCM polling stopped to work
This is expected behaviour. SCM poll will return true / false based on the changes. if not change found, it wont do anything..
This method does the actual polling and should return true or false if there are any changes in the repository.
More info
wiki.jenkins-ci.org/display/JENKINS/Polling+for+changes
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
- Use of runtime variables to save into another variable using register in Ansible - September 6, 2018
- Ansible & Ansible Tower Variable Precedence Hierarchy - September 6, 2018
- How to use template in Ansible? - September 6, 2018
Thanks for highlighting this SCM polling issue! When Jenkins stops polling the source code repository, it’s often due to configuration or environment problems rather than Jenkins itself silently failing. Make sure your Poll SCM trigger is correctly enabled and saved, that the SCM repository URL and branch names are accurate, and that valid credentials are provided — because misconfigured SCM settings can prevent Jenkins from detecting changes. Also check whether the relevant plugins (like the Git or SVN plugin) are up to date and compatible with your Jenkins version, and review the Jenkins logs for polling errors, as they often show connection or authentication failures that help pinpoint the root cause. In many cases, switching to webhook‑based triggers (where the SCM notifies Jenkins of changes) provides more reliable build triggering than traditional polling.