In general the pipeline steps[1] is a good way good start.
But it seems like it is still not showing the unstable steps.

Another thing I do is search for "Failed: " in the console output. The label should give you enough details about the problematic combination of OS+JDK+Maven.

There's indeed some room for improvements, but that requires quite some Jenkins Plugin development knowledge ;)

thanks,
Robert

[1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-scm/job/master/60/flowGraphTable/


On Sun, 09 Sep 2018 15:37:42 +0200, Hervé BOUTEMY <herve.bout...@free.fr> wrote:

looking at CI during vote looks like a good idea because the current CI builds
a lot of things, but I fear we don't use the results as much as we should

personally, every time I get a failing build, I find it very difficult to
understand what is failing: the branch display is not useful since you can't know which step is failing [1], neither is Test Result [2] since it does not
display which step failed

And the output log, with mixed logs is awful [3]: barely unusable

And the stage logs, if I can understand which stage is failing, is so tiny in
the center of my wide screen that I can't imagine I will use it


Our Jenkinsfile configuration is great for mass managment, but is not IMHO
usable for investigating on issues

Is it just me not knowing something on the way to use the current display?

Regards,

Hervé

[1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-scm/
job/master/

[2] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-scm/
job/master/59/testReport/

[3] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-scm/
job/master/59/console

Le samedi 8 septembre 2018, 12:16:00 CEST Robert Scholte a écrit :
Before verifying this release, I'm kind of surprised that master on
builds.a.o[1] is unstable for quite some time.
Not a blocker if there are good reasons, but would like to see these fixed
as well soon.

thanks,
Robert

[1] https://builds.apache.org/job/maven-box/job/maven-scm/job/master/

On Sat, 08 Sep 2018 00:57:32 +0200, Michael Osipov <micha...@apache.org>

wrote:
> Hi,
>
> We solved 23 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&;
> version=12343394
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SCM%20AND%20res
> olution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1445/
> https://repository.apache.org/content/repositories/maven-1445/org/apache/m
> aven/scm/maven-scm/1.11.0/maven-scm-1.11.0-source-release.zip
>
> Source release checksum(s):
> maven-scm-1.11.0-source-release.zip sha1:
> eddf58c38e4d968ffc463b0b9c435bae6cf1e505
>
> Staging site:
> https://maven.apache.org/scm-archives/scm-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to