Before you begin
- In the GenerateSources project configuration, set the path to the BuildJob_pom.xml file holding the instructions to generate sources in the Root POM field of the Build area.
In the Goals and options field, enter the Maven
instruction to generate sources.
Use local-generate to generate sources in script mode (recommended), or use generate to generate sources remotely.
(Optional) If you want to perform a non-local generation (not recommended), set
the other necessary Maven parameters in the MAVEN_OPTS
field of the Advanced part of the
Build area (plugin execution information as well as
parameters needed to generate the sources).
Tip: Note that the Maven documentation of the CI Builder plugin is embedded in the CI Builder archive file, see the files in the <CIBuilder_home>/help folder for more information.
-Dcommandline.workspace=<jenkins_path>/workspace/GenerateSources/projects -Dcommandline.host=localhost -Dcommandline.port=8002 -Dcommandline.email@example.com -DprojectsTargetDirectory=<jenkins_path>/workspace/RunTests/projectSources -DitemFilter=(type=process)and(path=TEST)
For more information on these parameters, see Create the POM file to generate sources.
For examples of filters you can apply to the execution of your project items, see How to filter the execution of your project on a single Job or specific Jobs.Tip: The only requirement is to store all projects in the workspace folder, this means you have the possibility create a Jenkins task that clones the projects and copy them (folders only) to the workspace.
If your project is on Git, you need to specify the folder in which your
projects will be checked out (Use custom workspace) in
the Advanced part of the Build
area. This path needs to be the same as the one you will use in your Talend CommandLine (see Executing the Tests).
You also have the possibility to check out one specific project in your repository by entering its name inpaths.
In the Advanced part of the Build
area, select Settings file in filesystem in the
Settings file list and point to the Maven settings
file of the Studio with all the dependencies needed to generate the
- (Optional) Add a post-build action to get it to run the next project, the RunTests project, that will run all the tests.