863765 - Apply patches to builds

Status: RESOLVED FIXED

(Firefox OS Graveyard :: GonkIntegration, defect)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

We have patches that we'd like to apply to our builds.  These patches are code differences in the AOSP repositories which we use, but which haven't been landed on our upstream repository.

Comment 1

[John Ford [:jhford] CET/CEST Berlin Time]

   b95a5cc..9a4dc85  master -> master
   9635c27..94519f4  v1-train -> v1-train
   bc902bf..956ee53  v1.0.1 -> v1.0.1

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

Attachment: script to update the patch queue

Comment 3

[Chris AtLee [:catlee]]

When/how will this script be invoked?

Can you not hardcode the github url so we can use git.m.o as well?

Comment 4

[John Ford [:jhford] CET/CEST Berlin Time]

the script is only attached for historical purposes.  It never needs to be run in production, only if we have to copy over new/more patches.  It's hardcoded because this is a simple script to update the gonk-patches repo.

Comment 5

[Chris AtLee [:catlee]]

Ok, so we just cleared this up on irc. tl;dr - no impact to releng builds

This script is run manually to update the contents of the gonk-patches repo. This repo has recently been added to the v1-train and v1.0.1 manifests, and so the 'repo' tool will pull in these patches as part of the source checkouts. The script is *not* invoked by build.sh, so there's no build-time dependency on github here.

Comment 6

[John Ford [:jhford] CET/CEST Berlin Time]

This landed a while ago.