![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Vincent Latombe
|
|
Components:
|
pollscm-plugin |
|
Created:
|
26/Mar/15 10:41 AM
|
|
Description:
|
SCM polling broke for me after updating to: 1.605
Before this i was running 1.591
The log shows:
no revision found corresponding to svn://$SVN_SERVER/path; known: [svn://my.servername.com/path]
And it simply never triggered any of the builds for that reason. Apparently something changed in how or when the SCM paths get expanded.
Regardless of the change, isn't the fallback of triggering a build in case of "no revision found corresponding", a safer fallback strategy ?
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Derk-Jan Hartman
|
|
|
|
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
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
