Please follow the below steps to deploy RPi Java API Provider implementation to Artifact repositories from Jenkins job
1.Creating Jenkins job
- From Jenkins, select “New Item”,
- Specify name of the new job to be created.
- Select ‘OK’ button.
2. Configuration of Jenkins Job
- In ‘General’ settings, add proper description in the ‘Description’ section
- Check ‘Discard old builds’ checkbox
- In ‘Source Code Management’, select git and under ‘Repository’ add the repo detail
eg : ‘https://code.rdkcentral.com/r/rdk/tools/automatics/rpi-provider/java-handler’ and also add the repo credentials
- Also add the branch of the repository in ‘Branches to build’
eg : */rdk-next
- In ‘Build Environment’, select ‘Delete workspace before build starts’
- In the ‘Build’ settings, Click on ‘Add build step’ and Select ‘Invoke top-level Maven level targets’
- Add the following maven step in the text box
clean deploy -DaltDeploymentRepository=<id>::default::<Artifact repository path>
altDeploymentRepository – Specifies an alternative repository to which the project artifacts should be deployed - Click on Advanced button in ‘Invoke top-level Maven level targets’ and add following maven configuration. In the image shown below, maven settings.xml is place at /mnt/maven directory. Update the settings.xml path based on its location in partner's VM.
Reference - https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html
Save the Configuration
- Click on ‘Apply’ and ‘Save’