[JIRA] (JENKINS-40660) Parallel Test Stage in Blue Ocean marks build as successful before completing
Title: Message Title Roni Frantchi edited a comment on JENKINS-40660 Re: Parallel Test Stage in Blue Ocean marks build as successful before completing Sorry for going away for so long.I was able to verify - this seems to only reproduce when using the artifactory plugin to deploy.I believe the "issue" is the that the artifactory plugin sets the build status to success upon deployment. Even though, the build did not complete yet;Jenkins UI seems to ignore that as it knows the job is still running and so it does not manifest there.Blue Ocean however, seems to show the current status of the build parameter, regardless of wether the build is still running or not. Maybe it should also check `isBuilding` before setting the build status..? 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-40660) Parallel Test Stage in Blue Ocean marks build as successful before completing
Title: Message Title Roni Frantchi commented on JENKINS-40660 Re: Parallel Test Stage in Blue Ocean marks build as successful before completing Sorry for going away for so long. I was able to verify - this seems to only reproduce when using the artifactory plugin to deploy. I believe the "issue" is the that the artifactory plugin sets the build status to success upon deployment. Even though, the build did not complete yet; Jenkins UI seems to ignore that as it knows the job is still running and so it does not manifest there. Blue Ocean however, seems to show the current status of the build parameter, regardless of wether the build is still running or not. 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-40660) Parallel Test Stage in Blue Ocean marks build as successful before completing
Title: Message Title
Roni Frantchi commented on JENKINS-40660
Re: Parallel Test Stage in Blue Ocean marks build as successful before completing
Thanks Michael Neale . I'll try to reduce it further and post it here over the weekend, but for now here's a few inputs regarding your thoughts: > use stage('test') {... (ie block scoped stage Tried that, same results > Try commenting out the junit archive step to see if that is tricking it... I'll try that, but I'm thinking, that stage comes later right?.. so why would it make a difference? > Does it show up as finished incorrectly in the "classic" stage view? The build status is flashing with the former build color indicator; so that seems right but is there anything else I should look for?
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-40660) Parallel Test Stage in Blue Ocean marks build as successful before completing
Title: Message Title Roni Frantchi created an issue Jenkins / JENKINS-40660 Parallel Test Stage in Blue Ocean marks build as successful before completing Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-12-23 at 14.47.40.png Components: blueocean-plugin Created: 2016/Dec/23 1:03 PM Labels: blueocean Priority: Critical Reporter: Roni Frantchi See screenshot below. My pipeline consists of three main stages really; 1. Checkout the code. 2. Build the app, deploy JARs to Artifactory. 3. Run all unit tests - a step that is executed using the Parallel Test Plugin to spread the load across several nodes and executors. In steps 1 and 2, the build state is "in progress", has a blue header. As soon as it starts step 3, and before completing it, it changes the build state to "Successful", even though, it is in fact still in progress. The header turns green, but the log, available "stop" action as well as the workflow below, shows that it is in fact, still in progress. Here's a scrubbed version of my `Jenkinsfile` too: Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml #!groovy
