Re: Build failed in Jenkins: sling-trunk-1.7 #2409
On Sun, 2015-10-04 at 14:56 +0530, Carsten Ziegeler wrote: > It seems we're getting a lot of failures due to deploy problems. Do > we > really need to deploy the snapshots? (as I doubt that we can fix the > deployment problems) Or can we maybe ignore the error if deployment > fails? For the record, this is tracked under https://issues.apache.org/jira/browse/INFRA-7984 Robert > > Regards > Carsten > > Am 04.10.15 um 13:07 schrieb Apache Jenkins Server: > > > Waiting for Jenkins to finish collecting data > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven > > -deploy-plugin:2.8.2:deploy (default-deploy) on project > > org.apache.sling.settings: Failed to deploy metadata: Could not > > transfer metadata org.apache.sling:org.apache.sling.settings:1.3.7 > > -SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https ( > > https://repository.apache.org/content/repositories/snapshots): > > Failed to transfer file: https://repository.apache.org/content/repo > > sitories/snapshots/org/apache/sling/org.apache.sling.settings/1.3.7 > > -SNAPSHOT/maven-metadata.xml. Return code is: 502, ReasonPhrase: > > Proxy Error. -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven > > with the -e switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug > > logging. > > [ERROR] > > [ERROR] For more information about the errors and possible > > solutions, please read the following articles: > > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/M > > ojoExecutionException > > [ERROR] > > [ERROR] After correcting the problems, you can resume the build > > with the command > > [ERROR] mvn -rf :org.apache.sling.settings > > channel stopped > > > >
Re: Build failed in Jenkins: sling-trunk-1.7 #2409
Another option is to retry the build if it fails using the Naginator plugin [1]. We can set it up to retry the job in case we have some known failures, like Java crashing or Nexus being down. Robert [1]: https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin On Tue, 2015-10-06 at 10:09 +0200, Julian Sedding wrote: > Maybe the "retryFailedDeploymentCount" of the maven-deploy-plugin > could help? Unfortunately I could not find an option to stop the > build > from failing if deployment fails - that's what I think Carsten > suggested and would be ideal IMHO. > > Regards > Julian > > On Tue, Oct 6, 2015 at 10:00 AM, Robert Munteanu > wrote: > > On Sun, 2015-10-04 at 14:56 +0530, Carsten Ziegeler wrote: > > > It seems we're getting a lot of failures due to deploy problems. > > > Do > > > we > > > really need to deploy the snapshots? (as I doubt that we can fix > > > the > > > deployment problems) Or can we maybe ignore the error if > > > deployment > > > fails? > > > > IIRC we need snapshots for two reasons > > > > - the sling-oak-it-1.7 Jenkins job, which is built after the sling > > -trunk-1.7 job deploys the jars and uses them for ITs > > - building the launchpad locally without building the full Sling > > reactor ( we had people asking why we have to build _everything_ > > for > > the launchpad ). > > > > Nexus seems to be stable for now, but I'll look into alternate > > solutions if this keeps being a problem. > > > > There is a 'Deploy artifacts to Maven repository' post-build action > > in > > Jenkins, but I'm not sure whether it fails the build on error or > > not. > > But I won't activate it straight away since it requires automatic > > artifact archival to be enabled, and we disabled it because it > > takes a > > lot of time. > > > > Robert > > > > > > > > Regards > > > Carsten > > > > > > Am 04.10.15 um 13:07 schrieb Apache Jenkins Server: > > > > > > > Waiting for Jenkins to finish collecting data > > > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven > > > > -deploy-plugin:2.8.2:deploy (default-deploy) on project > > > > org.apache.sling.settings: Failed to deploy metadata: Could not > > > > transfer metadata > > > > org.apache.sling:org.apache.sling.settings:1.3.7 > > > > -SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https ( > > > > https://repository.apache.org/content/repositories/snapshots): > > > > Failed to transfer file: > > > > https://repository.apache.org/content/repo > > > > sitories/snapshots/org/apache/sling/org.apache.sling.settings/1 > > > > .3.7 > > > > -SNAPSHOT/maven-metadata.xml. Return code is: 502, > > > > ReasonPhrase: > > > > Proxy Error. -> [Help 1] > > > > [ERROR] > > > > [ERROR] To see the full stack trace of the errors, re-run Maven > > > > with the -e switch. > > > > [ERROR] Re-run Maven using the -X switch to enable full debug > > > > logging. > > > > [ERROR] > > > > [ERROR] For more information about the errors and possible > > > > solutions, please read the following articles: > > > > [ERROR] [Help 1] > > > > http://cwiki.apache.org/confluence/display/MAVEN/M > > > > ojoExecutionException > > > > [ERROR] > > > > [ERROR] After correcting the problems, you can resume the build > > > > with the command > > > > [ERROR] mvn -rf :org.apache.sling.settings > > > > channel stopped > > > > > > > > > > > >
Re: Build failed in Jenkins: sling-trunk-1.7 #2409
On Tue, 2015-10-06 at 10:09 +0200, Julian Sedding wrote: > Maybe the "retryFailedDeploymentCount" of the maven-deploy-plugin > could help? Unfortunately I could not find an option to stop the > build > from failing if deployment fails - that's what I think Carsten > suggested and would be ideal IMHO. In case this happens again I will experiment with the setting - it should help us move away from intermittent failures ( but not outages ). Robert > > Regards > Julian > > On Tue, Oct 6, 2015 at 10:00 AM, Robert Munteanu > wrote: > > On Sun, 2015-10-04 at 14:56 +0530, Carsten Ziegeler wrote: > > > It seems we're getting a lot of failures due to deploy problems. > > > Do > > > we > > > really need to deploy the snapshots? (as I doubt that we can fix > > > the > > > deployment problems) Or can we maybe ignore the error if > > > deployment > > > fails? > > > > IIRC we need snapshots for two reasons > > > > - the sling-oak-it-1.7 Jenkins job, which is built after the sling > > -trunk-1.7 job deploys the jars and uses them for ITs > > - building the launchpad locally without building the full Sling > > reactor ( we had people asking why we have to build _everything_ > > for > > the launchpad ). > > > > Nexus seems to be stable for now, but I'll look into alternate > > solutions if this keeps being a problem. > > > > There is a 'Deploy artifacts to Maven repository' post-build action > > in > > Jenkins, but I'm not sure whether it fails the build on error or > > not. > > But I won't activate it straight away since it requires automatic > > artifact archival to be enabled, and we disabled it because it > > takes a > > lot of time. > > > > Robert > > > > > > > > Regards > > > Carsten > > > > > > Am 04.10.15 um 13:07 schrieb Apache Jenkins Server: > > > > > > > Waiting for Jenkins to finish collecting data > > > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven > > > > -deploy-plugin:2.8.2:deploy (default-deploy) on project > > > > org.apache.sling.settings: Failed to deploy metadata: Could not > > > > transfer metadata > > > > org.apache.sling:org.apache.sling.settings:1.3.7 > > > > -SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https ( > > > > https://repository.apache.org/content/repositories/snapshots): > > > > Failed to transfer file: > > > > https://repository.apache.org/content/repo > > > > sitories/snapshots/org/apache/sling/org.apache.sling.settings/1 > > > > .3.7 > > > > -SNAPSHOT/maven-metadata.xml. Return code is: 502, > > > > ReasonPhrase: > > > > Proxy Error. -> [Help 1] > > > > [ERROR] > > > > [ERROR] To see the full stack trace of the errors, re-run Maven > > > > with the -e switch. > > > > [ERROR] Re-run Maven using the -X switch to enable full debug > > > > logging. > > > > [ERROR] > > > > [ERROR] For more information about the errors and possible > > > > solutions, please read the following articles: > > > > [ERROR] [Help 1] > > > > http://cwiki.apache.org/confluence/display/MAVEN/M > > > > ojoExecutionException > > > > [ERROR] > > > > [ERROR] After correcting the problems, you can resume the build > > > > with the command > > > > [ERROR] mvn -rf :org.apache.sling.settings > > > > channel stopped > > > > > > > > > > > >
Re: Build failed in Jenkins: sling-trunk-1.7 #2409
Maybe the "retryFailedDeploymentCount" of the maven-deploy-plugin could help? Unfortunately I could not find an option to stop the build from failing if deployment fails - that's what I think Carsten suggested and would be ideal IMHO. Regards Julian On Tue, Oct 6, 2015 at 10:00 AM, Robert Munteanu wrote: > On Sun, 2015-10-04 at 14:56 +0530, Carsten Ziegeler wrote: >> It seems we're getting a lot of failures due to deploy problems. Do >> we >> really need to deploy the snapshots? (as I doubt that we can fix the >> deployment problems) Or can we maybe ignore the error if deployment >> fails? > > IIRC we need snapshots for two reasons > > - the sling-oak-it-1.7 Jenkins job, which is built after the sling > -trunk-1.7 job deploys the jars and uses them for ITs > - building the launchpad locally without building the full Sling > reactor ( we had people asking why we have to build _everything_ for > the launchpad ). > > Nexus seems to be stable for now, but I'll look into alternate > solutions if this keeps being a problem. > > There is a 'Deploy artifacts to Maven repository' post-build action in > Jenkins, but I'm not sure whether it fails the build on error or not. > But I won't activate it straight away since it requires automatic > artifact archival to be enabled, and we disabled it because it takes a > lot of time. > > Robert > >> >> Regards >> Carsten >> >> Am 04.10.15 um 13:07 schrieb Apache Jenkins Server: >> >> > Waiting for Jenkins to finish collecting data >> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven >> > -deploy-plugin:2.8.2:deploy (default-deploy) on project >> > org.apache.sling.settings: Failed to deploy metadata: Could not >> > transfer metadata org.apache.sling:org.apache.sling.settings:1.3.7 >> > -SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https ( >> > https://repository.apache.org/content/repositories/snapshots): >> > Failed to transfer file: https://repository.apache.org/content/repo >> > sitories/snapshots/org/apache/sling/org.apache.sling.settings/1.3.7 >> > -SNAPSHOT/maven-metadata.xml. Return code is: 502, ReasonPhrase: >> > Proxy Error. -> [Help 1] >> > [ERROR] >> > [ERROR] To see the full stack trace of the errors, re-run Maven >> > with the -e switch. >> > [ERROR] Re-run Maven using the -X switch to enable full debug >> > logging. >> > [ERROR] >> > [ERROR] For more information about the errors and possible >> > solutions, please read the following articles: >> > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/M >> > ojoExecutionException >> > [ERROR] >> > [ERROR] After correcting the problems, you can resume the build >> > with the command >> > [ERROR] mvn -rf :org.apache.sling.settings >> > channel stopped >> > >> >> >
Re: Build failed in Jenkins: sling-trunk-1.7 #2409
On Sun, 2015-10-04 at 14:56 +0530, Carsten Ziegeler wrote: > It seems we're getting a lot of failures due to deploy problems. Do > we > really need to deploy the snapshots? (as I doubt that we can fix the > deployment problems) Or can we maybe ignore the error if deployment > fails? IIRC we need snapshots for two reasons - the sling-oak-it-1.7 Jenkins job, which is built after the sling -trunk-1.7 job deploys the jars and uses them for ITs - building the launchpad locally without building the full Sling reactor ( we had people asking why we have to build _everything_ for the launchpad ). Nexus seems to be stable for now, but I'll look into alternate solutions if this keeps being a problem. There is a 'Deploy artifacts to Maven repository' post-build action in Jenkins, but I'm not sure whether it fails the build on error or not. But I won't activate it straight away since it requires automatic artifact archival to be enabled, and we disabled it because it takes a lot of time. Robert > > Regards > Carsten > > Am 04.10.15 um 13:07 schrieb Apache Jenkins Server: > > > Waiting for Jenkins to finish collecting data > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven > > -deploy-plugin:2.8.2:deploy (default-deploy) on project > > org.apache.sling.settings: Failed to deploy metadata: Could not > > transfer metadata org.apache.sling:org.apache.sling.settings:1.3.7 > > -SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https ( > > https://repository.apache.org/content/repositories/snapshots): > > Failed to transfer file: https://repository.apache.org/content/repo > > sitories/snapshots/org/apache/sling/org.apache.sling.settings/1.3.7 > > -SNAPSHOT/maven-metadata.xml. Return code is: 502, ReasonPhrase: > > Proxy Error. -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven > > with the -e switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug > > logging. > > [ERROR] > > [ERROR] For more information about the errors and possible > > solutions, please read the following articles: > > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/M > > ojoExecutionException > > [ERROR] > > [ERROR] After correcting the problems, you can resume the build > > with the command > > [ERROR] mvn -rf :org.apache.sling.settings > > channel stopped > > > >
Re: Build failed in Jenkins: sling-trunk-1.7 #2409
It seems we're getting a lot of failures due to deploy problems. Do we really need to deploy the snapshots? (as I doubt that we can fix the deployment problems) Or can we maybe ignore the error if deployment fails? Regards Carsten Am 04.10.15 um 13:07 schrieb Apache Jenkins Server: > Waiting for Jenkins to finish collecting data > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project org.apache.sling.settings: Failed to deploy metadata: Could not > transfer metadata > org.apache.sling:org.apache.sling.settings:1.3.7-SNAPSHOT/maven-metadata.xml > 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/sling/org.apache.sling.settings/1.3.7-SNAPSHOT/maven-metadata.xml. > Return code is: 502, ReasonPhrase: Proxy Error. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :org.apache.sling.settings > channel stopped > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
