Blocked task SonarQubePrepare because of NodeJS 6 execution handler

Template for a good bug report, formatted with Markdown:

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension)

    • SonarQube 8.9 DE
    • Azure DevOps Services
    • Task SonarQubePrepare 4.21.0
  • error observed (wrap logs/code around triple quote for proper formatting) `` The pipeline is not valid. Job: XXX Step 'SonarQubePrepare' references tasks 'SonarQubePrepare' at version '4.21.0' containts an execution handler that relies on NodeJS version '6' which is restrictred by your administrator.

  • steps to reproduce
    Any pipeline which uses the current SonarQube extension

  • potential workaround
    Enable NodeJS 6 tasks in Azure DevOps in organization Settings / Pipelines / Settings.

Hi Volker,
Thank you for sharing this bug. We are aware of this and haven’t take any decision so far regarding the fix.
Is this a blocker for you right now?


Hi Christophe,
we migrated from Azure DevOps Server to Services recently and NodeJS6 was blocked. I could convince our admin to enable it again, as your and another task (from Microsoft) were blocked.

Therefore, at the moment we are no longer blocked. As soon as Microsoft fixes their task the discussion will start again and then it will be more difficult to keep the NodeJS 6 technology enabled.


Thanks for your answer @milbrandt . We will try to address that asap :wink: