From da2657b1adc901dfc2905281fd299f15d1083b06 Mon Sep 17 00:00:00 2001
From: Daya Adianto <dayaadianto@cs.ui.ac.id>
Date: Fri, 13 Sep 2019 16:50:06 +0700
Subject: [PATCH] Fix GitLab CI job that runs SonarScanner
---
.gitlab-ci.yml | 7 +++++--
README.md | 5 ++++-
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 6693dd9..20469e6 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -5,7 +5,10 @@ stages:
- deploy
SonarScanner Analysis:
- image: addianto/sonar-scanner-cli:latest
+ image:
+ name: addianto/sonar-scanner-cli:latest
+ entrypoint:
+ - "/bin/bash"
stage: test
script:
- sonar-scanner
@@ -27,4 +30,4 @@ Publish to Docker Hub:
tags:
- docker
only:
- - master
\ No newline at end of file
+ - master
diff --git a/README.md b/README.md
index 371a791..258a999 100644
--- a/README.md
+++ b/README.md
@@ -29,7 +29,10 @@ To use the container image as a base image for a CI job on GitLab CI/CD:
```yaml
SonarScanner Analysis:
- image: addianto/sonar-scanner-cli:latest
+ image:
+ name: addianto/sonar-scanner-cli:latest
+ entrypoint:
+ - "/bin/bash"
# Ideally you want to run SonarScanner after the test suite has generated
# test & coverage report. The following is only an example to run
# SonarScanner concurrently with CI job(s) in `test` stage.
--
GitLab