NX not passing flag to the first job in affected run
See original GitHub issueCurrent Behavior
When running:
nx affected --target publish --parallel --base <hash> --with-deps --pkgVersion 1.3.0
The first job that gets run doesn’t receive flag.
- nx-core
- nx-jest-playwright
- nx-serverless
- nx-npm
With flags:
--pkgVersion=1.3.0
...
nx run nx-core:publish
...
nx run nx-jest-playwright:publish --pkgVersion=1.3.0
...
Consecutive jobs get it, but the first one is missing one.
Expected Behavior
All jobs should get flag.
Steps to Reproduce
You can see the run here: https://github.com/Bielik20/nx-plugins/runs/3997050209?check_suite_focus=true
Environment
Node : 14.16.1
OS : win32 x64
yarn : 1.22.10
nx : 13.0.2
@nrwl/angular : Not Found
@nrwl/cli : 13.0.2
@nrwl/cypress : Not Found
@nrwl/devkit : 13.0.2
@nrwl/eslint-plugin-nx : 13.0.2
@nrwl/express : Not Found
@nrwl/jest : 13.0.2
@nrwl/linter : 13.0.2
@nrwl/nest : Not Found
@nrwl/next : Not Found
@nrwl/node : 13.0.2
@nrwl/nx-cloud : 12.5.1
@nrwl/react : Not Found
@nrwl/schematics : Not Found
@nrwl/tao : 13.0.2
@nrwl/web : Not Found
@nrwl/workspace : 13.0.2
@nrwl/storybook : Not Found
@nrwl/gatsby : Not Found
typescript : 4.3.5
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Pnpm and Nx monorepo. Part 3 | Javier Brea
CI/CD for Pnpm and Nx monorepo using Github actions. ... When not in a PR and the current branch is main, pass --all...
Read more >Nx v14 is out — Here is all you need to know!
If you want to work on one of the remotes, simply explicitly pass their name using --devRemotes flag and it will be served...
Read more >Getting Started with Monorepo with Nx Nrwl - Rupesh Tiwari
This will solve the problem and you will not have many Git projects ... In order to create your first Nx Monorepo workspace...
Read more >go command - cmd/go - Go Packages
-work print the name of the temporary work directory and do not delete it when exiting. -x print the commands. -asmflags '[pattern=]arg list'...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Bielik20 you’re absolutely right. I’m sorry, I mixed the issues and forgot the original issue was about
--with-deps
.I’m re-opening this and we’ll have a look.
@leosvelperez Thank you for responding I appreciate that.
I have seen the other issue https://github.com/nrwl/nx/issues/7136 I think it is very important and calls for a larger debate. That being said, I do not agree it is a duplicate of THIS issue.
https://github.com/nrwl/nx/issues/7136 is about target dependencies and handling arguments in that NEW approach. Here we are discussing behaviour with
withDeps
flag which used to work fine and now it doesn’t, which is a regression.This is really critical regression for me, because I cannot update my repository that holds Nx Plugins because it will break the release process.