mirror of
https://github.com/jpochyla/psst.git
synced 2026-04-27 15:35:56 +03:00
[GH-ISSUE #59] Run Action Builds in Parallel #48
Labels
No labels
api
bug
build
documentation
duplicate
enhancement
good first issue
help wanted
idea
invalid
linux
lowprio
macos
pull-request
upstream
windows
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/psst#48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
(from psst/actions/runs/885002673)
Edit:
Found this in the docs:
Example not requiring dependent jobs to be successfulneedsmay not apply, butif: always()sounds promissing.https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-not-requiring-dependent-jobs-to-be-successful
@jpochyla commented on GitHub (May 31, 2021):
I'm not sure how to use this for a
matrix-triggered jobs :/@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
@jpochyla commented on GitHub (May 31, 2021):
Should be fixed by
11cec9dda1. There's another issue with thedebjob not running if Windows or MacOS builds fail, not sure how to approach that one.