[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman, frank, christmas , 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman, frank, christmas , 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman, frank, up next, christmas Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman, frank, christmas up next , post-release christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay stopped work on JENKINS-39892 Change By: James Dumay Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman, frank, tethys, christmas , post-release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated JENKINS-39892 Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious Brody Maclean I've decided to defer this so we can solve it in conjunction with Tends post-1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman, frank, tethys, christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman, frank , christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman , frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Brody Maclean updated JENKINS-39892 Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: Brody Maclean Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Brody Maclean started work on JENKINS-39892 Change By: Brody Maclean Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Michael Neale commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious Oleg Nenashev if this is due to the mvn "ignore test failures" to ensure it runs them all, then the step doesn't actually fail (ie it is "green") - same as in stage view today. I think rsandell points out showing a summary or cause (especially if known) way ahead of the step listing is probably what would help with this (the steps won't really help you here I think). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title rsandell commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious I would also like to see what analysis/tools that failed, and some of the tests that failed. In certain systems there are known flaky tests, so if one of those are in the quick summary then you could just rerun from the summary page instead of having to go into details and you saved yourself a click or two more. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay edited a comment on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious [~oleg_nenashev] we can't do that until JENKINS-27395 is fixed. ping [~svanoort] [~hrmpw] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious Oleg Nenashev we can't do that until JENKINS-27395 is fixed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Oleg Nenashev commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious James Dumay But from what I see in Summary I won't be able to determine which test reporting step caused the failure. If I do the test parallelization across multiple machines, it will be complicated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39892
When the run fails with tests or another analysis then it should be more obvious
Change By:
James Dumay
*Problem*{quote}When I upload a PR to GitHub and Jenkins responds with something bad and I click on details; In the traditional UI I get to the build page where I with a quick glance can most of the time directly see what is wrong, wether it's a test case that has failed or a checkstyle or findbugs violation etc.With BO I first get a blank page that load a bunch of stuff, compared to the traditional UI it takes forever, and during that load time I would have already found the culprit. And then I get a page that from my perspective shows me nothing except for a yellow color indicating an unstable build, but I sort of already knew that. And then I need to click around to find out what is wrong. While in the traditional build page I only need to click something to find out the details of why a particular thing is wrong.{quote}*Possible solution** When we detect that tests that have failed (or another analysis ) that is the cause of a failed run) the failure the log is not expanded and the "Issues detected" panel appears at the top of the screen.* Developer can click on the summary information in the issues detect and jump into analysis
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious Oleg Nenashev if there are any failed tests we will show this summary Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Oleg Nenashev commented on JENKINS-39892 Re: When the run fails with tests or another analysis then it should be more obvious If the test run marks the build unstable instead of Failed, it should be also visible. In https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/master/113/pipeline I get an unstable state, but all Pipeline steps are being shown as green. It complicates the analysis if you have multiple test result publishing steps Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Change By: James Dumay Sprint: tasman Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39892
When the run fails with tests or another analysis then it should be more obvious
Change By:
James Dumay
*Problem*{quote}When I upload a PR to GitHub and Jenkins responds with something bad and I click on details; In the traditional UI I get to the build page where I with a quick glance can most of the time directly see what is wrong, wether it's a test case that has failed or a checkstyle or findbugs violation etc.With BO I first get a blank page that load a bunch of stuff, compared to the traditional UI it takes forever, and during that load time I would have already found the culprit. And then I get a page that from my perspective shows me nothing except for a yellow color indicating an unstable build, but I sort of already knew that. And then I need to click around to find out what is wrong. While in the traditional build page I only need to click something to find out the details of why a particular thing is wrong.{quote} *Possible solution** When we detect that tests (or another analysis) is the cause of the failure the log is not expanded and the "Issues detected" panel appears at the top of the screen.* Developer can click on the summary information in the issues detect and jump into analysis
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39892 When the run fails with tests or another analysis then it should be more obvious Issue Type: Task Assignee: Brody Maclean Attachments: Failing result.png Components: blueocean-plugin Created: 2016/Nov/20 11:56 PM Priority: Minor Reporter: James Dumay Problem When I upload a PR to GitHub and Jenkins responds with something bad and I click on details; In the traditional UI I get to the build page where I with a quick glance can most of the time directly see what is wrong, wether it's a test case that has failed or a checkstyle or findbugs violation etc. With BO I first get a blank page that load a bunch of stuff, compared to the traditional UI it takes forever, and during that load time I would have already found the culprit. And then I get a page that from my perspective shows me nothing except for a yellow color indicating an unstable build, but I sort of already knew that. And then I need to click around to find out what is wrong. While in the traditional build page I only need to click something to find out the details of why a particular thing is wrong.
