| Re: [papyrus-rt-dev] Multiple Papyrus-RT-Master-Product builds for each merged commit |
|
Hi Peter,
As far as I remember, The Core build triggers Tooling and Codegen jobs. Codegen and Tooling jobs both trigger the Product
job. So you are right, every time a modification is done on the core, then tooling and codegen jobs are triggered. And both
trigger the Product job. It has been whished that the Product should be up to date at least every 15 minutes. That is why, Core, Tooling and Codegen
Build check for modification every 15 minutes. Product job is based on Core, Tooling and Codegen sub-repos as it builds the “releng” Target platform.
A solution would be not to trigger the product directly from the Components builds, but on a regular basis, 30 minutes
seem reasonable. In addition, the RCPTT is being extract from the Product Build to decrease the time of the Product Build to 17-20 minutes.
Any remarks on this suggestion ?
Regards Céline
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Peter Cigéhn Hi, I have a question regarding the new build system. I find a bit confusing knowing when it is safe to start upgrading and testing a merged commit. Almost all the latest
commits that I have been merged and which I wanted to test, and for which I then I have checked the builds when they are finished, have been triggering the final Papyrus-RT-Master-Product to be built (at least) twice. I guess that it is related to that a commit contains changes, e.g. for both core and tooling, which triggers both these builds (in parallell). When these are finished,
they trigger the final product build. And then when the core is finished that triggers yet another tooling build, which in its turn triggers a product build again. In more or less all cases I have seen, the second product build has gotten stuck in the queue
also since you cannot build two product builds in parallell. Is it safe to test already after the first product build have finished, or do I always have to wait for the second one to finish? More or less always having to wait
for two product builds feels pretty time consuming (since each takes up to half an hour to complete). Is the setup of the build system really correct? Why is both core and tooling triggered at the first step? If you only trigger building core, which then triggers tooling,
which finally triggers product, then you don't have tooling and product building twice. Any comments? Is this just how it is supposed to work? And that I (to be on the safe side) always needs to wait for the second (or whatever number the final will be)
build before I can upgrade safely? /Peter Cigéhn |
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
