Closed Bug 833555 Opened 11 years ago Closed 11 years ago

Self-serve build API page for UX branch says "Failed: Revision xxx not found on branch ux"

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jaws, Assigned: nthomas)

References

(
URL
)

Details

A few patches have been pushed to the UX branch since bug 816300 was fixed. Builds don't appear to be building on the UX branch though. Visiting the Self-serve build API page for the tip revision shows the following:

{
  "msg": "Revision 5b0d4917f10b not found on branch ux",
  "status": "FAILED"
}
Blocks: 816300
Moving to the right component.

After the repo was reset buildbot was asking pushlog for changes since the last revision in the old repo. IIRC that scenario normally requires a restart of a build scheduler (although hg.m.o is returning a 500 error for http://hg.mozilla.org/projects/ux/json-pushes?full=1&fromchange=29a10d95f4b4 so we could detect that and reset the state or something).

In the meantime a reconfig was done which resets the poller state, and that figures out the new tip is 5b0d4917f10b but ignores any changes prior to that. The quick fix here is to push a whitespace change to get new builds.
Assignee: server-ops-devservices → nobody
Component: Server Operations: Developer Services → Release Engineering: Developer Tools
QA Contact: shyam → hwine
Bug 774862 disabled the code we have to handle the repo-reset situation.
I've forced some builds on 5b0d4917f10b to get you back in business. Please reopen if subsequent pushes don't result in builds. Will follow up with IT to get us to fix up buildbot when repos are reset.
Assignee: nobody → nthomas
Status: NEW → RESOLVED
Closed: 11 years ago
Priority: -- → P2
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.