Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Follow up with JENKINS-39203 and fix the incorrect step marking #131

Closed
damienmg opened this issue Sep 28, 2017 · 2 comments
Closed

Follow up with JENKINS-39203 and fix the incorrect step marking #131

damienmg opened this issue Sep 28, 2017 · 2 comments

Comments

@damienmg
Copy link
Contributor

Right now the coloring of the step in Blue Ocean is a mess due to https://issues.jenkins-ci.org/browse/JENKINS-39203.

Due to error catching, if a test is failing or the build is failing during the test phase the whole pipeline get yellow (or red) and the precise step that caused stay green or sometime even the wrong step is shown as red. The coloring is incorrect (all step as yellow, using red for failing tests) and point at the wrong step (at least the damage is limited it shows which platforms fails now).

We should follow up with this issue and https://issues.jenkins-ci.org/browse/JENKINS-45579 that are scheduled for resolution on the Jenkins side and fix the marking step as broken

@philwo
Copy link
Member

philwo commented Jan 12, 2018

Unfortunately this is still blocked on Jenkins. Looks like they don’t even have a plan on how to fix this yet. There’s no known workaround either, except for what we currently have. :(

@philwo
Copy link
Member

philwo commented Feb 8, 2018

Obsolete, as we're migrating away from Jenkins.

@philwo philwo closed this as completed Feb 8, 2018
hlopko added a commit that referenced this issue Oct 18, 2018
joeleba pushed a commit to joeleba/continuous-integration that referenced this issue Jun 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

No branches or pull requests

2 participants