[GH-ISSUE #59] Run Action Builds in Parallel #48

Closed
opened 2026-02-28 14:30:14 +03:00 by kerem · 3 comments
Owner

Originally created by @shiftgeist on GitHub (May 28, 2021).
Original GitHub issue: https://github.com/jpochyla/psst/issues/59

It'd be great if the Debian build gets executed when the windows build fails. Sequential builds could also be interesting.

image
(from psst/actions/runs/885002673)


Edit:

Found this in the docs: Example not requiring dependent jobs to be successful

jobs:
  job1:
  job2:
    needs: job1
  job3:
    if: always()
    needs: [job1, job2]

needs may not apply, but if: always() sounds promissing.

https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-not-requiring-dependent-jobs-to-be-successful

Originally created by @shiftgeist on GitHub (May 28, 2021). Original GitHub issue: https://github.com/jpochyla/psst/issues/59 It'd be great if the Debian build gets executed when the windows build fails. Sequential builds could also be interesting. ![image](https://user-images.githubusercontent.com/30648730/120012566-f3925d80-bfdf-11eb-8c03-9d702c285cab.png) (from [psst/actions/runs/885002673](https://github.com/jpochyla/psst/actions/runs/885002673)) --- Edit: Found this in the docs: `Example not requiring dependent jobs to be successful` ```yaml jobs: job1: job2: needs: job1 job3: if: always() needs: [job1, job2] ``` `needs` may not apply, but `if: always()` sounds promissing. https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-not-requiring-dependent-jobs-to-be-successful
kerem closed this issue 2026-02-28 14:30:15 +03:00
Author
Owner

@jpochyla commented on GitHub (May 31, 2021):

I'm not sure how to use this for a matrix-triggered jobs :/

<!-- gh-comment-id:851383614 --> @jpochyla commented on GitHub (May 31, 2021): I'm not sure how to use this for a `matrix`-triggered jobs :/
Author
Owner

@jpochyla commented on GitHub (May 31, 2021):

This seems to be the culprit: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast

<!-- gh-comment-id:851385040 --> @jpochyla commented on GitHub (May 31, 2021): This seems to be the culprit: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast
Author
Owner

@jpochyla commented on GitHub (May 31, 2021):

Should be fixed by 11cec9dda1. There's another issue with the deb job not running if Windows or MacOS builds fail, not sure how to approach that one.

<!-- gh-comment-id:851394982 --> @jpochyla commented on GitHub (May 31, 2021): Should be fixed by 11cec9dda10828b470b3cf1f6da9c0acd6b56369. There's another issue with the `deb` job not running if Windows or MacOS builds fail, not sure how to approach that one.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/psst#48
No description provided.