Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

Should we support configuring the OSes go-test runs on? #349

Closed
galargh opened this issue Jun 29, 2022 · 3 comments
Closed

Should we support configuring the OSes go-test runs on? #349

galargh opened this issue Jun 29, 2022 · 3 comments

Comments

@galargh
Copy link
Contributor

galargh commented Jun 29, 2022

So far, I've encountered one instance where this would be a useful feature - see https://github.com/libp2p/go-openssl/pull/25/files#r909792651

@marten-seemann
Copy link
Contributor

Yes, that would be helpful. Is there any way to do it without requiring an extra step? It is nice that the GitHub Actions scheduler knows the matrix in advance right now.

@galargh
Copy link
Contributor Author

galargh commented Nov 14, 2022

Unfortunately, I don't think it is at the moment. I found an issue that would make it possible though and followed up on it - actions/runner#1180

@galargh
Copy link
Contributor Author

galargh commented Aug 28, 2023

OSes can now be skipped through https://github.com/pl-strflt/uci#job-specific-configuration-files.

Now that the go-test workflow is a reusable workflow, we'll also be able to make use of reusable workflow inputs for configuration. With that, we'd be able to skip jobs for skipped OSes entirely instead of going through the runner setup even though we're not doing any work.

This will be tracked in ipdxco/unified-github-workflows#42.

@galargh galargh closed this as completed Aug 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants