Skip to content

Extensions

Jump to bottom Edit New page
Damien Coraboeuf edited this page Jun 13, 2016 · 11 revisions

The Seed plug-in defines several extension points.

Adding steps to the root seed job

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.

Adding steps to the project seed job

See the [project extensions documentation](Project extensions) to know how to have specific steps added to a project seed job.

Adding steps to the branch seed job

See the [pipeline extensions documentation](Pipeline extensions) to know how to have specific steps added to a branch seed job.

Branch additional parameters

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.

TODO Example screenshot(s) - definition, entering, usage

For 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.

Branch SCM path

See [Branch SCM path](Branch SCM path). This is a particular case of branch parameter.

Connectors

By default, only GitHub WebHooks and HTTP connectors are supported, but custom ones can be added. See the connector documentation for more information.

Additional SCM support

To be implemented and documented. At the moment, only Git and Subversion are supported out of the box.

See also

Add a custom footer
Add a custom sidebar
Clone this wiki locally