![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
jenkins-tracker |
|
Created:
|
21/Mar/14 7:27 AM
|
|
Description:
|
I feel this is mysterious problem being faced by me.
I have a Jenkins job A which build polling based. And during build it updates the svn revision in some files. But due to this check-in new build doesn't get triggered since the changes are part of this build only.
However I created the new job from this job only but it behaves in different manner and it considers the check-in done by the build as new change and triggers another build with that change only, thus keep on triggering the build continuously.
I am not able to trace-out why this different behavior for two jobs, rest everything is same for both the jobs except name & its source url to build the code.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
swapnil soor
|
|
|
|
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.
