commit | d36cbc07e783bf238c60ce26f562c4ca85020cad | [log] [tgz] |
---|---|---|
author | Konrad Windszus <kwin@apache.org> | Tue Jul 05 09:42:10 2022 +0200 |
committer | Konrad Windszus <kwin@apache.org> | Tue Jul 05 09:42:10 2022 +0200 |
tree | 6c533e18cc0632cc754f95136c641a3060890f2a | |
parent | 116f1bb9bad5f192c18b1018c8c767033157c651 [diff] |
improve readme
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(['Windows'], [8, 17], ['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
vaultStageSanityCheck
: a quick Maven build supposed to fail fast and executed before triggering expensive parallel builds with vaultStageBuild
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.