Configure Jenkins
1 min read
A Jenkins integration lets automated test runs start Jenkins jobs and import the reports they produce. Unlike GitHub and GitLab, Jenkins is CI-only — there are no capabilities to choose, and it does not file defects.
Before You Start
Section titled “Before You Start”Prepare these Jenkins details:
- The Jenkins URL, for example
https://jenkins.example.com - A Username
- An API Token for that user
Generate the API token from the user’s own Jenkins profile, under Configure → API Token. Use an account that can build the jobs you intend to point test runs at — Hawzu can only start what that user could start by hand.
Add Jenkins
Section titled “Add Jenkins”-
Open the workspace Integrations page and select Add Integration.
-
Search for Jenkins and select it.
-
Add an optional integration name and description.
-
Choose All Projects or Selected Projects.
-
Enter the Jenkins URL, username, and API token.
-
Use Test Connection, then save.
If the test fails, check the URL (including whether Jenkins is served from a sub-path), the username, and that the API token has not been revoked.
Using it in a test run
Section titled “Using it in a test run”Jenkins has no repository level — it is flat. When you pick Jenkins in a test run’s CI/CD Config, the next field is Job. For a job inside folders, the identifier is folder/job.
Triggering returns a queue item rather than a build number, so Hawzu resolves the build by polling shortly after. A brief gap between pressing Run and seeing a build number is expected.
See Create an Automated Test Run.