Bonnes pratiques et cas avances¶

# Marquer une issue comme "Won't Fix" (faux positif)
curl -u admin:TOKEN -X POST \
  "http://localhost:9000/api/issues/do_transition" \
  -d "issue=AYxxxxxx" \
  -d "transition=wontfix"

# Ajouter un commentaire de justification
curl -u admin:TOKEN -X POST \
  "http://localhost:9000/api/issues/add_comment" \
  -d "issue=AYxxxxxx" \
  -d "text=Faux positif : ce pattern est securise par le middleware d'authentification en amont. Valide par @tech-lead le 2026-04-16."

# Script de collecte des metriques pour Grafana
#!/bin/bash
# /home/sonarqube/scripts/collect-metrics.sh

SONAR_URL="http://localhost:9000"
SONAR_TOKEN="${SONAR_TOKEN}"
OUTPUT="/var/lib/prometheus/textfile/sonarqube.prom"

# Lister tous les projets
projects=$(curl -s -u "${SONAR_TOKEN}:" \
  "${SONAR_URL}/api/projects/search?ps=500" | \
  jq -r '.components[].key')

echo "# HELP sonarqube_quality_gate_status Quality gate status (1=OK, 0=ERROR)" > "${OUTPUT}"
echo "# TYPE sonarqube_quality_gate_status gauge" >> "${OUTPUT}"

for project in ${projects}; do
  status=$(curl -s -u "${SONAR_TOKEN}:" \
    "${SONAR_URL}/api/qualitygates/project_status?projectKey=${project}" | \
    jq -r '.projectStatus.status')

  value=0
  [ "${status}" = "OK" ] && value=1

  echo "sonarqube_quality_gate_status{project=\"${project}\"} ${value}" >> "${OUTPUT}"
done

#!/bin/bash
# /home/sonarqube/scripts/backup.sh
set -euo pipefail

DATE=$(date +%Y%m%d-%H%M%S)
BACKUP_DIR="/backup/sonarqube"

mkdir -p "${BACKUP_DIR}"

# Dump PostgreSQL
podman exec sonarqube-db pg_dump -U sonarqube sonarqube | \
  gzip > "${BACKUP_DIR}/db-${DATE}.sql.gz"

# Export des quality profiles
for lang in java python js ts go; do
  curl -s -u "${SONAR_TOKEN}:" \
    "http://localhost:9000/api/qualityprofiles/backup?language=${lang}" \
    > "${BACKUP_DIR}/profile-${lang}-${DATE}.xml" 2>/dev/null || true
done

# Export de la configuration
curl -s -u "${SONAR_TOKEN}:" \
  "http://localhost:9000/api/settings/values" | \
  jq . > "${BACKUP_DIR}/settings-${DATE}.json"

# Nettoyage des backups > 30 jours
find "${BACKUP_DIR}" -name "*.gz" -mtime +30 -delete
find "${BACKUP_DIR}" -name "*.xml" -mtime +90 -delete
find "${BACKUP_DIR}" -name "*.json" -mtime +90 -delete

echo "Backup completed: ${DATE}"

# 1. Arreter SonarQube
sudo -u sonarqube podman-compose down

# 2. Restaurer la base PostgreSQL
gunzip -c "${BACKUP_DIR}/db-YYYYMMDD-HHMMSS.sql.gz" | \
  podman exec -i sonarqube-db psql -U sonarqube sonarqube

# 3. Restaurer les quality profiles
for profile in "${BACKUP_DIR}"/profile-*-YYYYMMDD-HHMMSS.xml; do
  lang=$(echo "${profile}" | sed 's/.*profile-\(.*\)-[0-9].*/\1/')
  curl -u "${SONAR_TOKEN}:" -X POST \
    "http://localhost:9000/api/qualityprofiles/restore" \
    -F "backup=@${profile}"
done

# 4. Redemarrer SonarQube (reindexation automatique)
sudo -u sonarqube podman-compose up -d

# 1. Backup complet
/home/sonarqube/scripts/backup.sh

# 2. Arreter SonarQube
sudo -u sonarqube podman-compose down

# 3. Mettre a jour l'image
# Dans podman-compose.yml, changer :
#   image: docker.io/library/sonarqube:10-community
# en :
#   image: docker.io/library/sonarqube:11-community

# 4. Demarrer (migration automatique de la base)
sudo -u sonarqube podman-compose up -d

# 5. Verifier les logs de migration
sudo -u sonarqube podman logs -f sonarqube
# Attendre "SonarQube is operational"

# 6. Verifier le statut
curl -s http://localhost:9000/api/system/status | jq .

# Verifier l'utilisation du heap ES
curl -s http://localhost:9000/api/system/info | \
  jq '.Statistics."Search State"'

# Si le heap est > 85%, augmenter la memoire
# sonar.search.javaOpts=-Xmx2g -Xms2g