Optimize GitHub Actions execution #840
Comments
kuritka
added a commit
that referenced
this issue
Jan 26, 2022
related to #840 skipping already finished workflows, NOT concurrent (different PR) I've been doing investigations about canceling workflows (https://github.com/fkirc/skip-duplicate-actions). The action works by checking in pre_job whether the pipe has already been run. Then in the main job there is a condition that either continues processing or skips the job. This results in ALWAYS running all workflows, even duplicate ones. The difference is that the duplicates will terminate at a different point. We will still see a lot of green runs. It's a bit different than I imagined (not starting or CANCEL the duplicate at all). I found out that I can cancel the workflow programmatically via HTTP POST. So if we create different custom ction, we can cancel on top and probably delete cancelled job. Signed-off-by: kuritka <kuritka@gmail.com>
Merged
kuritka
added a commit
that referenced
this issue
Jan 28, 2022
related to #840 skipping already finished workflows, NOT concurrent (different PR) I've been doing investigations about canceling workflows (https://github.com/fkirc/skip-duplicate-actions). The action works by checking in pre_job whether the pipe has already been run. Then in the main job there is a condition that either continues processing or skips the job. This results in ALWAYS running all workflows, even duplicate ones. The difference is that the duplicates will terminate at a different point. We will still see a lot of green runs. It's a bit different than I imagined (not starting or CANCEL the duplicate at all). I found out that I can cancel the workflow programmatically via HTTP POST. So if we create different custom ction, we can cancel on top and probably delete cancelled job. Signed-off-by: kuritka <kuritka@gmail.com>
kuritka
added a commit
that referenced
this issue
Mar 22, 2022
related to #840 skipping already finished workflows, NOT concurrent (different PR) I've been doing investigations about canceling workflows (https://github.com/fkirc/skip-duplicate-actions). The action works by checking in pre_job whether the pipe has already been run. Then in the main job there is a condition that either continues processing or skips the job. This results in ALWAYS running all workflows, even duplicate ones. The difference is that the duplicates will terminate at a different point. We will still see a lot of green runs. It's a bit different than I imagined (not starting or CANCEL the duplicate at all). I found out that I can cancel the workflow programmatically via HTTP POST. So if we create different custom ction, we can cancel on top and probably delete cancelled job. Signed-off-by: kuritka <kuritka@gmail.com>
|
/resolved; #844 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have quite an amount of duplication in action triggering given the parallel reaction to both
pushandpull_requestWe can try to optimize it with https://github.com/fkirc/skip-duplicate-actions
The text was updated successfully, but these errors were encountered: