Changes for page Jenkins Shared Library

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-xwiki:XWiki.achimmahnket-systemscom
	1	+xwiki:XWiki.borisfolgmannt-systemscom

Content

...	...	@@ -26,9 +26,8 @@
26	26	1. Checking out the source code from git.
27	27	1. If a pom.xml is found your favorite JDK is selected, by default jdk11. Then a maven build is done.
28	28	1. If there's no pom.xml but a package.json is found a nodejs build is done.
29		-1. If there is no pom.xml or package.json but a go.mod file, a go test tool run is done.
30	30	1. Then the following stages are executed in parallel
31		-11. Analysis: For maven projects the Java source code is checked by checkstyle, pmd and spotbugs. Furthermore the job output will be checked for any warnings generated by maven, javac or javadoc. If Python modules (.py files) exist in the git repository they will be analyzed using pylint and flake8. If pylint or flake8 are not available on the Jenkins agent the steps will be skipped. Python files that are generated or downloaded into the workspace will not be checked. The results will be displayed on the classical Jenkins build page after the build. If a go.mod f
	30	+11. Analysis: For maven projects the Java source code is checked by checkstyle, pmd and spotbugs. Furthermore the job output will be checked for any warnings generated by maven, javac or javadoc. If Python modules (.py files) exist in the git repository they will be analyzed using pylint and flake8. If pylint or flake8 are not available on the Jenkins agent the steps will be skipped. Python files that are generated or downloaded into the workspace will not be checked. The results will be displayed on the classical Jenkins build page after the build.
32	32	11. Security: If it's not a feature or bugfix branch a dependency check is done which checks if e.g. libraries are used which have known vulnerabilities. The results will be displayed in Jenkins after the build.
33	33	11. Docker: this will also work for projects which are neither maven or nodejs. A Dockerfile is enough to trigger this part of the pipeline.
34	34	111. If a Dockerfile is found a docker image is built.
...	...	@@ -397,13 +397,17 @@
397	397	|(((
398	398	sonarQube
399	399	)))|(((
400		-true for the defaultBranch and for pull-requests, if a SonarQube version is detected which supports scanning multiple branches
	399	+true for the defaultBranch
401	401
402		-false for all other branches
	401	+false for all other branches and pull-requests
403	403	)))|(((
404		-Set this to true to force a SonarQube scan for the current branch. Usually this makes only sense if you explicitly want to scan feature and bugfix branches.
	403	+Boolean which determines if SonarQube should be used if an installation is found.
405	405
406		-If not set or set to false, the default branch will be scanned automatically as well as pull-requests, if a SonarQube version is detected which supports scanning multiple branches. This is currently the case for SonarQube Developer and Enterprise editions. The free SonarQube Community edition supports just one branch.
	405	+The default is the best choice for the free community edition of SonarQube, which supports just one branch.
	406	+
	407	+If you have the Developer or Enterprise edition consider setting sonarQube to true to cover all branches. For more information see [[SonarQube>>SonarQube.WebHome]].
	408	+
	409	+Set this to true to force a SonarQube scan for the current branch. Usually this makes only sense if you explicitly want to scan feature and bugfix branches. If not set or set to false, the default branch will be scanned automatically as well as pull-requests if a SonarQube version is detected which supports scanning multiple branches. This is currently the case for SonarQube Developer and Enterprise editions. The free SonarQube Community edition supports just one branch.
407	407	)))
408	408	|(((
409	409	sonarScanMavenOpts