Releases: shasait/cipa
Releases · shasait/cipa
4.2.0
- Added
JobParameterContainer.addStringParameter(String name, String defaultValue, String description, String regex, String failedValidationMessage):void(this requires the Validating String Parameter Plugin) - Added
JobParameterContainer.addCustomParameter(ParameterDefinition parameter):void
4.1.2
4.1.1
4.1.0
Changes:
- Node specific tools and late adding of tools (see
CipaToolContribution):- E.g. to use a node location specific Maven configuration
- Transforming of SCM-URLs (see
ScmUrlTransformer):- To use node location specific replicas
- Maven execution using builder like pattern:
- E.g.:
script.mvn().addGoals(['clean', 'package']).execute()
- E.g.:
- Automatic retry for Maven repo access race condition
- If two parallel activities use the same Maven repo and both download the same new artifact
- Cleaner but slower is usage of withPrivateRepo
- Added
CipaRunHandlerfor logic before and/or after the pipeline. - Added
PScript.echoNonCPS(...)for simple logging inNonCPSannotated code - Added
PScript.encapsulateStringInSingleQuotesForShell(...)for quoting of a String for shell use, e.g. filepath.
4.0.0
Changes:
- Named beans to better support multiple beans of the same type:
- Added an optional
nameargument toaddBean,findBeanand related methods inCipa
- Added an optional
- Added
CipaArtifactStorefor managing build artifacts and stashes - more flexible than the Jenkins built-in one - Added
CipaNodeHandlerto execute before and after activities are executed on it- E.g. for initialization or cleanup
- Clearer separation of internal and public API - introduced interfaces like
CipaActivityInfo,CipaActivityRunContext