Bamboo build links not appearing in ELM 7.0.2 traceability-matrix reports

ALM IBM Engineering Lifecycle Management
, , , , , , ,
1

Bamboo build results stopped appearing in our ELM 7.0.2 traceability matrix reports. The builds complete successfully and Bamboo’s ELM publisher plugin shows “Published to ELM” status, but work items don’t link to builds in the traceability view.

We upgraded from 7.0.1 last week, and traceability worked fine before. Now compliance reports show missing build links, which fails our audit requirements. I verified the Bamboo publisher configuration - the ELM server URL and project area are correct.

When I check individual work items, the “Related Builds” section is empty. The Bamboo plan key mapping seems correct in ELM’s CI/CD integration settings. Is there a change in how OSLC link properties work in 7.0.2 that affects Bamboo integration?

2

Custom templates might be the issue. ELM 7.0.2 changed the default traceability matrix schema. If your custom template references old artifact types or link types, builds won’t appear even if links exist. Check if your template includes oslc_cm:TracksChangeSet link type for build associations.

3

Checked plan key mapping - we’re using the full format with project prefix. Still no links in traceability. Could this be related to the matrix templates? We’re using a custom template for compliance reporting.

4

I don’t see any errors in Bamboo publisher logs. The plugin reports successful publication. How do I verify if the OSLC link URIs are correct? Is there an API endpoint to query created links?

5

Here’s the comprehensive solution for restoring Bamboo build traceability:

1. Publisher URLs (Bamboo Configuration)

Verify Bamboo publisher plugin configuration:

Bamboo Plan → Tasks → ELM Publisher:


ELM Server URL: https://elm.company.com/ccm
Project Area: ProjectX
Build Result URL: ${bamboo.buildResultUrl}
Plan Key: ${bamboo.planKey}

Critical Change in 7.0.2: The publisher URL must include the project area context path:

  • Old (7.0.1): `/ccm/publish
  • New (7.0.2): `/ccm/oslc/projectareas/{area-id}/publish Update your Bamboo publisher configuration:

Publisher Endpoint: /ccm/oslc/projectareas/ProjectX/publish

2. OSLC Link Properties (Schema Changes)

ELM 7.0.2 updated OSLC namespace URIs for build links:

Old Link Property (7.0.1):

<oslc:link rdf:resource="http://bamboo/builds/123"
           xmlns:oslc="http://open-services.net/cm#"/>

New Link Property (7.0.2):

<oslc_cm:TracksChangeSet rdf:resource="http://bamboo/builds/123"
           xmlns:oslc_cm="http://open-services.net/ns/cm#"/>

Key changes:

  • Namespace: http://open-services.net/ns/cm# (added /ns/)
  • Property: TracksChangeSet (was generic link)
  • Prefix: oslc_cm (was oslc)

Verification Query:

curl -H "Accept: application/rdf+xml" \
  /ccm/oslc/workitems/12345/links
# Check for oslc_cm:TracksChangeSet elements

3. Plan Key Mapping (Integration Configuration)

ELM must recognize Bamboo plan keys for link resolution:

Admin Configuration:


ELM Admin → Integrations → CI Servers → Bamboo

Plan Mappings:
  PROJ-BUILD → ProjectX Work Items
  PROJ-RELEASE → ProjectX Releases

URL Template:
  https://bamboo.company.com/browse/${planKey}-${buildNumber}

Plan Key Format Requirements:

  • Must match Bamboo’s full plan key (project prefix + plan name)
  • Case-sensitive
  • Hyphen separator required

Common Mapping Errors:

  • Using plan name only: BUILD :cross_mark:
  • Correct format: PROJ-BUILD ✓
  • Missing project context: build :cross_mark:

4. Matrix Templates (Traceability Report Configuration)

Custom traceability templates must include build artifact types:

Template Configuration (Admin → Reports → Traceability Templates):

Add Build Artifact Type:

{
  "artifactTypes": [
    "oslc_cm:ChangeRequest",
    "oslc_cm:Requirement",
    "oslc_cm:Build"  // Add this
  ],
  "linkTypes": [
    "oslc_cm:TracksChangeSet",  // Build links
    "oslc_cm:Implements"
  ]
}

Matrix Column Configuration:


Columns:
  - Work Item ID
  - Title
  - Status
  - Related Builds (new column)
    Property: oslc_cm:TracksChangeSet
    Display: Build number + status

Complete Resolution Steps:

Step 1: Update Bamboo Publisher


1. Edit Bamboo plan → ELM Publisher task
2. Update Publisher Endpoint to: /ccm/oslc/projectareas/{area}/publish
3. Verify authentication token is valid
4. Save and run test build

Step 2: Verify OSLC Links

# Query work item links after test build
GET /ccm/oslc/workitems/{id}/links
Accept: application/rdf+xml

# Verify response contains:
<oslc_cm:TracksChangeSet rdf:resource=".../builds/123"/>

Step 3: Update Plan Key Mappings


ELM Admin → Integrations → Bamboo
Update each plan mapping:
  Old: BUILD → ProjectX
  New: PROJ-BUILD → ProjectX
Test link resolution with sample build URL

Step 4: Update Traceability Template


Admin → Reports → Traceability Templates → [Your Template]
Add artifact type: oslc_cm:Build
Add link type: oslc_cm:TracksChangeSet
Add column: Related Builds (property: TracksChangeSet)
Save and regenerate report

Step 5: Validate in Reports


Generate traceability matrix report
Verify "Related Builds" column shows Bamboo build links
Check compliance report includes build traceability

Migration Script (Bulk Link Update):

If you have existing builds that need link updates:

// Pseudocode - Key implementation steps:
1. Query all work items in project area
2. For each work item, fetch associated Bamboo builds from build history
3. Delete old oslc:link references (7.0.1 format)
4. Create new oslc_cm:TracksChangeSet links (7.0.2 format)
5. Update traceability index to reflect new links
// See documentation: ELM Migration Guide Section 12.3

Bamboo Plugin Update:

Ensure Bamboo ELM publisher plugin version compatibility:

  • ELM 7.0.2 requires plugin version 3.2.0 or higher
  • Update via Bamboo → Add-ons → Manage Add-ons → ELM Publisher
  • Restart Bamboo after plugin update

Troubleshooting Checklist:

✓ Publisher endpoint includes project area context

✓ OSLC link namespace uses `/ns/cm# ✓ Plan keys match Bamboo format with project prefix

✓ Traceability template includes Build artifact type

✓ Bamboo plugin version ≥ 3.2.0

✓ Authentication token has ccm.build.link.create permission

After completing these steps, Bamboo builds should appear in traceability matrix reports with proper OSLC link associations. The key changes are the publisher URL format and OSLC namespace updates in 7.0.2.

6

Check the Bamboo publisher logs for OSLC link creation errors. In 7.0.2, the link property URIs changed slightly - the namespace now requires /ns/cm# instead of /cm#. If your Bamboo plugin uses hardcoded old URIs, link creation succeeds but links aren’t recognized by the traceability matrix.