Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
master
5ffd132c fix(misc): use workspaceRoot in workspaceModule path (#35142) copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from. ## Current Behavior Running the `copy-workspace-modules` from anywhere other than the root of the workspace results in `ENOENT: no such file or directory` for the package. ## Expected Behavior Running `copy-workspace-modules` should copy the modules successfully regardless of where the process is run from.
by David Johnson
Succeeded
master
5ffd132c fix(misc): use workspaceRoot in workspaceModule path (#35142) copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from. ## Current Behavior Running the `copy-workspace-modules` from anywhere other than the root of the workspace results in `ENOENT: no such file or directory` for the package. ## Expected Behavior Running `copy-workspace-modules` should copy the modules successfully regardless of where the process is run from.
by David Johnson
Succeeded
master
5ffd132c fix(misc): use workspaceRoot in workspaceModule path (#35142) copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from. ## Current Behavior Running the `copy-workspace-modules` from anywhere other than the root of the workspace results in `ENOENT: no such file or directory` for the package. ## Expected Behavior Running `copy-workspace-modules` should copy the modules successfully regardless of where the process is run from.
by David Johnson
Failed
master
5ffd132c fix(misc): use workspaceRoot in workspaceModule path (#35142) copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from. ## Current Behavior Running the `copy-workspace-modules` from anywhere other than the root of the workspace results in `ENOENT: no such file or directory` for the package. ## Expected Behavior Running `copy-workspace-modules` should copy the modules successfully regardless of where the process is run from.
by David Johnson
Succeeded
35142
08ef134d fix(js): use workspaceRoot in copy-workspace-modules path copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from.
by David Johnson
Failed
35142
Flaky task→
08ef134d fix(js): use workspaceRoot in copy-workspace-modules path copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from.
by David Johnson
Failed
35142
Flaky task→
3673dcd9 fix(js): use workspaceRoot in copy-workspace-modules path copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from.
by David Johnson
Failed
master
8135f11d fix(core): run selected projects with --exclude-task-dependencies (#35562) `nx exec --projects @org/taskWithDeps --excludeTaskDependencies -- {command}` should still run the command for the passed project even if it's dependent tasks are ignored.      ## Current Behavior When `nx exec --projects @org/taskWithDeps --excludeTaskDependencies -- echo 1` 1 is never echo'd. ## Expected Behavior The command should run for at least the passed in projects, even if their dependencies are ignored. --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
by David Johnson
Failed
35142
Flaky task→
15b98d82 fix(js): use workspaceRoot in copy-workspace-modules path copy-workspace-modules should prepend the workspaceRoot when copying the workspaceModule to ensure that the executor can successfully copy the module regardless of where in the workspace it is run from.
by David Johnson