Respin yahoo-test partner repacks



2 years ago
2 years ago


(Reporter: mkaply, Assigned: aki)


Firefox Tracking Flags

(Not tracked)




2 years ago
We need to respin the yahoo-test repacks, specifically:

 <project name="yahoo-test" path="partners/yahoo-test" remote="mozilla-partners" revision="master"/>

Some changes related to the default search didn't get made.

This builds should end up in:
Hey Mike, I was wondering how urgent this is and what's the ETA for this? I was thinking to give a hand and jump in to learn the process in the funnelcakes. But if this is urgent, I'll defer to :aki as he's got the best knowledge. Otherwise, if it can wait a few more days, I could jump in to increse the bus factor here.
Flags: needinfo?(mozilla)
This is super urgent.  (Kaply's on PTO.)
Flags: needinfo?(mozilla)
(In reply to Mike Connor [:mconnor] from comment #2)
> This is super urgent.  (Kaply's on PTO.)

Okay then. I'll defer to :aki. Will try to get in the cycle at the next one.

Comment 4

2 years ago
Currently, the DISTRONAME we pass to the script matches against the directory in `desktop/`, not the partner name [1].
I noticed that the yahoo-test names [1] are not unique; they're shared with the names in the yahoo repo [2].
If we proceed as is, we'll also be re-repacking some yahoo partner-repacks along with the yahoo-test repacks.

We can:

- rename the yahoo-test directories in yahoo-test/desktop/ to start with yahoo-test; there are no yahoo-test directories in the yahoo repo
- rebuild yahoo-test, with the assumption that some or all yahoo repacks will also be rebuilt, and rely on the bucket and cdn rules to prevent overwriting
- change the script/docs to allow for specifying repacks by partner.  Not sure how tricky this one will be.
- something else I'm not thinking of

:mconnor, do you have a preference?

Assignee: nobody → aki
Flags: needinfo?(mconnor)

Comment 5

2 years ago
Done.  We had to respin all yahoo and yahoo-test repacks for this.
Flags: needinfo?(mconnor)


2 years ago
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.