Changes for page Jenkins Shared Library
Last modified by Achim Mahnke on 2025/10/01 10:24
From version 3.2
edited by Achim Mahnke
on 2025/10/01 10:24
on 2025/10/01 10:24
Change comment:
There is no comment for this version
To version 3.1
edited by Boris Folgmann
on 2025/07/09 16:16
on 2025/07/09 16:16
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. achimmahnket-systemscom1 +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 f30 +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.