Harsh "no" indeed - I understand where it comes from as I am looking from
my project perspective.
But maybe instead of binary yes/no answer - we can think about some
compromise/temporary solution (for a week or so while we run the release
and try to migrate out to another CI).
Maybe Increasing jus
On Mon, Jul 22, 2019 at 2:20 AM Jarek Potiuk
wrote:
> Hello Everyone (especially the infrastructure),
>
> Can we increase a number of workers/jobs we have per project now?
> Decreasing it to 5 (which I believe is the case) is terrible for us now
> We are nearing 1.10.4 release with Airflow and i
Thanks for looking and analysis :). Very correct.
However this is a special case actually. It only builds it that long
because we have a change in this branch that requires rebuilding more
layers of the image. In this case we add mysql dependencies in a different
way and we rebuild the whole stage
Hi Mark & Gavin,
Any issues to report on JDK 13 , would like to hear the status as we are
now in rampdown phase 2 ?
**OpenJDK builds *- JDK 13 Early Access build 30 **is now available **at
: - jdk.java.net/13/*
* Per the JDK 13 schedule [1], we are now in Rampdown Phase Two.
o For mo
Jarek>Decreasing it to 5 (which I believe is the case) is terrible for us
now
Jarek>We are nearing 1.10.4 release with Airflow and if we have more than
one PR
Jarek>in the queue it waits for several hours to run!
I see 5 "pre-test" Travis jobs take 5-8 minutes each, and all the time is
basically
Hello Everyone (especially the infrastructure),
Can we increase a number of workers/jobs we have per project now?
Decreasing it to 5 (which I believe is the case) is terrible for us now
We are nearing 1.10.4 release with Airflow and if we have more than one PR
in the queue it waits for several ho
