Concurrency - Implement fix for strict sequencing of actions in scheduled-baselines when available
Opened this issue · 1 comments
User Story
As a Modernisation Platform Engineer
I want all queued scheduled-baselines actions to run in the order in which they were started
So that issues related to changes in a given commit or PR are not obscured by latter changes and so made more difficult to debug.
This can only be applied once github have implemented the solution as discussed here - https://github.com/orgs/community/discussions/12835#discussioncomment-10612372
Value / Purpose
The current behaviour of the concurrency feature in github actions is to cancel any waiting actions if another action of that workflow is started. The result is that subsequent action applying a larger number of changes than was originally intended and, in the event of errors, could make identifying the source of the issue take longer.
Useful Contacts
No response
Additional Information
This is an outcome of spike #6857 and the discussions that were held during its review.
This issue is also discussed here - https://github.com/orgs/community/discussions/12835#discussioncomment-10612372
Definition of Done
- Fix applied to the concurrency implementation in the scheduled-baselines workflow.
- Fix tested and the correct behaviour confirmed.
We think this should be refined once the fix is available.