Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] HIPP dedicated job queue for Papyrus component

Hi,

As it happens, that’s one of the goals of the Neon refactoring effort:  to reduce the scope of the main Papyrus builds to the level of components/layers.  That includes component-level Gerrit builds that integrate test execution.  This should allow other (non-core) components’ builds to interleave with the main Papyrus builds.

Christian

On 10 February, 2016 at 07:36:23, LE FEVRE FRANCOIS (francois.le-fevre@xxxxxx) wrote:

Dear all,

I would like to know if the upcoming component architecture (for moka, robotml, sysml, designer), we could create a dedicated job queue for components.

Why?

Because a gerrit patch from Designer takes 3 mn, and perhaps 10mn for SysML.

While a gerrit from Papyrus could take more than 1h00.

 

Jobs associated with Papyrus core block the review process of the components.

Is there a way to parametize job queue to match with a pattern?

 

Thanks for your idea.

 

Francois.


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

Back to the top