On 2018-06-02 5:47 AM, Guillermo
González de Agüero wrote:
Hi,
If you read trough the ee4j-build mailing list, Oracle is
trying hard to get build scripts working for the donated
projects, specially GlassFish.
Oracle and the Eclipse Foundation are collaborating on moving all of
the builds to our Common Build Infrastructure. And thanks to some
generous donations/discounts from Red Hat and CloudBees we are in
the process of deploying CloudBees Jenkins Enterprise on OpenShift.
We're working hard to provide the community with a very solid,
scalable, and robust build infrastructure. Following the normal
Eclipse CBI approach, each project will get its own Jenkins master
so they can control their own build environments.
You can follow the conversation about this on
https://accounts.eclipse.org/mailing-list/ee4j-build
One word of caution about Travis: each GitHub organization gets a
limited number of free Travis instances. We've had times in the past
where organizations have needed more resources than the free stuff,
and build queues got quite slow as a result. We're investing a bunch
in Jenkins, so paying for extra Travis resources is not something we
intend to do.
HTH
Hi,
That's not for Oracle any more.
Eclipse Foundation has Jenkins pipelines and instances
already.
Members like Oracle or others may donate funds or even
HW, but they won't operate it.
|