Re: [v8-dev] Requesting try job access

On Thu, Jul 13, 2017 at 1:42 AM, Adam Klein wrote: > Hi Ben, > > Indeed this is a change in how Gerrit works compared to Rietveld, and my > understanding is that all contributors who wish to be able to land their own > changes need to request V8 tryjob access (CCing machenbach

Re: [v8-dev] Requesting try job access

No idea how widespread. This was an intentional decision made and explained here (sorry, Googlers only) resulting in requirement of at least tryjob access to operate CQ, even if CL has been approved. It wasn't meant for Gerrit

Re: [v8-dev] Requesting try job access

CC gerrit-switch experts. I'd like to understand what's the extend of this problem (e.g. how many people are affected and why) and if we can do anything to automatically make it work again in Gerrit as it used to in Rietveld. On Thursday, July 13, 2017 at 1:42:45 AM UTC+2, Adam Klein wrote: >

Re: [v8-dev] Requesting try job access

Hi Ben, Indeed this is a change in how Gerrit works compared to Rietveld, and my understanding is that all contributors who wish to be able to land their own changes need to request V8 tryjob access (CCing machenbach for confirmation on that). I've added you to the proper ACLs, so hitting CQ+2

[v8-dev] Requesting try job access

Hi, I'd like to request try job access so that I can land my CLs (again - used to work before the switch.) CLAs are on file for me personally (i...@bnoordhuis.nl) as well as from my employer, IBM. Should other Node.js contributors request access individually or can we get some blanket stamp of