As most of you have seen, we have a bunch of intermittent test failures. This, added to the difficulties in rebuilding a pull-request and updating the status lead to a bit of a cumbersome process to get a PR merged.
I have created issues for the tests I've seen failing and marked them with label "component/test". The full list is at https://github.com/apache/incubator-pulsar/issues?q=is%3Aissue+is%3Aopen+label%3Acomponent%2Ftest Please anyone that has time to investigate these, take one, assign to yourself and try to reproduce. Fortunately, in new builds we now have individual INFO logs for each of the test, so that it might help in the debugging. -- Matteo Merli <mme...@apache.org> On Tue, Aug 1, 2017 at 9:40 AM, Matteo Merli <mme...@apache.org> wrote: > As we discussed some time back, I have added CI builds in Jenkins. > > Jenkins seems to be much more stable compare to Travis and it's bit more > flexible in terms of what we can do. For example, for C++ build we can use > custom Docker image with all the dependencies we require to build the > Pulsar client lib. > > I have asked INFRA to disable the mandatory check on Travis (to merge the > PRs) and instead use Jenkins for the same purpose. > > The build page links: > > https://builds.apache.org/job/pulsar-master/ > > https://builds.apache.org/job/pulsar-pull-request/ > > The only minor issue that I can see is that the "Rebuild" button the on > the PR builder is not updating back the status on the Github pull request. > The workaround is to "repush" the branch on github. If there are no > changes, you can do a "git commit --amend" and it will just update the > timestamp of the commit and force a new sha hash. Then push --force to > update the PR. > > If anyone knows or wants to take a look for a better solution.. :) > > > > > -- > Matteo Merli > <mme...@apache.org> >
