Re: [papyrus-rt-dev] [Suggestion for 0.9.0] Split p2 and Product builds

[Christian Damus <give.a.damus@xxxxxxxxx>]

+1

I agree with all of Céline’s arguments and Charles's.

cW

On 14 October, 2016 at 12:06:37, charles+zeligsoft.com (charles@xxxxxxxxxxxxx) wrote:

It think that’s a good approach.

The RCP is really only necessary on an external facing site for releases and milestones, so we don’t need to build them that often, keeping in mind that there would be little need at the beginning of a release (milestone) cycle, as we can do our testing using the tester installation, and more at the end when we need to validate the RCP, along with the Oomph-based installations.

Sincerely,

Charles Rivet
Senior Product Manager, Papyrus-RT product lead

charles@xxxxxxxxxxxxx

On 2016.10.14, at 11:49 , Céline JANSSENS <celine.janssens@xxxxxxxxxxx> wrote:

Hi everyone,

During this release 0.8.0, I had a better overview of the user needs in terms of deliverables.

As you could see the Papyrus-RT-Master-Product job, takes long time and is very big (800 MB each build).

So I suggest to split it into 2 builds, the p2 which is still build every 15min and the RCP itself (which is the haviest part) to build and sign it every week for example.

Of course it could be run on demand if needed like it did so far.

If you have any remarks on this... let me know ;)

regards
Céline


[cid:image001.jpg@01D22642.65398090]

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

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