-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nx version 15.4 not forwarding arguments to run-many? #14050
Comments
Same here. In 15.4.2 just ignores params we pass to nx:affected |
@jgarciaokode I believe this should have been fixed by #14031. Can you try 15.4.2 and see if it is working for you? |
@AgentEnder yes, it is working in 15.4.2 Thanks for the quick answer ^^ |
Hi @AgentEnder, it works locally, but still swallowing the arguments on Azure with nx-cloud, could you advise, please? |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
In Nx v14.8.3 when you run
nx run-many --target deploy --options="--all"
then the options arg is being passed to all executors, therefore as we have a cdk with multiple stacks, the pipeline does not exit with error asking to supply which cdk stack should be deployedHowever, in Nx v15.4.1, when you run exactly the same command, the arg is not being passed (it seems) and therefore, the pipeline exists with error
I tried with nx:run-commands executors and the same applies, the thing is that if you run nx run :deploy --all it is working since the arguments are being forwarded
Expected Behavior
As described, same behaviour than Nx 14.8.3, arguments being forwarded in run-many command
Github Repo
No response
Steps to Reproduce
d
Nx Report
Failure Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: