Upcoming last release v.4.0.0 (remove Docker) and deprecation of GitHub action for SonarQube Cloud

SonarQube Cloud Announcements
, ,
1

Hello SonarQube Cloud users!

As recently done for SonarQube Server, we plan to release a new major version (v4.0.0) of our GitHub action for SonarQube Cloud, removing Docker and moving to a composite action.

:warning: DEPRECATION WARNING :warning:

This new version of the GitHub action for SonarQube Cloud is going to be the last one specifically designed for SonarQube Cloud.

Since v4.1.0, the former GitHub action for SonarQube Server (sonarqube-scan-action) is the entrypoint for both Server and Cloud: a single GitHub action to interact with the SonarQube solution, whether on premise or in the cloud! You can read more about the unified action here.

You may notice a warning in logs and annotations encouraging you to move to the latest version of sonarqube-scan-action.

image
image1600×101 59.1 KB

image
image1600×291 47.4 KB

We don’t expect any issue migrating from one action to the other: sonarqube-scan-action@v4 should be a drop-in replacement for sonarcloud-github-action@v3.

Removal of Docker

As for v4.0.0 of the GitHub action for SonarQube Server, the new version won’t spawn anymore a new Linux-based Docker container at every scan. Instead, the new action is now defined as a composite action. Therefore, its steps are directly embedded into your GitHub workflow, and the scan will run in the same environment of the workflow.

This comes with multiple benefits:

  • you can now use our GitHub action with Java and Dart project, that previously didn’t support it due to Docker isolation
  • your run won’t fail anymore in peak workload scenarios due the Docker image hitting the rate limit on DockerHub
  • the scan won’t need to run the scan as a root user, as recommended by GitHub for operations happening in a Docker container
  • you will be able to run the action as part of your workflow on any Operating System

Update

If you encounter any issues, please create a new post here in the community describing your scenario and providing logs. In the meantime, you can revert your pipeline to v3.1.0 to get back to an operational state.

Stay tuned for the release of this new version of the GitHub action in the coming days!
Antonio

2

Hi everybody,

We have just released v4.0.0!
You can find release notes here and marketplace page for the new version of the action here.

Antonio

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.