[
https://issues.jenkins-ci.org/browse/JENKINS-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pit Skywalker updated JENKINS-13601:
------------------------------------
Description: Project1 has dependencies in its pom.xml, that are listed as
Upstream Jobs in Jenkins job for Project1. And vice versa, Project1 is listed
in Downstream Jobs list in every dependent Jenkins job. But when by any trigger
dependent jobs start, when they finish, they a) do not trigger all jobs, just
one, and b) Project1 job is not triggered at all (so CI is lost for this
particular job) (was: Project1 has dependencies in its pom.xml, that are
listed as Upstream Jobs in Jenkins job for Project1. And vice versa, Project1
is listed in Downstream Jobs list in every dependent Jenkins job. But when by
any trigger depenndent jobs start, when they finish, they do not a) trigger all
jobs, just one, and b) Project1 job is not triggered at all (so CI is lost for
this particular job))
> Jenkins maven job does not trigger all downstream jobs
> ------------------------------------------------------
>
> Key: JENKINS-13601
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13601
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Environment: Debian Squeeze, 2.6.32-5 x64, Tomcat6
> Reporter: Pit Skywalker
>
> Project1 has dependencies in its pom.xml, that are listed as Upstream Jobs in
> Jenkins job for Project1. And vice versa, Project1 is listed in Downstream
> Jobs list in every dependent Jenkins job. But when by any trigger dependent
> jobs start, when they finish, they a) do not trigger all jobs, just one, and
> b) Project1 job is not triggered at all (so CI is lost for this particular
> job)
--
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
