Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Solved — Re: Weird new build failures

Hi Benoit & Christian,

Thank you very much for that help and for restoring the builds! 

I updated a few days ago also the release target for Papyrus, used for Quality job:  https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Quality/
Thanks to last Christian's update, it came back to green. This is a daily job, that runs a bunch of quality tools (findbugs, checkstyle, etc.), and generates a report from that quality assessment. It is worth checking from time to time this report.

Cheers
Rémi

2017-01-16 8:22 GMT+01:00 MAGGI Benoit <Benoit.MAGGI@xxxxxx>:

Hi Christian,

 

There was an http/https problem that was reported on cross-project [1].

(Basically browser are moving forward to enforce https everywhere.)

 

So I believe your guess is correct and some option may have been activated to enforce https over http.

 

 

Regards,

Benoit

1 : https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14054.html

 

 

De : papyrus-rt-dev-bounces@eclipse.org [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Christian Damus
Envoyé : samedi 14 janvier 2017 14:54
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : [papyrus-rt-dev] Solved — Re: Weird new build failures

 

Hi, Team,

 

With the clarity of a cool, crisp Winter morning, I found the cause of the problem:  our TPDs used the HTTP protocol to access the Papyrus HIPP.  They must use HTTPS; I suppose Eclipse.org turned on some new security constraints within their network.  I have regenerated the TPs and all should now be well again.

 

Until the next Friday the 13th.  😱


Cheers,

Christian


On Jan 13, 2017, 17:17 -0500, Christian Damus <give.a.damus@xxxxxxxxx>, wrote:

Hi, Team,

 

Our builds are failing with a new kind of error that is absolutely crazy-making.  It seems that our builds can no longer access the p2 repository of the latest successful Papyrus-Neon-Developer build, although they can access the latest successful Papyrus-Neon and Papyrus-Neon-Extra builds without trouble.

 

From the build console:

 

 
[INFO] Adding repository http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository
[WARNING] Failed to access p2 repository http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository, use local cache. Neither http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/content.jar nor http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/content.xml found.
[INFO] Adding repository file:/home/data/httpd/download.eclipse.org/modeling/emf/compare/updates/logical/emf.compare/nightly/latest
[INFO] Adding repository file:/home/data/httpd/download.eclipse.org/modeling/emf/compare/updates/egit-logical/nightly
[INFO] Adding repository file:/home/data/httpd/download.eclipse.org/cbi/updates/license
[INFO] Adding repository file:/home/data/httpd/download.eclipse.org/tools/orbit/downloads/drops/R20150519210750/repository
[INFO] Adding repository file:/home/data/httpd/download.eclipse.org/modeling/mdt/papyrus/components/designer/1.0.1_papyrus-designer-neon_133
[INFO] Adding repository file:/home/data/httpd/download.eclipse.org/elk/updates/releases/0.1.0
[INFO] Adding repository file:/home/data/httpd/download.eclipse.org/modeling/mdt/papyrus/updates/nightly/neon
[INFO] Fetching p2.index from https://hudson.eclipse.org/papyrus/job/Papyrus-Neon/lastSuccessfulBuild/artifact/repository/ (172B)
[INFO] Fetching p2.index from https://hudson.eclipse.org/papyrus/job/Papyrus-Neon/lastSuccessfulBuild/artifact/repository/ (172B)
[INFO] Fetching p2.index from https://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Extra/lastSuccessfulBuild/artifact/repository/ (172B)
[INFO] Fetching p2.index from https://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Extra/lastSuccessfulBuild/artifact/repository/ (172B)
[INFO] Adding repository file:/home/hudson/genie.papyrus-rt/.hudson/jobs/Papyrus-RT-Master-Product/lastSuccessful/archive/repository
[INFO] Resolving dependencies of MavenProject: org.eclipse.papyrusrt:org.eclipse.papyrusrt.umlrt.tooling.diagram.common:0.8.0-SNAPSHOT @ /jobs/genie.papyrus-rt/Papyrus-RT-Gerrit-Tooling/workspace/source/plugins/umlrt/tooling/org.eclipse.papyrusrt.umlrt.tooling.diagram.common/pom.xml
[INFO] o.h.m.e.h.MavenExecutionResultHandler - Build failed with exception(s)
[INFO] o.h.m.e.h.MavenExecutionResultHandler - [1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: Artifact not found: http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/artifacts.xml.xz.
[DEBUG] Closing connection to remote
[ERROR] Internal error: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: Artifact not found: http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/artifacts.xml.xz. -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: Artifact not found: http://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Developer/lastSuccessfulBuild/artifact/repository/artifacts.xml.xz.

 

 

So, as you can see, the build thinks it can’t get the metadata for the developer build.  However, I have no trouble from my computer using the same URL to access that repository, and it like it has all the same metadata files as the repositories that the build can access.  The p2.index files, in particular, are identical.

 

Any ideas?   I re-started the Papyrus-RT HIPP instance, but that didn’t help.  Does the server machine that hosts our HIPP need to be restarted?  Thinking maybe something is borked in the networking stack.

 

The only meaningful difference that I can think of between these Papyrus build repositories is that we actually get the Papyrus-Neon and Papyrus-Neon-Extra builds by re-direction through a composite repository on the build server that is specified by a file-scheme URL.  Our TPs reference the developer build by an http-scheme URL directly to the Hudson job because Papyrus doesn’t publish the developer builds on the download server.  But, in the end, it’s all HTTP anyways.

 

This will cause all of our builds, both the Gerrit and the production builds, to fail until it is resolved.


Cheers,

Christian


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev




--
Remi Schnekenburger

Senior Software Architect / General Manager
EclipseSource Paris

Email: rschnekenburger@xxxxxxxxxxxxxxxxx
Web: http://eclipsesource.com/paris
Mobil: +49 89 21 555 30 - 25 
Phone: +49 89 21 555 30 - 25
Fax: +49 89 21 555 30 - 19

EclipseSource France SAS
7 rue de la Croix Martre
91873 Palaiseau

General Manager: Remi Schnekenburger

Back to the top