Feature request: specify matrix on command line #114
Labels
area/cli
Relating to the cli
kind/feature-request
New feature or request
needs-work
Extra attention is needed
stale-exempt
Exempt from stale
Projects
Comments
cplee
added
area/cli
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
Is this actually done? I can't seem to find how to do it. |
|
@Julian it wasn't implemented |
|
Got it, thanks for the confirmation I wasn't missing it. |
catthehacker
added
stale-exempt
ChristopherHX
added a commit
to ChristopherHX/runner.server
that referenced
this issue
Apr 11, 2021
for workflow files Add --list to list jobs Add --secret(-file) to specifiy secrets from cli Add --env(-file) to specifiy env vars from cli --matrix is implemented like proposed for act: nektos/act#114
|
This would be a handy feature. My workflow as matrix of 5 node versions to test against and when running locally act seems to spin them all up in parallel and my system drops to a crawl. Being able to specify matrix items to run or at least how many containers at most to spin up at the same time would make this useable again. |
Merged
This comment was marked as spam.
This comment was marked as spam.
Handy workaround at least! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For matrix builds, it would be nice if I could limit the build to a subset (or just one) matrix option value for a build.
e.g.
my current workaround is to just edit the workflows file to remove the other matrix options before running
act, which works fine but isn't ideal.The text was updated successfully, but these errors were encountered: