We currently have 3 workflows that run as part of the CI, and they run on both push and pull-request.

• codeql.yml:

  • Basic sanity check of the CodeQL behavior.
  • Splits into 3 jobs of up to 9 minutes.
  • Hopefully this will improve soon with Use smaller Plarform-Language packages when analyzing only one language #172 and similar changes

• pr-checks.yml:

  • Code quality checks
  • Splits into 5 jobs of less than 30 seconds

• integration-testing.yml:

  • Extensive coverage of cross-feature behavior.
  • Splits into 19 jobs of between 5 and 15 minutes.
  • Use smaller Plarform-Language packages when analyzing only one language #172 is planning to add 21 additional jobs

All those parallel jobs compete for the same resources. Running them twice means that each push we are running 27x2 -> 54 jobs, filling up the queue.

Proposal

1. Change pr-checks.yml to be only on push (maybe rename to linting?)
2. Change codeql.yml to be on push only for main and v1, and pull-request for all.
3. Change integration-testing to be on pull-request and only on push for main and v1
4. Ideally sort the jobs in integration-testing from the more likely to fail to the less likely to fail, and make the latter conditional on the former.
   • This is the strategy I am hoping to adopt for Use smaller Plarform-Language packages when analyzing only one language #172

This would avoid duplication of jobs without reducing the coverage we get.