Changes to all GitHub workflows - timeout, checkout v3, concurrency, general cleanup #7178
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.
Signed-off-by: shirady 57721533+shirady@users.noreply.github.com
Explain the changes
According to CI next steps meeting:
This was a pilot in Add a step to cancel previous runs in GH Action #7159 , but after we started using it, we discovered that there is a builtin option from GitHub (concurrency).
General cleanup (was not in the meeting):
exit 1since the default behavior is when a step is failing to fail the whole job.idfields in the steps.Issues: Gap
The main gap is that the default timeout of jobs is 6 hours and it is a waste of computing resources since all of our jobs run in a sixth of the time. Another waste of computing resources is when we use successive pushes, and we would like to reduce it.
Testing Instructions: