Installation
Install the Seed plug-in like any other plug-in. It relies on several plug-ins and those will be installed if not present.
As soon as installed, it's ready to be used.
You can create as many seed jobs as you need, with different parameters.
Create a Freestyle project job, using any name - but I think having seed in the job name is a good start.
Add a Project folder generation build step where fields are defined directly or using job parameters. See Configuration for a list of all configuration attributes.
A typical seed project will have parameters in order to fill the configuration of the Project folder generation build step. Not all of them are required, according to your needs. Typical parameters will be:
-
PROJECT- the ID of the project to create a project seed for -
PROJECT_SCM_TYPE- the type of SCM to use (gitorsvn) if variable from one project to the other -
PROJECT_SCM_URL- the SVN or Git URL of the project -
PROJECT_SCM_CREDENTIALS- UUID of the Jenkins credentials to use (see [SCM credentials](SCM credentials)) -
PROJECT_TRIGGER_TYPE- set if the generated project must be triggered through SCM events like GitHub. If not set, the project cannot be triggered remotely, only manually or through SCM polling. -
PROJECT_TRIGGER_SECRET- used to enable security when triggering pipeline events through SCM events - not all end points support this feature.
In this sample, the SCM type is fixed to git while all other values depend on the parameters of the job:
- Configuration - configuration parameters for the seed jobs
- Triggering - how to trigger pipeline events from SCM events
- [SCM credentials](SCM credentials) - how to manage the SCM credentials for the seed jobs
- Extensions - how to extend the seed plugin