TestRail + Jenkins Integration — Automate Your Test Result Sync

Your Jenkins pipeline runs hundreds of tests on every build. Your QA team manages test cases in TestRail. But getting results from one system to the other? That's still a manual process for most teams.

It doesn't have to be. BuildButler bridges Jenkins and TestRail so that every build automatically creates test runs, populates results, and keeps your TestRail project up to date.

Why manual syncing doesn't scale

When your project has 50 tests and one Jenkins job, manual uploads are annoying but manageable. When you have 2,000 tests across 15 jobs running multiple times a day, manual syncing breaks down:

• Results lag behind builds — by the time someone uploads yesterday's results, three more builds have run
• Test cases drift — new tests in CI don't exist in TestRail, so results are incomplete
• Coverage gaps — some jobs never get uploaded because nobody remembers to do it
• No history — without consistent uploads, you can't track test trends over time

How BuildButler automates TestRail sync

BuildButler watches your Jenkins builds and exports results to TestRail automatically. Here's what it does:

Test case creation

When BuildButler encounters a test that doesn't exist in TestRail, it creates the test case in the specified section. You control the case type, priority, and custom fields. Existing tests are matched by name or full class path.

Test runs and plans

Each build creates a test run in TestRail. You can organize runs under test plans, associate them with milestones, and auto-close runs after export. Template variables let you name everything dynamically:

{
  "jobPattern": "backend/*",
  "project": "Backend",
  "testPath": "Automated Tests/API",
  "testRun": "{jobName} #{buildNumber}",
  "testPlan": "Sprint {date}",
  "milestonePath": "Releases/{branch}",
  "closeRun": true
}

Result mapping

Test statuses map directly: pass, fail, skip, error. BuildButler handles the translation from JUnit/TestNG/Allure/Cucumber/Robot format to TestRail's result model.

Multi-job configuration

Most teams have multiple Jenkins jobs that need to sync with different TestRail projects or sections. BuildButler uses glob patterns to route jobs:

[
  {
    "jobPattern": "backend/*",
    "project": "Backend",
    "testPath": "Automated Tests/API",
    "testRun": "{jobName} #{buildNumber}"
  },
  {
    "jobPattern": "frontend/*",
    "project": "Frontend",
    "testPath": "Automated Tests/UI",
    "testRun": "{jobName} #{buildNumber}"
  },
  {
    "jobPattern": "**/e2e-*",
    "project": "E2E",
    "testPath": "End to End",
    "testPlan": "E2E {branch}",
    "closeRun": false
  }
]

One configuration. Every job covered. Results flowing on every build.

Beyond Jenkins

BuildButler's TestRail integration isn't limited to Jenkins. It works with GitHub Actions, GitLab CI, TeamCity, and BuildKite. If your team uses multiple CI systems, all results flow into the same TestRail project.

Getting started

1. Sign up for BuildButler — TestRail integration is included on all plans
2. Connect your CI system
3. Enter your TestRail credentials in System Settings
4. Define your job mapping rules as JSON
5. Run a build — results appear in TestRail automatically

Read the full TestRail integration guide for configuration details, or see the complete field reference.