Re: Reproducible builds

Regarding timestamps in tarballs, using tar's --mtime option to force timestamps to MOZ_BUILD_DATE (or a derivative thereof) could work. On 19 July 2016 at 04:11, Kurt Roeckx wrote: > On 2016-07-18 20:56, Gregory Szorc wrote: > >> >> Then of course there is build signing, which

Re: Adding new jobs to pushes is not currently working

The Pulse infra issue has been resolved and we're now back to business. On 2016-07-18 10:38 AM, Armen Zambrano G. wrote: Hello, Treeherder sends a Pulse messages to add new jobs to your pushes. Those messages are currently not arriving, thus, the system won't work. If you want to know when it

Usability improvements for Firefox automation initiative - Status update #1

The developer survey conducted by Engineering Productivity last fall indicated that debugging test failures that are reported by automation is a significant frustration for many developers. In fact, it was the biggest deficit identified by the survey. As a result, the Engineering Productivity

Re: Reproducible builds

On 2016-07-18 20:56, Gregory Szorc wrote: Then of course there is build signing, which takes a private key and cryptographically signs builds/installers. With these in play, there is no way for anybody not Mozilla to do a bit-for-bit reproduction of most (all?) of the Firefox distributions at

Re: Reproducible builds

On 2016-07-19 00:49, Mike Hommey wrote: On Sun, Jul 17, 2016 at 09:38:31AM -0700, David Bruant wrote: Out of curiosity, how has is the TOR team handled points 1 and 2? I cannot answer for TOR, but I can answer for Debian, who also does reproducible builds of Firefox. 1) is not addressed at

Re: [Sheriffs] Current state of the tree closures

Hi, thanks Wes! taking over now and cleaning up the trees the sheriffed repos and will do backouts as needed. - Tomcat On Tue, Jul 19, 2016 at 4:05 AM, Wes Kocher wrote: > The Treeherder devs have deployed a hotfix that appears to have fixed up > the responsiveness