> I still have the original problem: e.g. I can't run the Travis jobs for my PR > and without all of them passing, I am hesitating to integrate my change: > https://github.com/apache/netbeans/pull/2707 - how do you guys do it, that > your Travis checks run?
If we still want to use Travis, someone with admin rights on Travis needs to migrate netbeans, netbeans-html4j, and netbeans-jackpot30 from travis-ci.org to travis-ci.com. https://docs.travis-ci.com/user/migrate/open-source-repository-migration#migrating-a-repository --Christian On Tue, Jan 26, 2021 at 4:30 AM Neil C Smith <[email protected]> wrote: > On Tue, 26 Jan 2021 at 01:47, Jaroslav Tulach <[email protected]> > wrote: > > I still have the original problem: e.g. I can't run the Travis jobs for > my PR > > and without all of them passing, I am hesitating to integrate my change: > > https://github.com/apache/netbeans/pull/2707 - how do you guys do it, > that > > your Travis checks run? > > I guess we don't, right now. There's quite a queue backlog at the > moment by the look of it. I don't see it getting any better. > Retriggering all or part of Travis jobs, checking logs, etc. is what > I'd normally be expecting to be doing during release, but it certainly > doesn't seem like something we'll be doing much of! > > > Anyway few thoughts, with respect to switching to GitHub actions: > > > > - 1st and foremost, ASF has to have a contract with provider of the CI > > solution! Unless I am mistaken ASF pays to Travis and as such we can run > such > > a huge NetBeans loads on Travis. ASF needs to do the same with GitHub > before > > we can fully use Actions. > > I'm not sure ASF pays to Travis - if so, the current issues and > configuration need some looking at! > > From the infra@ email linked earlier, the ASF GitHub account is a > sponsored enterprise level account as far as I know, so it is "paid". > It doesn't mean that ASF isn't already hitting the limits of what's > available. > > > - preferrably all of them, before the PR is merged. However, we don't > have to > > run them with every commit automatically. Simple `ant build` would be > enough > > for an automatic "ready to go" check. > > +1 to tests green to merge. Have argued for that multiple times. > But, we do need to look at what tests are actually reliable. eg. the > Java hints tests fail so much, that particularly if we don't have > ability to re-run them separately they're going to get annoying very > quickly. > > > - btw. shall not we reuse the ASF's own build infrastructure (e.g. > > `Jenkinsfile`) to run our pipeline tests? In general whoever donates a > CPU is a > > friend, right? > > In part I don't think there's a difference - both sponsored CPU's. > But we certainly shouldn't be adding to our use of resources without > also reviewing everything that's running on > https://ci-builds.apache.org/job/Netbeans/ > > Best wishes, > > Neil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
