|[cross-project-issues-dev] Travis CI and Eclipse Projects build|
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.
ITALY - Eurotech S.p.A. - Via Fratelli Solari, 3/a | 33020 Amaro UD | Tel. +39. 0433 485411 | Fax
+39. 0433 485499 |
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
Back to the top