Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
delivery-pipeline version: 0.6.3
Jenkins version: 1.509.4.1
Description
There are some pipelines that have no color.
I don't know what could be causing it.
The only commonality between the ones that have color and the ones that don't are this:
The ones that do NOT have color were started by an upstream change in its maven dependencies. The text will look like this:
****Example: #336 by anonymous, started 13 hours ago
The ones that work property were started by regular SCM changes, or by people manually kicking it off. The text will look like this (notice "USERNAME" in the text):
****Example: #161 by Alex Gray, anonymous, started 11 hours ago
Attachments
Activity
I was able to reproduce the problem. The bug occurs when the first Jenkins job in a pipeline has a upstream job. If so it will not find the first build in the pipeline and cant resolve the statuses for the downstream jobs.
If you want to reproduce this, do this:
1 Create a maven Jenkins project whose pom contains a dependency on another Jenkins project. Call this project "Downstream Project".
2 Create a maven Jenkins project that does nothing but compile some stuff. Call this project "Upstream Project".
In the project that contains a dependency, check "Build whenever a SNAPSHOT dependency is built".
Now modify the source code for "Upstream Project" and build it.
Jenkins will automatically kick off "Downstream Project", and the build pipeline will be blank (no colors).
If you need help reproducing this, let me know. I can probably create a zip for you.