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
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,
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-08 um 12:16 schrieb Robert Scholte:
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.
All fixed. We really had some serious
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
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
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
Am 2018-09-08 um 12:16 schrieb Robert Scholte:
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
I I found out why some tests are failing:
I am going to cancel the vote and respin the release. There a some
issues not be solved. I missed one to merge as well as the issues noted
by Robert.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
+1
notice that the checksum to use is now sha512 instead of sha1
sha512 =
c376ba0eeb88d40312e29ce4047eaa6393a56d2f3f6353b296a676db3fa8cd4aabdf513863dc3b2feeae8c13530a148f220dc3a866345c76a0e37bd36c9cdeee
this will be particularly important for the dist area: the Maven parent POM
version 33 has
Am 2018-09-08 um 12:16 schrieb Robert Scholte:
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.
They are Windows-related too long paths on
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/
+1 (non-binding)
Thanks for the release.
Regards,
François
Envoyé depuis mon smartphone Samsung Galaxy.
Message d'origine De : Michael Osipov
Date : 08/09/2018 02:57 (GMT+04:00) À : Maven Developers List
Objet : [VOTE] Release Maven SCM version 1.11.0
Hi,
We solved 23
Hi,
We solved 23 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828=12343394
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SCM%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
14 matches
Mail list logo
