fair points Rajani, not related to my question but worthy of attention. In the meanwhile I am taking them as a "yes we can schedule regular (master) build down to once a day"
On Thu, Aug 20, 2015 at 8:02 AM, Rajani Karuturi <raj...@apache.org> wrote: > pull-rat doest the rat check > pull-analysis does a roredist build and unittests after applying the pr. > I dont know what pull-request does. So, I am ok with disabling it :) > > The problem I see with these jobs is that, it only informs me of a success > or a failure once its done. There is no inprogress indication like travis. > sometimes the response is so slow that I get a build failure a few hours > after the PR merge. ( there is also the aborted noise when the pr is > getting appended with review comments) > > If we can solve that, it will also help reviewers in deciding to wait for > those additional checks to complete before doing a merge. > > ~Rajani > > On Wed, Aug 19, 2015 at 4:15 PM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > > > LS, > > > > I have disabled cloudstack-pull-request on builds.apache.org as we now > > have > > cloudstack-pull-rat and cloudstack-pull-analysis and also still have > > jenkins.bac.o. I want to further unburdon the apache jenkins web by > > scheduling down other jobs to once a day. noticably this is the master > > build but also the rat-catcher. If we do so review on PRs for these > issues > > become more important hence looking at the output of pull request jobs. > Can > > we live with that? > > > > regards, > > -- > > Daan > > > -- Daan
