Jenkins running Android Lint and Monkey

Enter the configuration page for the corresponding job.
Lint:
1. Add lint after adding build operations

2. Add the lint standard in the advanced

Monkey
1. Before running monkey, you need to install the APK package to the simulator or mobile phone, adding "Install Android packages" in the Add build step.
When build succeeds, an APK is generated under the corresponding version of the path, for example:

At the same time, Jenkins current project workspace will also produce apk, the path of the APK only one group, each build will be updated after the success, so we fill in the APK file is the path to ensure that every monkey run is the latest apk


Additionally, after the build operation add Archive the artifacts

2. Add Monkey Tester In the increase build operation

Fill in the package name at Packages IDs.
Event count fills in the number of random events
Delay between events Add event interval time (MS)
For example, 1500x200ms, it takes 5 minutes to run the monkey in theory.

Adding monkey result in post-build operations

where filename,
If it's empty, you'll need to create a new file called Monkey.txt in your local project's root directory. Note that the remote engineering code is downloaded and stored locally on the path, not in Jenkins.

Jenkins running Android Lint and Monkey