Closed Bug 492852 Opened 16 years ago Closed 16 years ago

Allow branchName to be passed to build factory

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kairo, Assigned: kairo)

Details

Attachments

(1 file)

We're currently assuming that branchName for build factories is the last part of the path of the repoPath passed to the factory, and base several things, like paths for logs, hourly and nightly builds as well as triggered factory names on that. When building different configs of builds from the same top-level repo, like with comm-central importing mozilla-1.9.1 or mozilla-central, this is not quite what we want, so we need a chance to pass in a different value as branchName.
This patch allows us to pass in a branchName but still falls back to what we did previously, so existing configs should not be affected.
Assignee: nobody → kairo
Status: NEW → ASSIGNED
Attachment #377255 - Flags: review?(bhearsum)
Attachment #377255 - Flags: review?(bhearsum) → review+
Comment on attachment 377255 [details] [diff] [review] allow passing branchName Looks fine, and safe.
Attachment #377255 - Flags: checked‑in+
Comment on attachment 377255 [details] [diff] [review] allow passing branchName changeset: 286:58aea7b55efd
Checked in, so should be fixed - the new SeaMonkey buildbots have been running with this locally applied and passing branchName=branch for a few days and everything looks good. :)
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Sorry, branchName=name in the master.cfg, of course.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: