Changes for page Jenkins Shared Library

Summary

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

Details

Page properties

Content

...	...	@@ -28,7 +28,7 @@
28	28	1. If there's no pom.xml but a package.json is found a nodejs build is done.
29	29	1. If there is no pom.xml or package.json but a go.mod file, a go build 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.
	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. For Go projects, the Go test tool is used to run all tests and produce a coverage output file for SonarQube. Additionally, the gotestsum tool is used to produce a report which is picked up by Jenkins.</dd>
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.
...	...	@@ -126,8 +126,11 @@
126	126	)))|(((
127	127	'npm install && npm run build ~-~-prod'
128	128	)))|(((
129		-npm command to execute for building Node.JS projects.
	129	+npm command to execute for building Node.JS projects.
130	130	)))
	131	+|= |goBuildCommand|(((
	132	+'go build -o app cmd/server/main.go'
	133	+)))|go build step. Must be over
131	131	|=(% rowspan="10" %)(((
132	132	Docker build
133	133	)))|(((