You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devicemap.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2015/09/15 19:50:28 UTC

Jenkins build is back to normal : devicemap-data-1.0 #196

See <https://builds.apache.org/job/devicemap-data-1.0/196/changes>


Fwd: Jenkins build is back to normal : devicemap-data-1.0 #196

Posted by Werner Keil <we...@gmail.com>.
Hi,

If those who helped with Jenkins jobs before had a chance to optimize this
one, it would be great.

By coincidence, I "fixed"
https://builds.apache.org/job/devicemap-data-1.0/195/console which looks
like it was merely due to an SVN outage (or those security problems and
attacks that caused some offline moments?)

However, I did not touch any folder under /trunk/data at all, simply adjust
the C# 1.x client related to a release issue. So while it got a "good"
build again, this should ideally not be triggered by "any" change in /trunk
after disecting DeviceMap into smaller, independent modules, but only by
changes under /trunk/data, if that's possible to configure?

Cheers,
Werner

---------- Forwarded message ----------
From: Apache Jenkins Server <je...@builds.apache.org>
Date: Tue, Sep 15, 2015 at 7:50 PM
Subject: Jenkins build is back to normal : devicemap-data-1.0 #196
To: devicemap-dev@incubator.apache.org, wkeil@apache.org


See <https://builds.apache.org/job/devicemap-data-1.0/196/changes>