Jenkins Pipeline Stage Result Visualization Improvements | jenkins pipeline stage
Publishedon2019-07-05byDevinNusbaum[1]SomechangeshaverecentlybeenreleasedtogivePipelineauthorssomenewtoolstoimprovePipelinevisualizationsinBlueOcean,inparticulartoaddressthehighly-votedissueJENKINS-39203[2],whichcausesallnon-failingstagestobevisualizedasthoughtheywereunstableiftheoverallbuildresultofthePipelinewasunstable.Thisissuemadeitdifficulttoquicklyidentifywhyabuildwasunstable,andforceduserstoreadthroughbuildslogsandtheJenkinsfiletofigureoutwhatactuallyhappened.Inordertofixthisissue,we...
Published on 2019-07-05 by Devin Nusbaum[1]Some changes have recently been released to give Pipeline authors some new tools to improve Pipeline visualizations in Blue Ocean, in particular to address the highly-voted issue JENKINS-39203[2], which causes all non-failing stages to be visualized as though they were unstable if the overall build result of the Pipeline was unstable. This issue made it difficult to quickly identify why a build was unstable, and forced users to read through builds logs and the Jenkinsfile to figure out what actually happened.
In order to fix this issue, we introduced a new Pipeline API that can be used to attach additional result information to individual Pipeline steps. Visualization tools like Blue Ocean use this new API when deciding how a given stage should be displayed. Steps like junit that used to set only the overall build result now additionally use the new API to set step-level result information. We created the new unstable an...