commit | 7e5d5582aeeeb6614ea30a7813f0646ad7d5f3e0 | [log] [tgz] |
---|---|---|
author | Konrad Windszus <kwin@apache.org> | Thu Mar 17 09:36:52 2022 +0100 |
committer | Konrad Windszus <kwin@apache.org> | Thu Mar 17 09:36:52 2022 +0100 |
tree | 4bd52cee421f9c78d6c9501f4372d85d9b7a1d4c | |
parent | d2434352d5029f87ba0e5c5dc98e8f09fb2060db [diff] |
remove workaround related to "Unexpected CryptoAPI failure generating seed" https://issues.apache.org/jira/browse/INFRA-22997
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.