Re: [jakarta.ee-community] Enabling Travis on repositories

[Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>]

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

El sáb., 2 jun. 2018 a las 10:07, Werner Keil (<werner.keil@xxxxxxxxx>) escribió:

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.

Werner

On Sat, Jun 2, 2018 at 9:54 AM, Guillermo González de Agüero <z06.guillermo@xxxxxxxxx> wrote:

Hi,

I expect Oracle to provide us Jenkins pipeline scripts when they are done. But for the time being, Travis compiles and tests our projects just fine ;)

El sáb., 2 jun. 2018 9:48, Werner Keil <werner.keil@xxxxxxxxx> escribió:

Hi,

Is Travis the CI tool of choice now at Eclipse?

Especially for Jakarta EE chaining builds for certain standards that are used by others looks extremely important and from what I read under https://stackoverflow.com/questions/22293444/chaining-builds-in-the-travisci Travis has never offered that.

So while having more than one build tool there's probably nothing wrong with, some or most Jakarta EE specs should also look into a proper Jenkins pipeline, which Eclipse Foundation offers (not sure about the scale for all the new Jakarta projects though?;-)

Werner

On Sat, Jun 2, 2018 at 8:25 AM, Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:

Hi Guillermo,

just create a Bugzilla issue for the Eclipse Webmaster Team. Just make sure to select the category "Community -> GitHub". See the issue we created for the JAX-RS API project.

Christian

Am Fr., 1. Juni 2018 um 19:20 Uhr schrieb Guillermo González de Agüero <z06.guillermo@xxxxxxxxx>:

Hi all,

Some repositories have already enabled Travis. Soteria contains the .travis.yml but Travis is not configured to run and I don't have permissions to set it up. I guess more project will face the same issue, hence I'm posting this for advice.

Who should we reach to enable Travis on repositories?

Regards,

Guillermo González de Agüero

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