Run checks done in push-apk at promote phase, instead of the very last task of the pipeline

RESOLVED FIXED

Status

enhancement
RESOLVED FIXED
3 months ago
3 months ago

People

(Reporter: jlorenzo, Assigned: jlorenzo)

Tracking

(Depends on 1 bug)

unspecified
Dependency tree / graph

Firefox Tracking Flags

(firefox68 fixed)

Details

Attachments

(3 attachments)

Assignee

Description

3 months ago

Over the last 2 weeks, push-apk broke twice: bug 1539933 and bug 1536522. This is not the first time push-apk breaks. Oftentimes, it catches real problems in the APKs. For instance:

These breakages which happen at the very end of the pipeline could be copied in their own task that runs at each push. This way, we know what push caused the breakage.

Therefore, I'm going to make the mozapkpublisher checks as a standalone script. This script will be called in a docker-worker task. The push-apk task will keep making these checks, no matter if they were run before.

Assignee

Comment 1

3 months ago

Run checks done in push-apk in promote-phase, instead of the very last task of the pipeline

Assignee

Comment 2

3 months ago

We don't have shippable builds on Fennec, so running these checks on hg-pushes can't be done. Instead, we can mitigate the problem by having the checks run at the beginning of release promotion.

Assignee: nobody → jlorenzo
Summary: Run checks done in push-apk on hg-pushes, instead of the very last task of the pipeline → Run checks done in push-apk at promote phase, instead of the very last task of the pipeline

Comment 5

3 months ago
Pushed by jlorenzo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b979e271d955
Run checks done in push-apk in promote-phase, instead of the very last task of the pipeline r=mtabara

Comment 6

3 months ago
bugherder
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Assignee

Updated

3 months ago
Blocks: 1543373
Regressions: 1543373
You need to log in before you can comment on or make changes to this bug.