|Re: [ee4j-pmc] EE4J build migration to Eclipse - Requirements|
The Glassfish project is a similar tech spec.
As a data point. We run our Jenkins CI on an Amazon AWS t2-xlarge – 4vcpus + 16 GB RAM.
Jenkins Jobs are running with -Xmx4G but also this will spawn maven and GlassFish instances.
We found if memory is constrained builds will fail and leave a mess which needs manual clean up.
.m2 repo is of the order 5.5GB HDD Space
Gut feeling is RAM is limited from the specs you provided in the document.
Greetings EE4J PMC (cross-post to ee4j-build),
The Eclipse IT & Release Engineer teams have been drafting a plan to incorporate the ee4j project builds into Eclipse's build farm (otherwise known as Eclipse CBI). An overview of CBI, as well as the migration plan, is below.
It's a work in progress for sure, and we hope to use the document to kickstart the discussion on the build (and test) requirements that each project has.
At a high level, what we're looking for is:
1. Do you think the Eclipse CBI will work for your project?
2. If so, what are each projects' requirements (see table under EE4J Build Requirements). What are you using today?
3. If not, what are we missing?
Back to the top