[cross-project-issues-dev] Travis CI and Eclipse Projects build

[Codutti, Alberto]

Hi all,

I’m a committer of the Eclipse Kapua project.

We use Travis CI as a continuous integration tool for branches and pull requests alongside Eclipse Jenkins.

In the last few months (and especially in the last few weeks) we noticed an increased time that it takes to actually start a build. Now we are at the point in which it take 2-3 hours to start a build after being enqueued.
To try to troubleshooting the problem, we reached Travis CI support.
After a couple of mail exchange the problem came out.
It turns out that Travis CI is free for opensource projects but allows only 5 jobs to run concurrently per each organization. This means that all Eclipse projects that are using Travis CI share this limit of 5 concurrent jobs, explaining the long time waiting an available executor.

Support also reported that on 2018-08-28 09:32:45 UTC there were 226 jobs waiting enqueued for Eclipse organization.

Is there any plan on the Eclipse side to get around this problem?
Do we need to find other solutions? Eclipse Jenkins could be one, but it allows only 2 concurrent jobs.

Best Regards,

Alberto Codutti
Software Engineer – R&D – Eurotech Italy
email: ***@eurotech.com<mailto:***@eurotech.com>

EUROTECH
Imagine.Build.Succeed.
[ind Us on Facebook]<http://www.facebook.com/pages/Eurotech/300969971064>[ollow Us on Twitter: EurotechFan]<http://twitter.com/EurotechFan>[urotech on linkedin]<http://www.linkedin.com/company/38780>[urotech on slideshare]<http://www.slideshare.net/Eurotechchannel>[urotech on YouTube]<http://www.youtube.com/EurotechChannel>[urotech on google+]<https://plus.google.com/109070752122324620778/posts>[urotech Blog]<http://blog.eurotech.com/en>
ITALY - Eurotech S.p.A. - Via Fratelli Solari, 3/a | 33020 Amaro UD | Tel. [phone] | Fax [phone] |
Cap. Soc. 8.878.946,00 € I.V. | P.IVA / C.F.: IT 01791330309 | REA Udine 196115
www.eurotech.com<http://www.eurotech.com/>
____________________________________

Il presente messaggio ed ogni suo allegato sono da intendersi inviati esclusivamente agli effettivi destinatari, possono contenere informazioni riservate o confidenziali e potrebbero essere soggetti a restrizioni legali. Se avete ricevuto questo messaggio per errore vi invitiamo a darne immediata notifica al mittente e cancellarlo dal vostro sistema. Qualsiasi altro uso di questo messaggio da parte vostra e' strettamente proibito.
This e-mail, and any file attached to it, is meant only for the intended recipient of the transmission, may contain information which is confidential or privileged and may be a communication privileged by law. If you have received it in error, please notify the sender immediately and delete the original from your system. Any other use of this e-mail by you is strictly forbidden.
____________________________________
Per favore, pensate all’ambiente prima di stampare questa e-mail. Please consider the environment before printing this e-mail

[Denis Roy]

Hi Alberto,

As perhaps mentioned, I can see two options:

1. We use a specific GH Organization for your project (eclipse-kapua
would be the name). That would give you all 5 Travis executors.

2. Use our CBI (Jenkins) which gives you 2 dedicated executors.


You can file a bug against Eclipse Foundation > Community > Github for
1. and Eclipse Foundation > Community > CI-Jenkins for 2.


You can also subscribe to the CBI-dev mailing list
(https://accounts.eclipse.org/mailing-list/cbi-dev) for build-specific
discussions.


Denis

Hi all, 
 
I’m a committer of the Eclipse Kapua project.
 
We use Travis CI as a continuous integration tool for branches and
pull requests alongside Eclipse Jenkins.
 
In the last few months (and especially in the last few weeks) we
noticed an increased time that it takes to actually start a build. Now
we are at the point in which it take 2-3 hours to start a build after
being enqueued. 
To try to troubleshooting the problem, we reached Travis CI support.
After a couple of mail exchange the problem came out.
It turns out that Travis CI is free for opensource projects but allows
only 5 jobs to run concurrently per each organization. This means that
all Eclipse projects that are using Travis CI share this limit of 5
concurrent jobs, explaining the long time waiting an available executor. 
 
Support also reported that on 2018-08-28 09:32:45 UTC there were 226
jobs waiting enqueued for Eclipse organization.
 
Is there any plan on the Eclipse side to get around this problem?
Do we need to find other solutions? Eclipse Jenkins could be one, but
it allows only 2 concurrent jobs.
 
Best Regards,
 
Alberto Codutti*
*Software Engineer – R&D – Eurotech Italy
*EUROTECH*
Imagine.Build.Succeed.
ind Us on Facebook
<http://www.facebook.com/pages/Eurotech/300969971064>ollow Us on
Twitter: EurotechFan <http://twitter.com/EurotechFan>urotech on
linkedin <http://www.linkedin.com/company/38780>urotech on slideshare
<http://www.slideshare.net/Eurotechchannel>urotech on YouTube
<http://www.youtube.com/EurotechChannel>urotech on google+
<https://plus.google.com/109070752122324620778/posts>urotech Blog
<http://blog.eurotech.com/en> 
ITALY - Eurotech S.p.A. - Via Fratelli Solari, 3/a | 33020 Amaro UD |
Tel. [phone]  | Fax [phone] |
Cap. Soc. 8.878.946,00 € I.V. | P.IVA / C.F.: IT 01791330309 | REA Udine 196115
*www.eurotech.com <http://www.eurotech.com/>
*____________________________________
Il presente messaggio ed ogni suo allegato sono da intendersi inviati
esclusivamente agli effettivi destinatari, possono contenere
informazioni riservate o confidenziali e potrebbero essere soggetti a
restrizioni legali. Se avete ricevuto questo messaggio per errore vi
invitiamo a darne immediata notifica al mittente e cancellarlo dal
vostro sistema. Qualsiasi altro uso di questo messaggio da parte
vostra e' strettamente proibito.
This e-mail, and any file attached to it, is meant only for the
intended recipient of the transmission, may contain information which
is confidential or privileged and may be a communication privileged by
law. If you have received it in error, please notify the sender
immediately and delete the original from your system. Any other use of
this e-mail by you is strictly forbidden.
____________________________________
*Per favore, pensate all’ambiente prima di stampare questa
e-mail. Please consider the environment before printing this e-mail*
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[Codutti, Alberto]

HI Denis,

Thank you for the reply.

We’ve already stumbled upon the idea of requesting a dedicated GitHub organization.
We also see that other projects have requested info about that.

Do you have any idea on how long it takes to that process to be completed? If it takes long, we might use both options.

Ps: the discussion has moved to Incubation Mailing list by Gunnar Wagenknecht, but you answered to the Cross Project one. I don’t know if it is ok continuing on this mailing list.

Best Regards,

Alberto Codutti | R&D | EUROTECH

From: <cross-project-issues-dev-***@eclipse.org> on behalf of Denis Roy <***@eclipse-foundation.org>
Reply-To: Cross project issues <cross-project-issues-***@eclipse.org>
Date: Friday, August 31, 2018 at 8:48 PM
To: "cross-project-issues-***@eclipse.org" <cross-project-issues-***@eclipse.org>
Subject: Re: [cross-project-issues-dev] Travis CI and Eclipse Projects build


Hi Alberto,

As perhaps mentioned, I can see two options:

1. We use a specific GH Organization for your project (eclipse-kapua would be the name). That would give you all 5 Travis executors.

2. Use our CBI (Jenkins) which gives you 2 dedicated executors.



You can file a bug against Eclipse Foundation > Community > Github for 1. and Eclipse Foundation > Community > CI-Jenkins for 2.



You can also subscribe to the CBI-dev mailing list (https://accounts.eclipse.org/mailing-list/cbi-dev) for build-specific discussions.



Denis





On 2018-08-31 09:01 AM, Codutti, Alberto wrote:
Hi all,

I’m a committer of the Eclipse Kapua project.

We use Travis CI as a continuous integration tool for branches and pull requests alongside Eclipse Jenkins.

In the last few months (and especially in the last few weeks) we noticed an increased time that it takes to actually start a build. Now we are at the point in which it take 2-3 hours to start a build after being enqueued.
To try to troubleshooting the problem, we reached Travis CI support.
After a couple of mail exchange the problem came out.
It turns out that Travis CI is free for opensource projects but allows only 5 jobs to run concurrently per each organization. This means that all Eclipse projects that are using Travis CI share this limit of 5 concurrent jobs, explaining the long time waiting an available executor.

Support also reported that on 2018-08-28 09:32:45 UTC there were 226 jobs waiting enqueued for Eclipse organization.

Is there any plan on the Eclipse side to get around this problem?
Do we need to find other solutions? Eclipse Jenkins could be one, but it allows only 2 concurrent jobs.

Best Regards,

Alberto Codutti
Software Engineer – R&D – Eurotech Italy
email: ***@eurotech.com<mailto:***@eurotech.com>

EUROTECH
Imagine.Build.Succeed.
[ind Us on Facebook]<http://www.facebook.com/pages/Eurotech/300969971064>[ollow Us on Twitter: EurotechFan]<http://twitter.com/EurotechFan>[urotech on linkedin]<http://www.linkedin.com/company/38780>[urotech on slideshare]<http://www.slideshare.net/Eurotechchannel>[urotech on YouTube]<http://www.youtube.com/EurotechChannel>[urotech on google+]<https://plus.google.com/109070752122324620778/posts>[urotech Blog]<http://blog.eurotech.com/en>
ITALY - Eurotech S.p.A. - Via Fratelli Solari, 3/a | 33020 Amaro UD | Tel. [phone] | Fax [phone] |
Cap. Soc. 8.878.946,00 € I.V. | P.IVA / C.F.: IT 01791330309 | REA Udine 196115
www.eurotech.com<http://www.eurotech.com/>
____________________________________

Il presente messaggio ed ogni suo allegato sono da intendersi inviati esclusivamente agli effettivi destinatari, possono contenere informazioni riservate o confidenziali e potrebbero essere soggetti a restrizioni legali. Se avete ricevuto questo messaggio per errore vi invitiamo a darne immediata notifica al mittente e cancellarlo dal vostro sistema. Qualsiasi altro uso di questo messaggio da parte vostra e' strettamente proibito.
This e-mail, and any file attached to it, is meant only for the intended recipient of the transmission, may contain information which is confidential or privileged and may be a communication privileged by law. If you have received it in error, please notify the sender immediately and delete the original from your system. Any other use of this e-mail by you is strictly forbidden.
____________________________________
Per favore, pensate all’ambiente prima di stampare questa e-mail. Please consider the environment before printing this e-mail




_______________________________________________

cross-project-issues-dev mailing list

cross-project-issues-***@eclipse.org<mailto:cross-project-issues-***@eclipse.org>

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev