Michael Lumsden created JENKINS-13708:
-----------------------------------------
Summary: Check for Modifications feature does not check
sub-projects (erroneously does not build after check-ins detected)
Key: JENKINS-13708
URL: https://issues.jenkins-ci.org/browse/JENKINS-13708
Project: Jenkins
Issue Type: Bug
Components: synergy
Affects Versions: current
Environment: Jenkins 1.462, Synergy Plugin v1.6, Synergy v6.5, Linux OS
Reporter: Michael Lumsden
Assignee: jribette
Priority: Critical
Our SCM system is setup such that a number of projects in Synergy all inherit
from (are child projects of) one "Master" project. To perform such builds in
Jenkins, the project we are referencing is a build-user copy of the Master
project (in a working state).
If someone checked in files that affect/are related to sub-projects off that
Master project in Synergy, then the SCM Polling within Jenkins Synergy plugin
successfully identifies that changes occurred, but the "Check for
Modifications" feature prevents the build from being triggered. This appears
to be because the changes did NOT directly affect members/sub-directories of
the Master project, but instead of sub-projects within Master.
This would seem to be a bug, since the perceived intent of the "Check for
Modifications" feature is to prevent check-ins that are to the same Synergy
Release Attribute but to unrelated Synergy SCM projects from kicking off
Jenkins builds of unrelated projects, but a sub-project off a "Master" is
indeed related and should thus trigger a build if changes are detected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
