Bug 458337 - HUDSON_BUILDS stores matrix job builds with non-unique identifiers
Summary: HUDSON_BUILDS stores matrix job builds with non-unique identifiers
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: 3.1.2   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Bob Foster CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard: candidate-4.0.0
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-24 13:06 EST by Bob Foster CLA
Modified: 2015-04-21 13:42 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Foster CLA 2015-01-24 13:06:06 EST 
Unfortunately, Bug 398310 didn't quite fix builds for matrix jobs. There is no project identifier; instead builds are stored in folders named by the matrix axis values, e.g., "bar,JDK7" in the order they appear starting from the configurations folder. Since it is possible for two different jobs to have the same matrix parameters, these names are ambiguous.

I have confirmed that when you create two matrix jobs with the same axes, e.g., JDK7 and JDK8, the latest build from either job overwrites data, e.g., lastSuccessfulBuild, written by the other job.