[
https://issues.jenkins-ci.org/browse/JENKINS-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160631#comment-160631
]
Adrian Petrescu commented on JENKINS-6338:
------------------------------------------
This is affecting us as well -- a cycle of length 2 in the dependencies (which
is intentional) results in Jenkins recompiling the projects constantly.
Is there at least any temporary workaround whereby I can manually check what
triggered a build when deciding which downstream builds it triggers itself?
Just throwing ideas out there :)
> Job's cyclic dependency not detected
> ------------------------------------
>
> Key: JENKINS-6338
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6338
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Environment: Windows XP Pro
> Hudson 1.355
> Reporter: jlpinardon
> Fix For: current
>
>
> When playing aroud with job dependencies, configured as free style projects
> and simple windws batch commands, I discovered that cyclic job dependencies
> are not detected.
> Neither when saving configuration nor when running the, supposed, "parent"
> job.
> E.g.
> JobA is configured to trigger another projet (Build Other Project) JobB wich
> is on its turn configured to trigger JobC.
> And unfortunately, JobA is finally configured to be lauched after JobC is
> finished ("Build after other projects are built").
> It results in a cyclic execution with absolutely no warning.
> I think that the cyclic dependency should be at least detected at
> configuration time and should probably forbid the execution of such a set of
> jobs.
--
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
