Closed Bug 1187946 (nexus-5l-builds) Opened 4 years ago Closed 4 years ago

Enable Nexus 5L builds in taskcluster

Categories

(Taskcluster :: General, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: selenamarie, Assigned: mshal)

References

Details

Attachments

(1 file)

Move builds for Nexus 5L into Taskcluster.
Alias: nexus-5l-builds
Summary: nexus → Enable Nexus 5L builds in taskcluster
Most of the nexus-4 configuration was already in tree, but not enabled. I fixed it so it builds, and added nexus-5l. I verified on try by temporarily adding it to try/job_flags.yml, though we don't currently seem to build nexus on try so that isn't part of this patch. Is there a way to verify that the builds actually built correctly? ie: that the eng builds are actually eng builds, and/or it actually is a fully functioning nexus build? I don't have a device to test it on.

try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=9ed4c64ea786
Assignee: nobody → mshal
Attachment #8662722 - Flags: review?(wcosta)
Comment on attachment 8662722 [details] [diff] [review]
0001-Bug-1187946-enable-Nexus-B2G-builds-in-Taskcluster.patch

Review of attachment 8662722 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good, you just need to add the phone names to base_job_flags.yml file [1]

[1] https://dxr.mozilla.org/mozilla-central/source/testing/taskcluster/tasks/branches/base_job_flags.yml#8
Attachment #8662722 - Flags: review?(wcosta) → review+
I updated base_job_flags.yml & also added blobfree for nexus-5l per our IRC conversation. The nexus-4 builds failed with blobfree enabled, so if that's required someone will have to dig into it some more :)
https://hg.mozilla.org/mozilla-central/rev/d09a02afe050
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
That is lacking exposing the blobfree distribution too.
(In reply to Alexandre LISSY :gerard-majax from comment #7)
> That is lacking exposing the blobfree distribution too.

It's a bug in fact, the present patch was okay :)
You need to log in before you can comment on or make changes to this bug.