Before you begin
You have defined all the parameters necessary to build your project artifacts, see Specify the parameters to generate and deploy the sources.
Make sure your Talend CommandLine
application points to the Jenkins workspace where your project sources are
- If you installed Talend CommandLine as a service on Windows, you need to go to the service installation directory and open the file <service_path>/conf/wrapper.conf to edit the wrapper.app.parameter.7 parameter value and point to the Jenkins workspace where your project sources are stored.
- If you installed Talend CommandLine as a service on Unix, you need to edit the file start_cmdline.sh that calls the service script.
- If you did not install Talend CommandLine as a service, edit
the .bat or .sh file of Talend CommandLine to change the
data parameter value.
- Start the Talend CommandLine service.
- From the Jenkins home page, select the Generate_Execute_Deploy project.
- Click Build with parameters in the left panel.
In the list, select the parameters to build your project and execute the Maven
phase of your choice.
Tip: If you are building your project for the first time, you can select generate-sources to only test the generation of your source code.
If you have selected the deploy phase in the list, you
have to select the Nexus repository in which you want the packaged artifacts to
- Click Build.
The build is launched and your project is being processed according to the Maven phase that has been defined.
The best practice is to use the deploy phase in order to generate the source code, compile it, test it, package it and then deploy the packages into Nexus.
You can see their results displayed:
- in Jenkins: the detail of your results can be found in the Console
Output view of the specific builds.Example where you can see one failure on the execution of the test named test_process_client_file):Example where 6.3.1-SNAPSHOT artifacts are being deployed to the TALEND group in the repository):
in Jenkins: a diagram that represents graphically the status of the last executions of the project (here you can see one failure out of a total of six tests):
in your Nexus web application: you can find the artifacts deployed in the defined repository: