Unfortunately I can't get to content of that message.
Now I'm only halfway through job conversion.
I thing we need to define which checks must be run for every PR and
which are needed on daily basis.
Some jobs seems that they can be merged together - "Test java.hints
batch 1 with nb-javac on Java 13" and "Test java.hints batch 2 with
nb-javac on Java 13" use same setup. By merging them together we can
save one build step.
Jobs can have dependency defined, matrix tests can limit maximum
parallel processes run. By this mean we can serialize jobs and limit
used runners.
I added Windows build to test PHP modules because of some issues in
handling different path separator. It can be run on schedule just to
verify it still works.
Regards,
Tom
On 25. 01. 21 11:59, Lars Bruun-Hansen wrote:
For those on users@infra, this email worth a read -
https://lists.apache.org/thread.html/r748a0e034256f22c240d6a00cece0e005724a3173cfbb478b548d979%40%3Cusers.infra.apache.org%3E
This is a disturbing read !
Some notes based on my experience with GitHub Actions.
Optimization ideas:
- Using some form of git diff to figure out which modules were changed
in the commit and then run tests only for that / those modules. I
think Apache Airflow has done something along those lines, not sure.
- Manually triggered workflows for now. The person who wishes to merge
can then trigger the workflow on a need basis. (obviously not a good
long term solution)
- a full-blown CI run only once per day (using cron trigger)
- never ever use Windows or MacOS unless you _absolutely_ need to.
They start a lot slower (possibly there are fewer such Runners?) but
in my experience they also execute the same flow *a lot* slower than
their Linux counterpart.
Security:
Really perplexed with the email from the Airflow project. It seems
really severe issues.
/Lars
