build failure emails are bothering me. I am ready to help fix it if we agree to give it some attention after each checkin.
If not can we at least disable the job? ~Rajani On Mon, Aug 25, 2014 at 2:54 PM, Rajani Karuturi <raj...@apache.org> wrote: > We are discussing on the CI infra and the tests/hardware required. It is a > much needed discussion. Its something which everybody agrees that we > require. > > Can we take a step back and look at out existing jenkins setup? > No CI system would help us if we dont look at it. > > We have [simulator-singlerun] job there which I believe runs after every > commit and executes all the simulator based tests. (I am not sure on this. > Can someone confirm?) > This job has been failing for the past 100+ builds with 1 consistent > failure and a few no ones here and there. > Can we give enough attention to this please and fix any failures > immediately? > > We also have a [hotfix-trigger] which is run on any branch with name > matching hotfix* > > Anybody aware of any such job which runs test cases/does sanity checking? > > [simulator-singlerun] > http://jenkins.buildacloud.org/job/simulator-singlerun/ > [hotfix-trigger] > http://jenkins.buildacloud.org/view/simulator/job/simulator-hotfix-trigger/ > > ~Rajani >
