Speed up and simplify PR pipelines #4219
Draft
+56
−31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Problem: Our CI run on PRs run in excess of 30 jobs on every update - this is slow, resource intensive, and likely overkill for the majority of PRs. Additionally, it increases the likelihood of having flaky test failures - often happens for 1/8 or 1/16 of the functional or conformance tests respectively - requiring rerunning of the failed jobs.
Additionally, Plus UBI builds fail pretty consistently in PRs from forks.
Each pipeline run also takes a really long time to build the binary and images.
Solution:
On PR runs:
On all runs:
Testing: This PR pipeline
Please focus on (optional): Is running a subset of the tests on PR runs an acceptable trade off? Note we will have to update our required checks if we go with this option
Closes #ISSUE
Checklist
Before creating a PR, run through this checklist and mark each as complete.
Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.