Hi All, We are a community with limited resources. I think we should have precisely 1 CI solution. Multiple CI results confuse the casual contributor and we do not have the resources to manage multiple parallel systems (which I think is obvious). Of the things we have used Travis seems to be the simplest option for our github-centric community. That said having 1 is far more important than which one to me.
- I strongly +1 the move to one CI solution - Add to that a strong +1 for one build system (make <-> cmake), a closely related subject -Randy On Fri, Jun 10, 2016 at 12:05 AM, Jens Geyer <[email protected]> wrote: > > Morning, > > Will we lose the connection between the PRs and JIRA tickets as well? That > would be ... not so good. > > Next, what prevents us from having a working Jenkins again? If the build > env is so reproducable, why can't Jenkins reproduce it? I'm not really > involved in the CI stuff so please bear with me and my possibly dumb > questions. > > Have fun, > JensG > ________________________________ > Von: Aki Sukegawa > Gesendet: 10.06.2016 05:14 > An: [email protected] > Betreff: [DISCUSS] Disable Github -> Jenkins pull request hook > > Hi, > > Our Jenkins build has been dead for a while now. > The thing is that the job is only a subset of Travis-CI jobs. > So we can proceed just fine with Travis-CI and Appveyor without losing any > test case. > > To be clear, our Jenkins build has not been sufficient alone during recent > years. > On the other hand the Travis-CI build covers more cases and contains what > the Jenkins job currently does. > > If there's no concerns, I'll request Apache infra team for removal of our > Github-Jenkins integration, on their JIRA. > Thought ? >
