NX Console Does Not Detect NX Cloud Connection for CI

[Squixx]

Issue: NX Console Does Not Detect NX Cloud Connection for CI

Description

I am experiencing an issue where the NX Console does not detect that I have connected to NX Cloud for CI because I haven't used the NX generator for my CI setup. I want to maintain my current CI setup and have the NX Console connect to my (EU) cloud environment.

Steps to Reproduce

1. Set up CI without using the NX generator.
2. Connect to NX Cloud for CI.
3. Open NX Console.

Expected Behavior

The NX Console should recognize the connection to NX Cloud and display recent CI runs.

Actual Behavior

• The NX Console does not detect the connection to NX Cloud.
• The NX Console shows the 'Generate CI configuration' button.
• Temporarily generating a new CI config makes the console recognize the CI configuration but still does not show recent CI runs.

Environment

• NX Console Version: [Your NX Console version]
• NX Cloud Region: EU
• CI Platform: Azure DevOps
  -VScode version: latest
  -nx-console version: latest

Additional Context

• My main goal is to get failed run feedback in the MCP, but this seems to be the first issue to fix.
• Any help or guidance on how to resolve this issue while keeping my current CI setup would be greatly appreciated.

Thank you!

[MaxKless]

Hi! Could you send an excerpt of your nx.json? Ofc replace the actual access tokens or ids with placeholders but it would very useful to see. Also, can you send a screenshot of the exact state of your cloud sidebar?

[Squixx]

{
  "$schema": "./node_modules/nx/schemas/nx-schema.json",
  "cli": {
    "packageManager": "pnpm"
  },
  "defaultBase": "develop",
  "defaultProject": "<redacted>",
  "generators": {
    "@nx/angular:application": {
      "e2eTestRunner": "cypress",
      "linter": "eslint",
      "prefix": "<redacted>",
      "strict": false,
      "style": "css",
      "unitTestRunner": "jest"
    },
    "@nx/angular:component": {
      "style": "none"
    },
    "@nx/angular:library": {
      "linter": "eslint",
      "prefix": "<redacted>",
      "strict": false,
      "unitTestRunner": "jest"
    }
  },
  "namedInputs": {
    "default": ["{projectRoot}/**/*", "sharedGlobals"],
    "production": [
      "default",
      "!{projectRoot}/**/?(*.)+(spec|test).[jt]s?(x)?(.snap)",
      "!{projectRoot}/tsconfig.spec.json",
      "!{projectRoot}/jest.config.[jt]s",
      "!{projectRoot}/.eslintrc.json",
      "!{projectRoot}/.storybook/**/*",
      "!{projectRoot}/**/*.@(mdx|stories.@(js|jsx|ts|tsx))",
      "!{projectRoot}/src/test-setup.[jt]s",
      "!{projectRoot}/tsconfig.storybook.json",
      "!{projectRoot}/**/*.stories.@(js|jsx|ts|tsx|mdx)",
      "!{projectRoot}/eslint.config.js"
    ],
    "sharedGlobals": [
      "{workspaceRoot}/.nx/workflows/agents.yaml",
      "{workspaceRoot}/.nvmrc"
    ]
  },
  "nxCloudAccessToken": "<redacted>",
  "nxCloudEncryptionKey": "<redacted>",
  "nxCloudUrl": "https://eu.nx.app",
  "parallel": 1,
  "plugins": [],
  "targetDefaults": {
    "@angular-devkit/build-angular:application": {
      "cache": true,
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"]
    },
    "@nx/angular:application": {
      "cache": true,
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"],
      "parallelism": false
    },
    "@nx/angular:browser-esbuild": {
      "cache": true,
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"],
      "parallelism": false
    },
    "@nx/angular:ng-packagr-lite": {
      "cache": true,
      "defaultConfiguration": "production",
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"]
    },
    "@nx/angular:package": {
      "cache": true,
      "defaultConfiguration": "production",
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"]
    },
    "@nx/eslint:lint": {
      "cache": true,
      "configurations": {
        "ci": {
          "quiet": true
        }
      },
      "inputs": [
        "default",
        "{workspaceRoot}/.eslintrc.json",
        "{workspaceRoot}/eslint.config.js"
      ],
      "options": {
        "cache": true
      }
    },
    "@nx/jest:jest": {
      "cache": true,
      "configurations": {
        "ci": {
          "ci": true,
          "codeCoverage": true
        }
      },
      "inputs": ["default", "^production", "{workspaceRoot}/jest.preset.js"],
      "options": {
        "codeCoverage": true,
        "passWithNoTests": true
      },
      "parallelism": false
    },
    "@nx/js:swc": {
      "cache": true,
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"]
    },
    "@nx/js:tsc": {
      "cache": true,
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"]
    },
    "build": {
      "cache": true,
      "dependsOn": ["^build"],
      "inputs": ["production", "^production"]
    },
    "build-storybook": {
      "cache": true,
      "dependsOn": ["^build"],
      "inputs": [
        "default",
        "^production",
        "{workspaceRoot}/.storybook/**/*",
        "{projectRoot}/.storybook/**/*",
        "{projectRoot}/tsconfig.storybook.json"
      ]
    },
    "e2e": {
      "cache": true,
      "inputs": ["default", "^production", "^e2e"],
      "parallelism": false
    },
    "lint": {
      "cache": true,
      "inputs": [
        "default",
        "{workspaceRoot}/.eslintrc.json",
        "{workspaceRoot}/eslint.config.js"
      ]
    },
    "sonar": {
      "cache": true,
      "dependsOn": ["test"],
      "inputs": [
        {
          "runtime": "echo $IS_PR"
        },
        {
          "runtime": "$IS_PR"
        }
      ],
      "parallelism": false
    },
    "test": {
      "cache": true,
      "inputs": ["default", "^production", "{workspaceRoot}/jest.preset.js"],
      "parallelism": false
    }
  },
  "tasksRunnerOptions": {
    "default": {
      "options": {
        "selectivelyHashTsConfig": true
      },
      "runner": "nx-cloud"
    }
  },
  "workspaceLayout": {
    "appsDir": "apps",
    "libsDir": "libs"
  }
}

it seems like its just not recognized ci is set up (we use tools/pipeline/affected-nx-agents.yml not azure-pipeliens.yml)

and even after that i'd wonder if it would be easy to link a PR run to a branch, as in nx-cloud the branch will the intermidate PR branch (#pr number), and not the actual local branch.

let me know if i could provide more info!

[MaxKless]

Do you have a recent CIPE on a branch that you have checked out locally?
Those two settings shouldn't actually block the CIPE screen to be displayed if there are any executions...

Still, it would probably be better if there was an option to mark these as completed manually...

[Squixx]

yes, e.g. https://eu.nx.app/cipes/6814c71c76a7d032075d6bd1

[MaxKless]

are there any messages in the output? Maybe an error of some sort in the request that we can track down?

• Go to Output -> Nx Language Server and paste what you see there.
• Go to Output -> Nx Console and paste what you see there.
• Run Toggle Developer Tools and paste what you see there too
• Finally, run nx daemon and provide the contents of the daemon.log file linked there

Thank you!

[Squixx]

[2025-05-02T18:53:19.581Z] Activating Nx Console (pid 10406) 
Nxls Client - idle
Nxls Client - starting
Telemetry: production
Nxls Client - idle
Nxls Client - idle
Nxls Client - starting
Graph Machine - undefined, {"context":{"state":"init","project":null,"error":null},"event":{"type":"xstate.init"},"self":{"xstate$$type":1,"id":"x:0"},"system":{"_snapshot":{"_scheduledEvents":{}},"scheduler":{},"_clock":{}}}
Graph - init
Enabling TypeScript plugin for workspace /redacted/devVf/vf-features
[2025-05-02T18:53:20.148Z] Using local Nx package at /redacted/vf-features/node_modules/nx/src/utils/nx-cloud-utils 
[2025-05-02T18:53:20.149Z] MCP server started on port 9515 
Nxls process started with pid: 10481
Nxls Client - running

[Nxls] - 2025-05-02T18:53:19.741Z - Initializing Nx Language Server

[Nxls] - 2025-05-02T18:53:19.745Z - Retrieving workspace configuration for nx 20.8.1

[Nxls] - 2025-05-02T18:53:19.824Z - Using local Nx package at /redacted/vf-features/node_modules/nx/src/project-graph/project-graph.js

[Nxls] - 2025-05-02T18:53:19.824Z - Using local Nx package at /redacted/vf-features/node_modules/nx/src/utils/output.js

[Nxls] - 2025-05-02T18:53:19.824Z - Using local Nx package at /redacted/vf-features/node_modules/nx/src/project-graph/file-map-utils.js

[Nxls] - 2025-05-02T18:53:19.825Z - Using local Nx package at /redacted/vf-features/node_modules/nx/src/daemon/client/client.js

[Nxls] - 2025-05-02T18:53:19.827Z - createProjectGraphAndSourceMapsAsync

[Nxls] - 2025-05-02T18:53:19.866Z - createProjectGraphAndSourceMapsAsync successful

[Nxls] - 2025-05-02T18:53:19.942Z - Resetting daemon client

[Nxls] - 2025-05-02T18:53:19.942Z - Retrieved workspace configuration in: 197.109042 ms

[Nxls] - 2025-05-02T18:53:20.007Z - Using local Nx package at /redacted/vf-features/node_modules/nx/src/daemon/client/client.js

[Nxls] - 2025-05-02T18:53:20.007Z - Initializing daemon watcher 

[Nxls] - 2025-05-02T18:53:20.403Z - Initialized daemon watcher

[Nxls] - 2025-05-02T18:53:20.622Z - Using local Nx package at /redacted/vf-features/node_modules/nx/src/utils/nx-cloud-utils

[Nxls] - 2025-05-02T18:53:20.768Z - Using local Nx package at /redacted/vf-features/node_modules/nx/src/utils/nx-cloud-utils

[Nxls] - 2025-05-02T18:53:20.813Z - Making claimed request

[Nxls] - 2025-05-02T18:53:20.833Z - Making recent CIPE request

daemon.log

no errors from what i can see unfortunately

Edit: or atleast none releated to this plugin.

I do see the making CIPE request going out though.

Could it be that as azure devops creates a mergebranch (and nx cloud takes the pr number as the branch name) the plugin isn't able to match the PR branch / local branch?

[MaxKless]

Hey, thanks for the logs! As you can see from that Making recent CIPE request log, the request to the cloud api goes through without errors, otherwise we'd see error logs there.

That something is up with the branches is very possible... we just take the local branch names and query the API for them.
You can see the logic that we use to determine branch names here:

nx-console/libs/shared/nx-cloud/src/lib/get-recent-cipe-data.ts

Line 77 in 47ea625

function getRecentlyCommittedGitBranches(

Maybe there's a mismatch here?

[Squixx]

Could be, as in nx-cloud the branch name is set like:

  - ${{ if eq(variables['Build.Reason'], 'PullRequest') }}:
      - name: NX_BRANCH
        value: $(System.PullRequest.PullRequestId)
      - name: TARGET_BRANCH
        value: $[replace(variables['System.PullRequest.TargetBranch'],'refs/heads/','origin/')]
      - name: BASE_SHA
        value: $(git merge-base $(TARGET_BRANCH) HEAD)

so my assumption would be you query on NX_BRANCH on the nx-cloud side, but knowing this I'm not actually sure the origin branch would be known on nx-cloud in the case of azure devops.

this pr reference # is also used for stuff like pr comments, so I'd expect this might be bit of a bigger issue.

Possibly hitting core, cloud and plugin?

Meaning this probably isn't broken, but might be missing some data by design (currently).

it might be as 'simple' as having an additional input e.g. NX_ORIGIN_BRANCH throughout the entire flow and then matching on both NX_BRANCH and NX_ORIGIN_BRANCH in the plugin.

Not sure how you'd like me to approach this issue though, as I can imagine this isn't a simple fix.

@meeroslav just tagging you as an FYI

[MaxKless]

I talked to @lourw who built this from the cloud side. He agrees with you - it's probably an issue with the branch names. Currently we've focused mostly on GitHub and handled edge cases there, so other providers might have bugs.
Thanks to you, we're aware of it now and will look into asap :)

[Squixx]

Awesome, let me know If I can provide any kind of help.