Indeed, a dedicated organization could work around the issue. Note that given 
the way Travis is changing, I would advise to prepare to switch to another 
build system now rather than waiting to be forced to do so on the next policy 
change (which seems to happen frequently).

The Eclipse Foundation offers a Jenkins based CI, which integrates seamlessly 
with GH (build on commit push, PR builds etc..). See 
https://wiki.eclipse.org/CBI#CI_Environment_.28Jenkins.29 
<https://wiki.eclipse.org/CBI#CI_Environment_.28Jenkins.29> and 
https://wiki.eclipse.org/Jenkins <https://wiki.eclipse.org/Jenkins>

Cheers,

Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation 
and Collaboration

> On 27 Nov 2020, at 18:45, Jonah Graham <jo...@kichwacoders.com> wrote:
> 
> In the past there was a similar issue and IIRC the solution was to have a new 
> github organization so that not everything was shared together. There are 
> already a number of Eclipse organizations (in addition to the main eclipse 
> one).
> 
> HTH,
> Jonah
> 
> On Fri., Nov. 27, 2020, 12:33 Mezzasalma, Claudio, 
> <claudio.mezzasa...@eurotech.com <mailto:claudio.mezzasa...@eurotech.com>> 
> wrote:
> Hello all,
> In Eclipse Kapua we're using Travis as our CI server. However, it looks like 
> in the past few weeks the queue in the Eclipse account increased 
> significantly, leading to very long waiting time (the average waiting time 
> for today, November 27th, 2020 is 2392 minutes while yesterday was 2248 
> minutes -- data from [1]). Moreover, Travis announced they're moving to a 
> different usage policy for free account (announcement [2] and follow up [3]) 
> that is basically preventing us, as single committers, to use our personal 
> forks to do CI on pull requests before merging the code in the main branch, 
> something we were doing to reduce the amount of jobs in the whole Eclipse 
> account on Travis.
> So, while we wait for a reply from the Travis staff who could offer some free 
> credits for our personal forks, I would like to ask for any suggestion from 
> our community on how we could approach this issue.
> 
> Thanks everyone!
> 
> [1] https://travis-ci.org/github/eclipse?tab=insights 
> <https://travis-ci.org/github/eclipse?tab=insights>
> [2] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing 
> <https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing>
> [3] https://blog.travis-ci.com/oss-announcement 
> <https://blog.travis-ci.com/oss-announcement>
> --
> Claudio Mezzaslma | Eurotech
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> <mailto:cross-project-issues-dev@eclipse.org>
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Attachment: signature.asc
Description: Message signed with OpenPGP

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to