Configuring Jenkins

Configure Jenkins to run your API tests. Jenkins is a highly extensible system and most things are done via plugins. That is why there is a bit of configuration to do on Jenkins before you can run your tests.

Before you begin

You have a GitHub account.
You know how to launch Talend Cloud API Tester from the CLI.
You have installed the Talend Cloud API Tester Maven plugin.

Procedure

Push your scenario to a GitHub repository.
Make sure to push the two test files:
- The JSON file containing your scenario
- The pom.xml configuration file
Information noteNote: Talend Cloud API Tester has a GitHub integration to help you push your test files to GitHub.
Go to Manage Jenkins > Manage plugins > Available, then search for and install the Pipeline Maven Integration Plugin and the Junit Attachments Plugin.
Go to Manage Jenkins > Global tool configuration.

You have two sections for JDK and Maven configurations. Configure both of them by clicking Add JDK and Add Maven.

Information noteNote: The name you set for your Maven installation will be re-used later on. Copy it somewhere so you don't have to come back to the configuration page.
Open the credentials page from the left menu and click Global next to the Jenkins store.

Some information is too sensitive to be pushed on a repository. For this type of information Jenkins has a credentials store. You can define credentials in there and consume them in your jobs.
Click Add credentials and enter your information as follows, with your Account ID in the Secret field. Then click OK.
Repeat the operation to add credentials for your API key with the ID CONTACTS_API_KEY, for example.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here