| Re: [mdt-papyrus.dev] resolving dependencies |
|
Hi, Ø
Intermediate poms Please feel free to propose a prototype for this and push it to Gerrit. We’ll see how much it improves the performances. If it gives good improvements we’ll consider integrating it, but I fear that it will also
introduce more complexity. Each intermediate pom makes it harder to configure, update, fix or manipulate the build in general (Especially when POMs are not stored in an Eclipse project, such as the Documentation pom) Ø
Gerrit OK Camille De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LE FEVRE FRANCOIS Dear all, Previously, Camille improves the build time on gerrit job The builds are mostly back to normal, with a few changes: -
Gerrit now builds everything in a single pass (Rather than 4 separate builds)
o
Pro: It is a little bit faster (~38 minutes vs ~42 minutes)
o
Con: It takes 25 minutes to resolve *all* dependencies before actually compiling anything.
I would like to propose two methods to improve the build time: Intermediate poms In order to help maven to compute the reactor build order, we could use intermediate poms that groups plugins that shared a functional unit. For instance, we could create a pom for the different ../../plugins/infra/org.eclipse.papyrus.infra.elementtypesconfigurations plugins that will hold a modules paragraphe. https://bugs.eclipse.org/bugs/show_bug.cgi?id=470489 Gerrit For the specific gerrit job, I have noticed that we call tycho-source-plugin and tycho-source-feature-plugin Perhaps we could switch these plugins into a dedicated profile in order not to run them for the specific gerrit job? https://bugs.eclipse.org/bugs/show_bug.cgi?id=470490 It is a proposition. Thanks for your advice. Francois
|
