Custom-Dockers/docker-sonarqube
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
master
docker-sonarqube/release.md
Mpho raf 8611a4bcb7
Some checks failed
continuous-integration/drone/pr Build is failing
Details
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/tag Build is passing
Details
update to version 9.9.2
2023-10-29 22:38:24 +02:00

3.4 KiB
Raw Permalink Blame History

Releasing

Docker image release cycle and SonarQube product

We consider the docker image as part of the SonarQube product. Therefore, it follows the same release process.

Overview

Release of a new version of the official SonarQube Docker images is made of several operations:

  1. bump the version of SonarQube in Dockerfiles
  2. bump the version of CURRENT_LTS_VERSION and CURRENT_VERSION accordingly in .cirrus.yml (please note that the nightly build will fail before the public image becomes available)
  3. Update the docker hub SonarQube's documentation (if applicable)
  4. Update Docker Hub's SonarQube images
  5. add a GIT tag for the new version

Bump the version of SonarQube in Dockerfiles

The version of SonarQube is hardcoded in each Dockerfile of this repository and must be updated in master branch.

Update the docker hub SonarQube's documentation (if applicable)

If needed, prepare PR of Docker Hub documentation https://github.com/docker-library/docs

Note: Please use your own fork like seen in this closed PR

To create a good PR:

  1. The markdown format must follow a certain standard, otherwise automated tests will fail. You can test with the markdownfmt.sh tool included in the repository, for example ./markdownfmt.sh -d sonarqube/content.md will output the diff that would have to be done to make the tests pass. You can use the patch command to apply the changes, for example: ./markdownfmt.sh -d sonarqube/content.md | patch sonarqube/content.md
  2. Verify the Pull Request passes the automated tests (visible in the status of the PR)

To control the generated content of the Docker Hub page, look around in the files in .template-helpers of the [docs repository][docs]. For example, the "Where to get help" section is customized by a copy of .template-helpers/get-help.md in sonarqube/get-help.md.

Until SonarQube is released and the public artifacts are available, keep your PR a draft PR to make it clear it is not ready to be merged yet.

For more and up to date documentation, see https://github.com/docker-library/docs.

Update Docker Hub's SonarQube images

In order to update the Docker Hub images, a Pull Request must be created on the official-images repository.

To do so you should use your own personal fork

Create a feature branch on the fork:

Until SonarQube is released and the public artifacts are available, keep your PR a draft PR to make it clear it is not ready to be merged yet.

  • Create the PR here
    • If the documentation was updated in the step before, reference that PR in this PR.
  • Click on compare across fork to be able to use the fork as head repository.

For more and up to date documentation, see https://github.com/docker-library/official-images.

Add a GIT tag for the new version

The commit referenced in the DockerHub Pull Request must be tagged with the (marketing) version of SQ: eg. 8.0, 8.0.1, 8.1.