Closed Bug 1100755 Opened 10 years ago Closed 10 years ago

identify mozilla-* cset in the buildbotcustom code

Categories

(SeaMonkey :: Release Engineering, defect)

Product:
SeaMonkey
Component:
Release Engineering
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ewong, Unassigned)

Details

Currently, there is a step which shows the cset |hg identify -i| for the comm-* repo. Unfortunately, we don't know the c-set for the corresponding code in mozilla-*. It would help to know which m-* cset our c-* cset is building with.
Nevermind. I missed the "tinderboxprint_changeset" step which does display the m-? cset.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.