Please provide a sonar-javascript-plugin without bundled nodejs runtimes

[anon67236913]

Hi,

@gab

For example, we are working on downloading only the target platform architecture, which would significantly reduce the payload.

Do you think that would help in your case?

Regarding the size of the bundled nodejs runtimes, it would surely help to reduce the used bandwith

But IMO your approach is wrong. Every npm build needs a nodejs runtime, right ?
If a CI/CD system drives frontend builds (including the Sonarqube analysis), it needs - and already has - a configured nodejs runtime environment.

Will you also start shipping a JRE and dll for mssql integrated authentication in the future !?
BTW that’s often wrong in the docs after releasing a new Sonarqube version
just one example

SonarQube 9.3 released

Hi @Chris , the problem is, that the release notes doesn’t mention the concrete version of the mssql jdbc driver. Also the release of Sonarqube version and the docs SonarQube 10.3 should be synchronous. And the docs for 9.3 have an error related to the mssql driver (you need to expand the Microsoft SQL Server section), https://docs.sonarqube.org/latest/setup/install-server/ has Integrated Security To use integrated security: Download the Microsoft SQL JDBC Driver 9.2.0 package and copy m…

Shipping a bundled nodejs runtime is well-intentioned, but overkill / causes problems.
How to implement “downloading only the target platform architecture”, guess you have to ship different editions of the sonar-javascript-plugin ?
Then you might also provide a variant without a bundled nodejs runtime.

@gab

Could you share a bit more about this? Where is the timeout? What is it affecting?

The timeout of 5min comes from load balancers, this causes failed builds because of socket timeouts after a Sonarqube update when scanners have to download the new plugins.

@gab

Is Sonar the only system affected?

Right now yes. No other tool transfers such big files.

Gilbert