Hello everyone (Gavin, Sander especially),
Over the last few days again the queue for GA got completely blocked. We
have 2-4 jobs in parallel max and our speed of merging PRs dropped to 1 per
4-5 hours.
We really need to find out to solve the problem together with Github
account that we were supp
Jarek>workflows in/progress/queued per project and they clearly show the
Jarek> situation is getting worse by day
The chart suggests that Pulsar, Spark and Airflow are the top contributors
to the queue.
I filed issues to Pulsar ( https://github.com/apache/pulsar/issues/9154 )
and Spark ( https://i
Thanks, for that!
I think this is not a "permanent" solution and the data is a bit flawed :( .
I do not think it's the fault in Pulsar/Spark per se. I think it is very
hard to request from them to do any limits, even if we do it now this might
again go ballistic tomorrow. And I think it's very un
I am also very sad that our CI is so slow. After the obvious technical
problems, the fact that the project is developing very slowly is also a
problem for the health of the community.
Among active members of the community, this causes reluctance to continue
working. I also fell victim and recently
Jarek>But let's see, maybe it will work !
That is exactly my feeling. I guess they have already optimized the build,
however, let's see.
At least, 24 Spark jobs (22 of them are "master") are queued:
https://github.com/apache/spark/actions?query=is%3Aqueued
If they commit too fast, they might do b
On Fri, Jan 8, 2021, 12:08 PM Jarek Potiuk wrote:
>
> There is one problem with the charts, They are flawed. They show
> 'workflows' not 'jobs' and one workflow might mean many jobs :(. For
> example the big number of workflows you can see in Airflow yesterday come
> from "Label when reviewed" w
> On Jan 8, 2021, at 12:11 PM, Kamil Breguła wrote:
> I would be happy if we could get a tip on what we can do next to improve
> our CI as well as keep our community happy. Is there any solution that
> complies with the Apache policy and is more stable? In Airflow, we've
> already tried sever
> We should be able to make an efficient query via GraphQL API right? I found
> the REST API for actions to be a little underwhelming.
That was the first thing I checked when we started looking at the stats.
Unfortunately last time that I checked (and I even opened an issue for that
to
Github sup
Hi,
On Fri, 8 Jan 2021 12:49:03 -0800
Chris Lambertus wrote:
>
> Have you considered the internal and fully supported ASF Jenkins
and/or Buildbot infrastructure? Infra has little control over the free
open source offerings, but we have significantly more resources we can
bring to bear on own on
It must have been many, many years since you last looked at Jenkins.
They've supported pipelines (stored in your code repository) since at
least 2015 or so.
https://www.jenkins.io/doc/book/pipeline/
On Fri, 8 Jan 2021 at 15:17, Antoine Pitrou wrote:
>
>
> Hi,
>
> On Fri, 8 Jan 2021 12:49:03 -080
Hi Antoine,
Am 08.01.21 um 22:17 schrieb Antoine Pitrou:
>> What are the gaps in the ASF CI systems that are pushing people onto
> less viable platforms such as GA?
>
> While being a PMC and core developer for Apache Arrow, I'm going to
> give a personal opinion here:
>
> - Jenkins I think many p
Le 08/01/2021 à 22:29, P. Ottlinger a écrit :
> Hi Antoine,
>
> Am 08.01.21 um 22:17 schrieb Antoine Pitrou:
>>> What are the gaps in the ASF CI systems that are pushing people onto
>> less viable platforms such as GA?
>>
>> While being a PMC and core developer for Apache Arrow, I'm going to
>>
Let me just answer from my side.
Personally - I hate and love Jenkins at the same time. I am a Jenkins user
and developer for 15 years or so. I even developed mobile app plugins for
jenkins and we run our own jenkins farm for mobile app CI. but some 5 years
ago we switched to GitLab which was so
One of the biggest ways that Traffic Control benefits from GH Actions is
that workflows run on forks, which only counts towards that user's 20
runner limit. As a result, our contributors have less cleanup work to do by
the time they open a PR.
Since running on all forks is not an option with Jenki
I used to love gradle and Jenkins and started to hate it. Once you move to
python/javascript world, suddenly stuff that take you days in Java/Gradle
take hours in Python/Javascript. And it is amplified in case of CI where
you do not need to have an enterprise-grade system but a bunch of scripts
to
On Fri, Jan 8, 2021 at 10:45 PM Zach Hoffman wrote:
> One of the biggest ways that Traffic Control benefits from GH Actions is
> that workflows run on forks, which only counts towards that user's 20
> runner limit. As a result, our contributors have less cleanup work to do by
> the time they open
On Fri, 8 Jan 2021 at 16:04, Jarek Potiuk wrote:
>
> Github Actions, GitLab, TravisCI. even Cloud Build are s much easier
> to work with and get your stuff done.
The multiple threads about how shitty those are in practice for your
needs seem to indicate otherwise. Security and easy learning
Oops, forgot the footnote:
[1]: https://github.com/kubernetes/test-infra/tree/master/prow
On Fri, 8 Jan 2021 at 16:15, Matt Sicker wrote:
>
> On Fri, 8 Jan 2021 at 16:04, Jarek Potiuk wrote:
> >
> > Github Actions, GitLab, TravisCI. even Cloud Build are s much easier
> > to work with and g
> One of the biggest ways that Traffic Control benefits from GH Actions is
> > that workflows run on forks, which only counts towards that user's 20
> > runner limit. As a result, our contributors have less cleanup work to do
> by
> > the time they open a PR.
> >
>
> How come? Most people in Airlfo
> On Jan 8, 2021, at 1:33 PM, Jarek Potiuk wrote:
>
> We moved to GA when we had exactly the same troubles with
> Apache-organisation run Travis. more than a year ago we got in very much
> the same situation and GA seemed like an easy win for us.
The ASF does not run Travis. We pay a large
> On Jan 8, 2021, at 1:45 PM, Zach Hoffman wrote:\
> Since running on all forks is not an option with Jenkins, that's where my
> preference comes from. Jenkins is still useful for jobs that don't need to
> run on forks, (e.g., periodically checking for Go version updates and
> opening a PR if
21 matches
Mail list logo
