Hi,
On Sun, 16 Sep 2018 at 06:15, Hervé BOUTEMY wrote:
> thank you Olivier: this one is really great
> the only issue is that it's really picky: you can't reload or navigate by
> tweaking url
There might be some missing configuration for blueocean (see proxy on
Apache Tomcat https://wiki.jenkins
thank you Olivier: this one is really great
the only issue is that it's really picky: you can't reload or navigate by
tweaking url
but a least, now that I know that I must start navigating from beginning to
the interesting build, I'll do it since this view is exactly what I missed
Regards,
Her
Hi
Better using blue ocean UI to have logs split
https://builds.apache.org/blue/organizations/jenkins/pipelines/?search=maven-scm
follow links to maven-scm and voilla :_
On Sun, 9 Sep 2018 at 23:37, Hervé BOUTEMY wrote:
> looking at CI during vote looks like a good idea because the current CI
>
Am 2018-09-09 um 15:37 schrieb Hervé BOUTEMY:
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 fail
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 ind
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 yo
