The bridge server used for analyzing JavaScript/TypeScript files is unresponsive.

[Dhruvin Gabani]

image: node:lts # Choose an image matching your project needs

clone:

depth: full # SonarCloud scanner needs the full history to assign issues properly

definitions:

caches:

sonar: ~/.sonar/cache # Caching SonarCloud artifacts will speed up your build

services:

docker:

memory: 1024

docker-with-large-memory:

memory: 7168

type: docker #For large file line code

steps:

- step:

name: Install dependencies

caches:

- node

script:

- npm install

- npm install -g increase-memory-limit

- step: &build-test-sonarcloud

name: Build, test and analyze on SonarCloud

caches:

- node # See https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html

- sonar

script: # Build your project and run

- pipe: sonarsource/sonarcloud-scan:2.0.0

variables:

EXTRA_ARGS: "--exclude=src/@fuse/* -X"

- step: &check-quality-gate-sonarcloud

name: Check the Quality Gate on SonarCloud

script:

- pipe: sonarsource/sonarcloud-quality-gate:0.1.6

variables:

EXTRA_ARGS: "--exclude=src/@fuse/*"

pipelines: # More info here: https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html

default:

- step: *build-test-sonarcloud

- step: *check-quality-gate-sonarcloud

above is code of my bitbucket-pipeline.yml file for my react.js project but i still faced below issue as show in image

[Syahrul]

G'day, @Dhruvin Gabani 

Welcome to the community!

I can see that you are using a pipe. Can you enable the debug option in the pipe to generate a more verbose log?

DEBUG: "true"

Once done, please create a support ticket on our Support portal with the pipeline build URL enabled by the verbose option.

Regards,
Syahrul