Skip to Content

Changes for page Jenkins Shared Library

Last modified by Boris Folgmann on 2025/11/03 09:41
From version 9.1
edited by Boris Folgmann
on 2025/11/03 09:18
Change comment: Uploaded new attachment "1762161531690-966.png", version {1}
To version 5.1
edited by Boris Folgmann
on 2025/11/03 08:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,7 +6,7 @@
6 6  
7 7  == Getting Started ==
8 8  
9 -Since the Shared Library is globally configured on all Jenkins instances managed by DevOps-as-a-Service you just need to place the following very short Jenkinsfile in the root folder of your git repository to automatically build your maven, node or go project or simply build a container using a Dockerfile.
9 +Since the Shared Library is globally configured on all Jenkins instances managed by DevOps-as-a-Service you just need to place the following very short Jenkinsfile in the root folder of your git repository to automatically build your maven or node project or simply build a container using a Dockerfile.
10 10  
11 11  {{code}}
12 12  @Library('sdcloud') _
... ... @@ -128,8 +128,6 @@
128 128  )))|(((
129 129  npm command to execute for building Node.JS projects.
130 130  )))
131 -|= |go|'go'|Golang version to use.
132 -Refers to a symbolic name of a go tool configuration in Jenkins.
133 133  |= |goBuildCommand|(((
134 134  'go build -o app cmd/server/main.go'
135 135  )))|go build run. Should be overridden for your project.
... ... @@ -312,11 +312,9 @@
312 312  |(((
313 313  helmRegistry
314 314  )))|(((
315 -Helm registry of your DOaaS instance, which is usally 'https:~/~/registry-CUSTOMER.devops.t-systems.net/chartrepo/PROJECTKEY'
313 +Nexus registry of your DOaaS instance
316 316  )))|(((
317 -Helm registry to which the packaged Helm chart is uploaded.
318 -
319 -
315 +Name of registry to which the packaged Helm chart is uploaded.
320 320  )))
321 321  |(((
322 322  helmRegistryCredentialsId
... ... @@ -355,7 +355,7 @@
355 355  )))|(((
356 356  Id of the Jenkins Credentials for signers private keyfile.
357 357  )))
358 -|=(% colspan="1" rowspan="8" %)(((
354 +|=(% colspan="1" rowspan="12" %)(((
359 359  Static Source Code Analysis
360 360  )))|(((
361 361  checkstyleConfig
... ... @@ -380,7 +380,29 @@
380 380  )))|(((
381 381   Name of a config file to use for yamllint. If not set a best-practice[[ relaxed configuration >>url:https://prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/sdcloud-caas-jenkins-libs/browse/resources/com/tsystems/sdc/jenkinslib/yamllint.yml||shape="rect"]]is used which is different from the original yamllint[[ config>>url:https://yamllint.readthedocs.io/en/stable/configuration.html#default-configuration||shape="rect"]].
382 382  )))
379 +|skipDependencyCheck|false|Set to true to skip the dependency-check.
383 383  |(((
381 +dependencyCheckTool
382 +)))|(((
383 +'dependency-check'
384 +)))|(((
385 +Defines which named dependency-check tool should be used.
386 +)))
387 +|(((
388 +dependencyCheckArgs
389 +)))|(((
390 +'~-~-disableAssembly ~-~-nvdValidForHours 720'
391 +)))|(((
392 +Addtional arguments which are be passed to dependency-check. See [[Dependency>>url:https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html||shape="rect"]][[ Check CLI Arguments>>url:https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html||shape="rect"]] for more information.
393 +)))
394 +|(((
395 +dependencyCheckNvdApiKeyCredentialsId
396 +)))|(((
397 +'dependency-check-nvdapikey'
398 +)))|(((
399 +If you have your own NVD API Key, set it as a credential of type text in Jenkins. Then specify the credential id using this argument. It will be automatically passed to dependency-check. There will be no error if no credential is found. Just the NVD download will be slower. Please note, on DevOps-as-a-Service a shared NVD API Key is automatically supplied for the default credential id.
400 +)))
401 +|(((
384 384  sonarQube
385 385  )))|(((
386 386  true for the defaultBranch and for pull-requests, if a SonarQube version is detected which supports scanning multiple branches
... ... @@ -431,13 +431,6 @@
431 431  |sonarQualityGate| |Sets the desired quality gate to use for the scan result in SonarQube.
432 432  If not specified, the quality gate is not changed.
433 433  As a default, SonarQube will use the quality gate "Sonar way" for new scan results.
434 -|=(% colspan="1" rowspan="5" %)Dependency Check|skipDependencyCheck|false|Set to true to skip the dependency-check.
435 -|dependencyCheckTool|'dependency-check'|Defines which named dependency-check tool should be used.
436 -|dependencyCheckMvnArgs|'-DassemblyAnalyzerEnabled=false'|Additional arguments which are be passed to dependency-check for maven projects.(((
437 -See [[Dependency Check Maven Configuration>>https://jeremylong.github.io/DependencyCheck/dependency-check-maven/configuration.html]] for more information.
438 -)))
439 -|dependencyCheckArgs|'~-~-disableAssembly'|Addtional arguments which are be passed to dependency-check. See [[Dependency>>url:https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html||shape="rect"]][[ Check CLI Arguments>>url:https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html||shape="rect"]] for more information.
440 -|dependencyCheckNvdApiKeyCredentialsId|'dependency-check-nvdapikey'|If you have your own NVD API Key, set it as a credential of type text in Jenkins. Then specify the credential id using this argument. It will be automatically passed to dependency-check. There will be no error if no credential is found. Just the NVD download will be slower. Please note, on DevOps-as-a-Service a shared NVD API Key is automatically supplied for the default credential id.
441 441  |=(% colspan="1" rowspan="2" %)Dependency Track|depTrackCredentialsId|'PROJECTKEY-deptrack-projectcreator'|(((
442 442  Id of the Jenkins Credential which has to be used to authenticate to Dependency Track for publishing the SBOM.
443 443  )))
... ... @@ -444,10 +444,6 @@
444 444  |depTrackClassifier|'application'|The component type (e.g. application, library, firmware, ...) that should be set in the SBOM file.
445 445  Will be later shown as classifier for the project in Dependency Track.
446 446  See [[CycloneDX Metadata Component Type>>https://cyclonedx.org/docs/1.6/json/#metadata_component_type]] for supported values.
447 -|=(% colspan="1" rowspan="2" %)Trivy|trivySeverity|'High'|String which sets the minimum severity of Trivy findings that has to be reached to mark the Trivy Results stage as unstable.
448 -Possible values are: "None", "Unknown", "Negligible", "Low", "Medium", "High", "Critical".
449 -|trivyBuildResult|'SUCCESS'|String which sets the overall build result when the result of the Trivy scan reaches trivyServerity.
450 -Possible values are: "SUCCESS", "UNSTABLE" or "FAILURE"
451 451  |=(% rowspan="7" %)(((
452 452  Deployment
453 453  )))|(((
1762161476370-318.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.borisfolgmannt-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -79.4 KB
Content
1762161531690-966.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.borisfolgmannt-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -82.3 KB
Content
© 2018-2025 T-Systems International GmbH