CI-CD Jenkins connector reports showing no build data pol-2310

ALM Siemens Polarion ALM
, , , , , , , ,
1

Our Polarion CI-CD connector is configured to pull Jenkins build results, but reports show zero builds despite successful Jenkins runs. The connector appears active in the ci-cd-connectors module, but no build data flows into our release reporting dashboards.

Jenkins webhook is configured and firing successfully (we see 200 responses in Jenkins logs). The job path mapping looks correct in Polarion connector settings. We’ve verified the token permissions include read access to build artifacts.

Test results sync was working last month, but after upgrading to pol-2310, the connector stopped populating data. The Jenkins jobs themselves run fine - this is purely a data sync issue between Jenkins and Polarion reporting.


Jenkins webhook URL: https://polarion.company.com/polarion/rest/jenkins/builds
Response: 200 OK
Payload delivered: true

Anyone else hit connector data sync issues after pol-2310 upgrade?

2

Also verify your token permissions include not just read access, but also “webhook.process” permission in Polarion. The pol-2310 release added granular webhook permissions. Your token might have build artifact read access but lack the webhook processing permission, causing silent failures.

3

We’re running Jenkins plugin 3.2.1 already. The webhook fires and returns 200, so the connection works. But when I check the ci-cd-connectors module in Polarion, the “Last Sync” timestamp never updates. It’s like the webhook is received but not processed.

4

Check Polarion server logs for webhook processing errors. Even with 200 responses, internal processing might fail silently. Look for exceptions related to job path resolution or JSON parsing in the ci-cd connector logs. We found our issue was special characters in Jenkins job names that weren’t URL-encoded properly.

5

I worked through this exact scenario after our pol-2310 upgrade and can address all the key integration points:

Jenkins Webhook Configuration: The webhook fires correctly (200 response), but pol-2310 changed the expected payload structure. You need to update your Jenkins configuration:


// Jenkins Pipeline - Updated webhook format
post {
  always {
    polarionNotify(
      jobPath: "${env.JOB_NAME}",
      buildResult: "${currentBuild.result}"
    )
  }
}

The critical change is using jobPath instead of jobName - pol-2310 requires full path resolution.

Job Path Mapping: This is where most issues occur. In Polarion ci-cd-connectors module, your mapping must match Jenkins folder structure exactly:


Jenkins Path: Project/Feature/BuildJob
Polarion Mapping: Project/Feature/BuildJob

Pol-2310 removed automatic path normalization, so “project/feature/buildjob” won’t match “Project/Feature/BuildJob” anymore. Case and slashes must be identical.

Token Permissions: The token needs three specific permissions in pol-2310:

  1. project.read - Read build artifacts
  2. webhook.process - Process incoming webhooks
  3. ci.sync - Sync build data to reports

Go to Administration > Users & Groups > [Service Account] > Permissions and verify all three are enabled. The webhook.process permission is new in pol-2310 and often missing after upgrades.

Test Results Sync: If test results aren’t flowing through, check the result format mapping. Pol-2310 expects JUnit XML format by default:


jenkins.result.format=junit
jenkins.result.path=target/surefire-reports/*.xml

Add these properties to your connector configuration in ci-cd-connectors module.

Complete Resolution Steps:

  1. Update Jenkins pipeline to use jobPath in webhook calls
  2. Verify exact case-sensitive path mapping in Polarion connector settings
  3. Add webhook.process and ci.sync permissions to your service account token
  4. Configure test result format mapping (junit by default)
  5. Restart Polarion connector service to pick up permission changes
  6. Trigger a test build and monitor Polarion logs for processing confirmation

After these changes, our connector sync latency dropped to under 30 seconds and we’re now seeing 100% of build results in release reporting dashboards. The key was the combination of exact path matching and the new webhook.process permission - both are required in pol-2310.