Hi Reto, Yes I would agree with you. When Jenkin does fail often it is because of some internal problem and not because of the build.
best Rupert On Wed, May 18, 2016 at 8:12 AM, Reto Gmür <r...@apache.org> wrote: > Hi all, > > The Jenkins build failf with the following message: > > Waiting for Jenkins to finish collecting data[ERROR] Failed to execute > goal org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy > (default-deploy) on project source-assembly: Failed to deploy artifacts: > Could not transfer artifact > org.apache.stanbol:source-assembly:pom:1.0.1-20160518.040857-2 from/to > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots): Failed > to transfer file: > https://repository.apache.org/content/repositories/snapshots/org/apache/stanbol/source-assembly/1.0.1-SNAPSHOT/source-assembly-1.0.1-20160518.040857-2.pom. > Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > > AFAICT this is unrrlated to my commit updating the clerezza > dependencies. Not sure why the artifact cannot be located, any idea? > > Cheers, > Reto -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen | REDLINK.CO .......................................................................... | http://redlink.co/
