René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"CI: Reduce unnecessary jobs","articleBody":"We currently have 3 workflows that run as part of the CI, and they run on both `push` and `pull-request`.\r\n\r\n- codeql.yml: \r\n  - Basic sanity check of the CodeQL behavior. \r\n  - Splits into 3 jobs of up to 9 minutes. \r\n  - Hopefully this will improve soon with https://github.com/github/codeql-action/pull/172 and similar changes\r\n\r\n- pr-checks.yml:\r\n  - Code quality checks\r\n  - Splits into 5 jobs of less than 30 seconds\r\n\r\n- integration-testing.yml:\r\n  - Extensive coverage of cross-feature behavior.\r\n  - Splits into 19 jobs of between 5 and 15 minutes.\r\n  - https://github.com/github/codeql-action/pull/172 is planning to add 21 additional jobs\r\n\r\nAll those parallel jobs compete for the same resources. Running them twice means that each push we are running 27x2 -\u003e 54 jobs, filling up the queue.\r\n\r\n**Proposal**\r\n1. Change `pr-checks.yml` to be only on `push` (maybe rename to `linting`?)\r\n2. Change `codeql.yml` to be on `push` only for `main` and `v1`, and `pull-request` for all.\r\n3. Change `integration-testing` to be on  `pull-request` and only on push for `main` and `v1`\r\n4. 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.\r\n    * This is the strategy I am hoping to adopt for https://github.com/github/codeql-action/pull/172\r\n\r\nThis would avoid duplication of jobs without reducing the coverage we get.","author":{"url":"https://github.com/marcogario","@type":"Person","name":"marcogario"},"datePublished":"2020-09-11T12:08:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/182/codeql-action/issues/182"}