[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [papyrus-rt-dev] Build infrastructure wiki questions
|
Note that we _will_ need an RCP for the 1.0 release. So it’s a good idea to think about this now…
Sincerely,
Charles Rivet Senior Product Manager, Papyrus-RT product lead
Hi. I finally had time to read the description of the build infrastructure at https://wiki.eclipse.org/Papyrus-RT/Developer_Guide/Builds, and I have a few questions:
First an RCP/Product newbie question here: if I wanted to package Papyrus-RT as a zip file to distribute, how would I do it? Are the "rcp" and/or "product" projects supposed to provide this? If not, do we have plans to do this?
Under "Integration Jobs" it says:
* Papyrus-RT-<Stream>-Product-Releases doesn publish and archive
Is that a "doesn't" or a "does"?
Under "Target Platforms", should the -Product path be updated to the updates/nighly/<Stream>?
Under "Triggering", it seems to me that codegen is a bit of a special case, because changes to plugins/xtumlrt/... should trigger a codegen build as well, or is this supposed to be handled by triggering the codegen build from a (not yet existing) xtumlrt build?
In fact, shouldn't there be triggering dependencies for the Gerrit jobs according to the components? E.g., shouldn't a gerrit build of "Core" trigger a build of "Tooling", "Codegen", etc?
-- Ernesto Posse Zeligsoft
_______________________________________________ papyrus-rt-dev mailing list papyrus-rt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail