[
https://issues.jenkins-ci.org/browse/JENKINS-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159453#comment-159453
]
evernat commented on JENKINS-6338:
----------------------------------
Reproduced using Jenkins v1.446:
When a job "test" is configured to trigger a build of the same job "test", then
there is no warning but at least the trigger of the same job is silently
excluded from the configuration: clicking on configure again shows that the job
is not anymore in the triggers.
But when a job "test" is configured to trigger a build of the job "test2" and
that the job "test2" is configured to trigger the job "test", then the jobs are
not excluded from the configuration.
And when running one of the job, the jobs "test" and "test2" are indefinitely
running one after the other ! (fortunately my test jobs have no SCM and no
steps so they do nothing).
It seems easy to detect a cycle among configured jobs when checking or saving
the configuration of a job.
> 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
