fix(core): Trailing slash in outputs array prevents correct caching
Fix by removing trailing slash when performing cp -a into cache.
Add test to confirm fix.
Fixes nrwl/nx#10549
☁️ Nx Cloud Report
CI is running/has finished running commands for commit 4960cdae968d772cfe3683d5cd74fdf7cdab345e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this branch
✅ Successfully ran 12 targets
nx affected --target=e2e --base=a592af1eb34c3f430cb1828800c4670e1246dec2 --head=4960cdae968d772cfe3683d5cd74fdf7cdab345e --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox,e2e-make-angular-cli-faster --parallel=1nx affected --target=test --base=a592af1eb34c3f430cb1828800c4670e1246dec2 --head=4960cdae968d772cfe3683d5cd74fdf7cdab345e --parallel=1nx-cloud record -- yarn depchecknx affected --target=lint --base=a592af1eb34c3f430cb1828800c4670e1246dec2 --head=4960cdae968d772cfe3683d5cd74fdf7cdab345e --parallel=3nx-cloud record -- yarn nx workspace-lintnx-cloud record -- yarn check-lock-filesnx affected --target=build --base=a592af1eb34c3f430cb1828800c4670e1246dec2 --head=4960cdae968d772cfe3683d5cd74fdf7cdab345e --parallel=3nx-cloud record -- yarn check-commitnx-cloud record -- yarn nx format:check --base=a592af1eb34c3f430cb1828800c4670e1246dec2 --head=4960cdae968d772cfe3683d5cd74fdf7cdab345enx-cloud record -- yarn check-importsnx-cloud record -- yarn documentationnx build typedoc-theme
Sent with 💌 from NxCloud.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated |
|---|---|---|---|
| nx-dev | ✅ Ready (Inspect) | Visit Preview | Sep 29, 2022 at 3:23PM (UTC) |
Hej @FrozenPandaz @meeroslav, does one of you have the capacity to review this?
Once the comments are addressed, we should rebase to the latest version to fix those conflicting files.
@meeroslav @AgentEnder I've made changes as requested and rebased. Thanks.
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.