![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
git |
|
Created:
|
19/Aug/14 12:04 PM
|
|
Description:
|
After updating https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin to Version 2.2.5 (Aug 15, 2014) all my jobs that are configured to pull the SCM @hourly started doing builds like crazy one after another even if there were no SCM changes and also having it configured to check @hourly.
After i downgraded to previous version Version 2.2.4 (Aug 2, 2014), everything is working fine again.
Maybe this is related to this fix http://issues.jenkins-ci.org/browse/JENKINS-22009
—
Stept to reproduce:
1. Have a build that's already configured and working (Multiple SCMs plugin 0.3 - configured with 2 GIT sources and @hourly pooling for changes to trigger the build)
2. Update the Git plugin to Version 2.2.5
3. Go to your working job
4. Update any setting there (I've just had the branch changed)
5. Press Apply and start a build. (now Jenkins should start doing builds like crazy one after another always because it was "triggered by a SCM change" where if you go to changes there will be none.
|
|
Environment:
|
Jenkins ver. 1.575
Git plugin Version 2.2.5
Multiple SCMs plugin 0.3 - configured with 2 GIT sources and @hourly pooling for changes to trigger the build.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Blocker]() Blocker
|
|
Reporter:
|
Daniel Anechitoaie
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
