You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Reto Gmür <re...@apache.org> on 2016/05/18 06:12:53 UTC
Build failing on jenkins
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
Re: Build failing on jenkins
Posted by Reto Gmür <re...@apache.org>.
Thanks Rupert,
the java version needs some tidying up:
- https://stanbol.apache.org/docs/trunk/tutorial.html says that Stanbol
needs Java 6
- The parent pom configures maven-enforcer-plugin to enforce java 8
- Jenkins build with java 7 (how is this possible?)
I thinks we should harmonize things to Java 8.
Cheers,
Reto
On Wed, 18 May 2016, at 09:14, Rupert Westenthaler wrote:
> Hi Reto, all,
>
> However https://builds.apache.org/job/stanbol-trunk/1642/console notes
>
> Java 8 or higher is required to compile this modul
>
> If this is the case the `stanbol-trunk` jenkins config is broken as it
> is configured to use Java 7
>
> best
> Rupert
>
> On Wed, May 18, 2016 at 9:11 AM, Rupert Westenthaler
> <ru...@gmail.com> wrote:
> > 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 <re...@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.westenthaler@gmail.com
> > | Bodenlehenstraße 11 ++43-699-11108907
> > | A-5500 Bischofshofen
> > | REDLINK.CO ..........................................................................
> > | http://redlink.co/
>
>
>
> --
> | Rupert Westenthaler rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11 ++43-699-11108907
> | A-5500 Bischofshofen
> | REDLINK.CO
> ..........................................................................
> | http://redlink.co/
Re: Build failing on jenkins
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Reto, all,
However https://builds.apache.org/job/stanbol-trunk/1642/console notes
Java 8 or higher is required to compile this modul
If this is the case the `stanbol-trunk` jenkins config is broken as it
is configured to use Java 7
best
Rupert
On Wed, May 18, 2016 at 9:11 AM, Rupert Westenthaler
<ru...@gmail.com> wrote:
> 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 <re...@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.westenthaler@gmail.com
> | Bodenlehenstraße 11 ++43-699-11108907
> | A-5500 Bischofshofen
> | REDLINK.CO ..........................................................................
> | http://redlink.co/
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
| REDLINK.CO ..........................................................................
| http://redlink.co/
Re: Build failing on jenkins
Posted by Rupert Westenthaler <ru...@gmail.com>.
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 <re...@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.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
| REDLINK.CO ..........................................................................
| http://redlink.co/