Build Pipeline Plugin, Ball Color, and Unused Steps
Rob Mandeville
I auto-generate a bunch of build jobs and build pipeline views with the Job Generator plugin and the Job DSL plugin. My jobs use the Conditional Build Step plugin and can launch sub-jobs depending on runtime conditions. For instance, if we find a smoke test defined in the source at runtime, we deploy the system to a testbed and run the smoke tests against it. If there are no smoke tests defined, we neither deploy the code nor run the tests. Deploying the code and running smoke tests are each a Jenkins job in their own rights.
Thus, when I run a pipeline where there are no smoke tests, those two tasks are un-run, and the pipeline view shows them as blue (not successful-blue, just blue—at my site, success is green). In the nested view holding the pipeline views, however, the ball for that pipeline shows red, presumably because not all the jobs succeeded (as not all of them ran).
Is there a good way to show my users the true outcome of these pipelines? I specifically define the “true outcome” as the result of the first job in the pipeline, as it collects all test artifacts and results from all the downstream jobs.
Thanks in advance,
--Rob
This e-mail and the information, including any attachments it contains, are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.
Thank you.
Please consider the environment before printing this email.