Ya, we will see if people actually do kick off new jenkins runs. I will follow up with a few people to ask them to as I know their PRs are running into some of the problems we have discussed.
*Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Thu, May 19, 2016 at 11:45 AM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > Maybe I should have formulated my request A little less open minded :) Hope > it did help. As I choose one of two possible solutions let me know if I > should try the other one. > > On Thu, May 19, 2016 at 5:25 PM, Will Stevens <wstev...@cloudops.com> > wrote: > > > Haha. Too bad you can't batch this email to a smaller groups. Daan just > > crashed the Jenkins... :P > > > > Seriously, thank you for your help on this. I think this will make a big > > difference going forward. > > > > *Will STEVENS* > > Lead Developer > > > > *CloudOps* *| *Cloud Solutions Experts > > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > > w cloudops.com *|* tw @CloudOps_ > > > > On Thu, May 19, 2016 at 7:46 AM, Daan Hoogland <daan.hoogl...@gmail.com> > > wrote: > > > > > People, > > > > > > I've asked several people to reopen their pr because of jenkins > > > configuration problems. I think i found the little checkbox that needed > > > setting now. Please do not hurry but reopen any failed PRs on jenkins > > > problems, if you fell it wasn't in your code. don't do it all at once > as > > > builds.a.o is kind of heavily loaded. > > > > > > -- > > > Daan > > > > > > > > > -- > Daan >
