Here's a thought from the peanuts gallery :-) Nothing prevents you from setting up a separate Jenkins instance maintained by Adobe and making the results public. This would not be vastly different from the ASF Jenkins instance, I guess that you would not be in a 'trusted' ASF network anymore and the administrator are different, but that's about it.
Robert On Thu, 2016-11-17 at 14:22 +0100, Michael Dürig wrote: > I agree in general. And we could as well also keep our current > Jenkins > instance. It is just that it doesn't provide much value unless we > spent > a lot of time on it, which didn't happen in the (extended) past. > > Michael > > On 17.11.16 2:15 , Tommaso Teofili wrote: > > sorry but I disagree, while Adobe can have its internal > > infrastructure run > > whatever kind of tests, I think Oak should have its own continuous > > build > > working on the ASF infra, if anything needs to be adjusted we can > > get in > > touch with infra@. > > Other than that I am sorry I could not spend more time on CI setup > > (and Oak > > in general) lately. > > > > Regards, > > Tommaso > > > > Il giorno gio 17 nov 2016 alle ore 13:35 Michael Dürig <mduerig@apa > > che.org> > > ha scritto: > > > > > > > > > > > On 17.11.16 12:31 , Bertrand Delacretaz wrote: > > > > On Thu, Nov 17, 2016 at 9:27 AM, Michael Dürig <mduerig@apache. > > > > org> > > > > > > wrote: > > > > > ...I was mostly thinking of using some internal resources as > > > > > so far the > > > > > > public > > > > > options didn't work out for us... > > > > > > > > Internal to what? > > > > > > To Adobe > > > > > > Michael > > > > > > > > -Bertrand > > > >
