[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [papyrus-rt-dev] Hudson builds fail on bogus time-out error
|
+1.
That can be done into the TP files with a specific property like in Papyrus : transfer.protocol=”file” or “http”
By default it would be “http”, and in the jobs, we can override it to “file”.
It seems not too difficult to put in place.
Céline
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Christian Damus
Envoyé : mercredi 5 octobre 2016 16:57
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Hudson builds fail on bogus time-out error
Now it looks like we just have some kind of severe performance problem in accessing
download.eclipse.org via HTTP: fetching the metadata from p2 repositories hosted there is extremely slow. I’m working on generation of targets localized for use on
Eclipse.org that access the downloads via the local filesystem, as is done in Papyrus. The build would automatically detect when it is running in the HIPP on
Eclipse.org to activate that option.
On 5 October, 2016 at 08:47:30, Christian Damus (give.a.damus@xxxxxxxxx) wrote:
It appears that we now have Gerrit builds failing on a time-out error accessing the latest successful build results of the Papyrus Developer component:
I don’t think that anything has changed in the Papyrus builds that could cause this. Is it possible that today's plug-in installations and/or
restart of the Papyrus-RT HIPP could have broken HTTP connections to the other HIPPs at
eclipse.org?
And I don’t suppose it will be just the Gerrit builds that fail, but the main component and product builds, too, because they all use the same
target-platform files. Papyrus has two forms of every TP, one using HTTP access and one using local disk access for use on the Hudson build servers. Should we be doing the same? I have no trouble accessing the required resources in the Papyrus Hudson instance
from home; it’s only our builds that are timing out.
This would be another thing to account for in the single-sourcing of TPs for the build and Oomph setups for the developers.
|
BEGIN:VCARD
VERSION:2.1
X-MS-SIGNATURE:YES
N;LANGUAGE=fr;CHARSET=Windows-1252:Céline;JANSSENS
FN;CHARSET=Windows-1252:JANSSENS Céline
ORG:ALL4TEC
TITLE;CHARSET=Windows-1252:Ingénieur d'Etude Papyrus Support Manager
TEL;WORK;VOICE:+33 2 44 47 23 23
ADR;WORK;PREF;ENCODING=QUOTED-PRINTABLE:;;Parc CERES Bat. L=0D=0A=
2 rue Ferdinand Buisson;CHANGE;;53810;France
LABEL;WORK;PREF;ENCODING=QUOTED-PRINTABLE:Parc CERES Bat. L=0D=0A=
2 rue Ferdinand Buisson=0D=0A=
53810 CHANGE
X-MS-OL-DEFAULT-POSTAL-ADDRESS:2
EMAIL;PREF;INTERNET:celine.janssens@xxxxxxxxxxx
X-MS-OL-DESIGN;CHARSET=utf-8:<card xmlns="http://schemas.microsoft.com/office/outlook/12/electronicbusinesscards"; ver="1.0" layout="left" bgcolor="ffffff"><img xmlns="" align="fit" area="16" use="cardpicture"/><fld xmlns="" prop="name" align="left" dir="ltr" style="b" color="000000" size="10"/><fld xmlns="" prop="org" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="title" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="telwork" align="left" dir="ltr" color="d48d2a" size="8"><label align="right" color="626262">Bureau</label></fld><fld xmlns="" prop="email" align="left" dir="ltr" color="d48d2a" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="addrwork" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/></card>
REV:20160907T143407Z
END:VCARD
