Closed tfoote closed 8 years ago
The jobs are already being generated in topological order. Also each job has the correct configuration. Jenkins does not update its in-memory representation correctly. We already trigger a rebuild (https://github.com/ros-infrastructure/ros_buildfarm/blob/f5f58aafde12956dcfeece7139dbefe087a19e23/ros_buildfarm/templates/snippet/reconfigure_jobs.groovy.em#L214) but that does not ensure that all dependencies are being used immediately.
Therefore I would close this as "wontfix" since there is nothing we can do about it.
I think this is related to #242 but a new job has been created dynamically, but does not have any of it's dependencies present in the jenkins instance.
http://build.ros.org/view/Kbin_uX64/job/Kbin_uX64__md49_base_controller__ubuntu_xenial_amd64__binary/
The raw config has the correct upstream projects:
Suggesting that it was an ordering issue on creation and if jenkins reload the project config it will work fine. Oddly though even the sourcedeb is not registered.
The associated reconfigure job is here: http://build.ros.org/job/Krel_reconfigure-jobs/98/console
It looks to have done this in the right order.