| commit | 111fcf1e89f6e343bef6af9ded293ef158655805 | [log] [tgz] |
|---|---|---|
| author | Konrad Windszus <kwin@apache.org> | Tue Mar 15 19:07:35 2022 +0100 |
| committer | Konrad Windszus <kwin@apache.org> | Tue Mar 15 19:07:35 2022 +0100 |
| tree | 57dfc1bebb9fc8d7099b791bb3fdfcc69621c029 | |
| parent | 8540ab8d8dce5405998b5bc7371c0fb58ad757d8 [diff] |
clear workspace prior to running IT stage/deploy stage
This library is used for all FileVault Jenkins builds and enabled on https://ci-builds.apache.org/job/Jackrabbit/job/filevault/
It follows the structure outlined at https://www.jenkins.io/doc/book/pipeline/shared-libraries/
It is supposed to be called in a Jenkinsfile like this
vaultPipeline('ubuntu', 11, '3', {
vaultStageBuild(['ubuntu', 'Windows'], [8, 11, 17], ['3', '3.6.3'], 'apache_jackrabbit-filevault-package-maven-plugin')
vaultStageDeploy()
}
)
The vaultPipeline step encapsulates the main build environment parameters: The first argument is the main node label to build with, the second one the main JDK version, third argument the main Maven version The fourth argument is a closure containing the actual stages where each may be one of
vaultStageBuild: the actual Maven build and SonarQube execution (the latter only for the main environment)vaultStageIT: an isolated execution of just the integration testsvaultStageDeploy: the stage to deploy the previously built Maven artifacts to the ASF Snapshot Repository (depends on 1.)For the parametrisation of those individual stages refer the source code.