Extensions
The Seed plug-in defines several extension points.
Additionally to the Project generation step, you are free to define any other step you need in the Seed job, and/or to define several types of seed jobs.
See the [project extensions documentation](Project extensions) to know how to have specific steps added to a project seed job.
See the [pipeline extensions documentation](Pipeline extensions) to know how to have specific steps added to a branch seed job.
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 Extra branch parameters for the project. Each parameter is a name and a description. Parameters will be entered as string parameters.
For example:
When a project seed, generated for this definition, is fired, those extra parameters will be asked to the user:
In this sample, the OWNER and BRANCH_TYPE values will be available in the pipeline script.
See [Branch SCM path](Branch SCM path). This is a particular case of branch parameter.
By default, only GitHub WebHooks and HTTP connectors are supported, but custom ones can be added. See the connector documentation for more information.
To be implemented and documented. At the moment, only Git and Subversion are supported out of the box.
- Installation
- Development
- Connectors
- [Pipeline extensions](Pipeline extensions)
- [Pipeline library](Pipeline library)