Add additional documentation regarding available jenkins slave images for Sonar scanning - Githubissues

BCDevOps / sonarqube

An OpenShift-focused Docker build of Sonarqube

GNU Lesser General Public License v3.0

2 stars 33 forks source link

Add additional documentation regarding available jenkins slave images for Sonar scanning #5

Open WadeBarnes opened 6 years ago

WadeBarnes commented 6 years ago

The following Jenkins slave images are available in the Pathfinder OpenShift environment;

jenkins-slave-base-rhel7
jenkins-slave-bddstack
jenkins-slave-nodejs
jenkins-slave-nodejs6
jenkins-slave-py3nodejs
jenkins-slave-python-rhel7
jenkins-slave-python3nodejs (created for Sonar scanning)
jenkins-slave-sonar (created for Sonar scanning .net applications)
jenkins-slave-zap (created for zap scanning)

These images are built off the sources found here; https://github.com/BCDevOps/openshift-components/tree/master/cicd

jenkins-slave-sonar is an image created for .net applications. Built from https://github.com/BCDevOps/openshift-components/blob/master/cicd/sonar/Dockerfile

Example using that image:

The pipeline using it is here; https://github.com/bcgov/hets/blob/master/Jenkins/sonarqube/Jenkinsfile

Question:

Can jenkins-slave-sonar be used in place of jenkins-slave-python3nodejs so there is just one image used for Sonar scanning.

rstens commented 6 years ago

Can jenkins-slave-sonar be used in place of jenkins-slave-python3nodejs so there is just one image used for Sonar scanning. If the image also contains Python, sure why not. Right now I am not sure it does.