-
Notifications
You must be signed in to change notification settings - Fork 13
Extensions
The Seed plug-in defines several extension points.
The Docker image provided by the Seed plug-in has a predefined seed job, but in most of the cases, you'll define yourselves this seed job using a Project seed generator build step.
You are free to define any other additional step you need in this job, and/or to define several types of seed jobs.
See the [pipeline extensions documentation](Pipeline extensions) to know how to have specific steps added to a branch seed job.
See the [project extensions documentation](Project extensions) to know how to have specific steps added to a project seed job.
See [Branch strategies](Branch strategies).
To be documented
By default, the branch seed and the underlying branch pipeline generator are passed only the default Seed parameters, like BRANCH and SEED_BRANCH.
It is possible to allow for additional parameters which are entered at project seed level and then propagated at lower levels.
This is done at configuration level - by declaring branch-parameters at project, class or global level. Each parameter is a name and a description. Parameters will be entered as string parameters.
For example:
classes:
- id: my-class
branch-parameters:
BRANCH_PARAM: Additional parameterFor a project using the my-class class, when its project seed job is fired, an additional parameter BRANCH_PARAM will be requested, on top of the Seed default BRANCH parameter.
This BRANCH_PARAM value will be available in the branch seed parameter and also in the pipeline script, like in seed/seed.groovy.
See [Branch SCM path](Branch SCM path).
To be implemented and documented. At the moment, only Git and Subversion are supported out of the box.
- Installation
- Development
- [Pipeline extensions](Pipeline extensions)
- [Pipeline library](Pipeline library)