Closed Bug 649046 Opened 14 years ago Closed 14 years ago

Implement mobile tests on project branches

Categories

(Release Engineering :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 645168

People

(Reporter: stechz, Unassigned)

Details

We are currently seeing a pattern where many developers work on cedar when no sheriff is around. Unfortunately, there are no mobile tests on cedar so we don't see any regressions there. This weekend when a cedar merge occurred, we ended up with oranges on mobile, so it is more difficult to ascertain what the offending changeset was.
As I said on IRC, there is nothing specific about cedar.  This should happen on all project branches.
Summary: Implement mobile tests on cedar branch → Implement mobile tests on project branches
Component: Orange Factor → Release Engineering
Product: Testing → mozilla.org
QA Contact: orangefactor → release
Version: unspecified → other
Doing Cedar and Try now, in bug 645168; any other requests?
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
(In reply to comment #2)
> Doing Cedar and Try now, in bug 645168; any other requests?

Can't we do this on all branches?
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.