On Sun, Apr 28, 2019 at 1:10 PM Matteo Merli <matteo.me...@gmail.com> wrote:
> Ups, that was me. I had it changed to do update on the site for 2.3.1 > release (amidts the CI errors for master) and forgot to switch it back :/ > Did that now. > Thank you. > > > Regardless, we used to use Jenkins DSL for managing Jenkins jobs to > ensure all the jenkins jobs are under review ( > https://github.com/apache/pulsar/tree/master/.test-infra/jenkins). It > seems > that was disabled. Should we re-enable it? > > Yes, we should re-enable. I think we started doing manual changes (eg: on > the lists of worker nodes) when there were instabilities on Jenkins nodes > and that kind of diverged from there. We should sync the jobs config with > what it's on Jenkins now. > > -- > Matteo Merli > <matteo.me...@gmail.com> > > > On Sat, Apr 27, 2019 at 9:44 PM Sijie Guo <guosi...@gmail.com> wrote: > > > Any updates on this? > > > > If no one has objections, I will change the branch back to master. So the > > pulsar website can be built. > > > > - Sijie > > > > On Fri, Apr 26, 2019 at 5:48 PM Sijie Guo <si...@apache.org> wrote: > > > >> Hi all, > >> > >> It seems that pulsar-website-build has stopped since 4/13. I found that > >> the branch was changed to `site-update`. Did anyone change this > recently? > >> This should be configured to `master`, otherwise the job will not get > any > >> updates from github hence the job will stop running. > >> > >> Regardless, we used to use Jenkins DSL for managing Jenkins jobs to > >> ensure all the jenkins jobs are under review ( > >> https://github.com/apache/pulsar/tree/master/.test-infra/jenkins). It > >> seems that was disabled. Should we re-enable it? > >> > >> - Sijie > >> > >> > >> [image: Screen Shot 2019-04-26 at 5.42.53 PM.png] > >> > > >
