1432701 - l10n not field not populated in ship-it for Thunderbird 52.6.0

Status: RESOLVED DUPLICATE of bug 1431344

(Release Engineering :: Applications: Shipit, enhancement)

Description

[Wayne Mery (:wsmwk)]

Building Thunderbird esr, typed 52.6.0 into ship-it. Build# was not populated, partials list was populated. l10n field should have populated from the prior build which was 52.5.2 but it had not, I had to populate it manually.

I did not notice whether the description to the right stated "Could not fetch l10n changesets! Are you sure the revision or the version you provided are correct?" 

I tried various combinations. In some cases l10n populated and in others it did not.

Comment 1

[Axel Hecht [:Pike]]

The l10n changesets part is a dupe of bug 1431344, see the discussion there for more background.

Comment 2

[Justin Wood (:Callek)]

:jlorenzo, any additional insight here?

Comment 3

[Johan Lorenzo [:jlorenzo]]

I agree with Pike. That's a dupe of bug 1431344. It will affect every 52.X.0 versions. 52.X.Y, Y being > 0 won't, because we fetch changesets from the .0 build. We can implement a workaround in ship-it, but I think the value is low and we can recover from the bug easily by copying and pasting the changesets of the previous build.

Moreover, like said in bug 1431344, we won't fetch the strings from elmo, once the taskcluster migration is done.

If you think we should address this bug, please reopen 1431344.

Comment 4

[Wayne Mery (:wsmwk)]

I had forgotten I filed this.  

Just noting for the record (and aki) that this is the reason it just happened today for building 52.7.0.