1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-08-09 13:47:13 +02:00
unleash.unleash/.github/workflows
Kitsios Konstantinos 84748aaff0
[CI]: Cancel CI runs that become obsolete (#10339)
## About the changes
Currently, if a PR is open and a push happens, the **e2e:frontend**
workflow will start running. If, shortly after a subsequent push on the
*same* PR happens, the workflow will start running again without
cancelling the previous (now obsolete) run. With these changes, the
first run would be cancelled, thus **saving compute resources** (see
below for quantity) that can be used to **speed up your overall CI/CD**,
without sacrificing functionality, since the second run will contain the
changes from the first push as well. 🌱

### Example
Here is an example of the behaviour described above: the commit
`b1b2e61` triggered
[this](https://github.com/Unleash/unleash/actions/runs/14493085673/)
workflow run, and shortly after the commit `9997fe1`, that happened on
top of the first commit, triggered
[this](https://github.com/Unleash/unleash/actions/runs/14493089012/)
workflow. Both workflows ran till the end, spending approximately 8 CPU
minutes each. With the proposed changes, the first run would be
cancelled, hence saving ~8 CPU minutes and clearing the queue for other
workflows. Note that this is an example of a single concurrent run; the
accumulated gain for all PRs would be higher, with a lower estimate at
**2 CPU hours** over the last few months.

The same holds for these workflow(s) as well: Dependency review, PR ->
Build Docs.

### Context
Hi,

We are a team of [researchers](https://www.ifi.uzh.ch/en/zest.html) from
University of Zurich and we are currently working on energy
optimizations in GitHub Actions workflows.

Kindly let us know (here or in the email below) if you would like more
details, if you want to reject the proposed changes for other reasons,
or if you have any question whatsoever.

Best regards,  
[Konstantinos
Kitsios](https://www.ifi.uzh.ch/en/zest/team/konstantinos_kitsios.html)
konstantinos.kitsios@uzh.ch
2025-07-17 11:22:44 +01:00
..
add-to-project.yml
ai-flag-cleanup-pr.yml chore: AI flag cleanup action trigger workflows (#10288) 2025-07-03 08:48:28 +01:00
ai-flag-cleanup.yml chore: AI flag cleanup action trigger workflows (#10288) 2025-07-03 08:48:28 +01:00
auto-assign-pr-author.yaml
build_coverage.yaml fix(ci): update config to make GHA reporting be better 2025-05-16 15:04:40 +02:00
build_doc_prs.yaml [CI]: Cancel CI runs that become obsolete (#10339) 2025-07-17 11:22:44 +01:00
build_frontend_prs.yml
build_prs_jest_report.yaml fix: coverage (#10321) 2025-07-07 11:14:39 +02:00
build.yaml chore: openapi-diff on PRs (#10100) 2025-06-10 16:51:12 +02:00
check_links.yaml
codeql-analysis.yml
core-feature-alert.yml chore(deps): update actions/github-script action to v7 (#9040) 2025-06-23 10:48:27 +00:00
dependency-review.yml [CI]: Cancel CI runs that become obsolete (#10339) 2025-07-17 11:22:44 +01:00
docker_publish.yaml task(ci): Bump base image for OSS docker (#10014) 2025-05-16 15:50:58 +02:00
e2e.frontend.yaml [CI]: Cancel CI runs that become obsolete (#10339) 2025-07-17 11:22:44 +01:00
flag-no-response.yaml
gitar-duet-action.yml
gradual-strict-null-checks.yml
hypermod.yml chore(deps): update actions/checkout action to v4 (#10192) 2025-06-24 09:53:47 +02:00
notify_enterprise.yaml
openapi-diff.yaml chore: openapi-diff on PRs (#10100) 2025-06-10 16:51:12 +02:00
pr_add_test_results.yaml
publish-new-version.yaml
release.yaml feat: ability to run npm release from branch (#10120) 2025-06-11 16:22:09 +02:00
reset_heroku.yml
update_contributors.yaml
update_version_for_version_checker.yml
validate-migrations.yaml