I made the same change to jena development deploy so we should get a
deploy this evening.
On Mon, Jun 5, 2017 at 2:43 PM, <[email protected]
<mailto:[email protected]>> wrote:
Hm, looks like Claude's latest build failed on the same problem--
did you make you fix after that?
ajs6f
Andy Seaborne wrote on 6/4/17 11:43 AM:
See the thread
http://mail-archives.apache.org/mod_mbox/www-builds/201706.mbox/%3Cpony-84a3f5a42c31170b6f0cfe9682940d3779cc1a0d-410a725ec4f05db8367902a98b017f9d9e0d72f6%40builds.apache.org%3E
<http://mail-archives.apache.org/mod_mbox/www-builds/201706.mbox/%3Cpony-84a3f5a42c31170b6f0cfe9682940d3779cc1a0d-410a725ec4f05db8367902a98b017f9d9e0d72f6%40builds.apache.org%3E>
and I fixed it for the development build by setting it to
maven 3.3.3, not "maven 3 latest".
Andy
On 04/06/17 14:43, [email protected] <mailto:[email protected]>
wrote:
I'll take it up with INFRA tomorrow unless someone beats
me to it.
ajs6f
Claude Warren wrote on 6/4/17 8:54 AM:
Looks like the last number of Dev builds have faild
for this reason.
On Fri, Jun 2, 2017 at 11:48 AM, Andy Seaborne
<[email protected] <mailto:[email protected]>> wrote:
Jena built with maven 3.5.0 locally.
Andy
On 02/06/17 11:15, Andy Seaborne wrote:
Jenkins is having a bad time - I tried kicking
the job off (morning, UK
time) and it crashed on ubuntu-us1 with
java.lang.NoSuchFieldError:
DEFAULT_USER_SETTINGS_FILE
inside maven. Different error.
I see email on [email protected]
<mailto:[email protected]> about that. Apparently a Jenkins bug
when using "latest" maven which is now 3.5.0
Maybe that is related to what happened on
ubuntu-4 . If thart keeps
happening, then it's INFRA time:
http://www.apache.org/dev/infra-contact
<http://www.apache.org/dev/infra-contact>
(Hipchat or a ticket.)
As a temporary measure, I've kicked off a "mvn
deploy" on my machine to
get snapshot build done today.
Andy
On 01/06/17 13:00, [email protected]
<mailto:[email protected]> wrote:
Urg, we're getting:
ERROR: Maven Home
/home/jenkins/tools/maven/latest3 doesnt exist
out of that. That doesn't look right. Is
that an INFRA ticket or just
wait a bit and see if it comes back?
ajs6f
Apache Jenkins Server wrote on 6/1/17 7:34
AM:
See
<https://builds.apache.org/job/Jena_Development_Test/2674/
<https://builds.apache.org/job/Jena_Development_Test/2674/>
display/redirect?page=changes>
Changes:
[ajs6f] Upgrade some dependencies to
next minor versions
[ajs6f] Bumping HTTP Core version
------------------------------------------
Started by an SCM change
[EnvInject] - Loading node environment
variables.
Building remotely on ubuntu-4 (ubuntu
trusty) in workspace <
https://builds.apache.org/job/Jena_Development_Test/ws/
<https://builds.apache.org/job/Jena_Development_Test/ws/>>
> git rev-parse --is-inside-work-tree
# timeout=10
Fetching changes from the remote Git
repository
> git config remote.origin.url
git://git.apache.org/jena.git <http://git.apache.org/jena.git> #
timeout=10
Fetching upstream changes from
git://git.apache.org/jena.git <http://git.apache.org/jena.git>
> git --version # timeout=10
> git fetch --tags --progress
git://git.apache.org/jena.git <http://git.apache.org/jena.git>
+refs/heads/*:refs/remotes/origin/*
> git rev-parse
origin/master^{commit} # timeout=10
Checking out Revision
3b3ba37487f6e90dc5aefa48d2b64c22e9c7dca1
(origin/master)
> git config core.sparsecheckout #
timeout=10
> git checkout -f
3b3ba37487f6e90dc5aefa48d2b64c22e9c7dca1
> git rev-list
41ebfe01679a4bee830f53fe54bd9352e4f5a278 # timeout=10
ERROR: Maven Home
/home/jenkins/tools/maven/latest3 doesnt exist
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
