Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-02 Thread Brian Gerstle
Right, but GitLab apparently has its own CI offering, so we wouldn't need to wait for Travis to integrate. On Friday, October 2, 2015, C. Scott Ananian wrote: > Travis is not integrated with gitlab, so it's not really relevant here. > *If* travis adds gitlab integration *and* we switch our curr

Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-02 Thread C. Scott Ananian
Travis is not integrated with gitlab, so it's not really relevant here. *If* travis adds gitlab integration *and* we switch our current github mirror to gitlab *then* it could be something to look at. Neither of those preconditions are currently met. We're not using any "new" github features, ju

Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-02 Thread Brian Gerstle
Ah of course, my misunderstanding. (I even mentioned pushing to git in my last email). > If we wanted to keep build > artifacts around "forever", we could easily do so; How would you get artifacts of a build done inside a Travis VM? In any case, this still involves going through GitHub. Is an

Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-02 Thread C. Scott Ananian
On Fri, Oct 2, 2015 at 11:50 AM, Brian Gerstle wrote: > Lastly, it appears that Travis's build-triggering API is still in beta > , and there's no mention > of polling builds in this way. I don't use this API, and it's not really suitable in any

Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-02 Thread Brian Gerstle
Also, sorry if this all should've gone in Phab and not email. I can transcribe to Phab if we'd rather continue discussion there. On Fri, Oct 2, 2015 at 11:50 AM, Brian Gerstle wrote: > * iOS Mobile app >> < >> https://lists.wikimedia.org/pipermail/wikitech-l/2015-September/083005.html >> > > > >

Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-02 Thread Brian Gerstle
> > * iOS Mobile app > < > https://lists.wikimedia.org/pipermail/wikitech-l/2015-September/083005.html > > I saw npm-travis when you announced it a while back and was intrigued. The master branch on the wikipedia-ios repo is already building successfully on Travis, so feel free to try triggering

Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-02 Thread Gabriel Wicke
On Fri, Oct 2, 2015 at 6:15 AM, Marko Obrovac wrote: > > > While hosted officially on Gerrit, Citoid should be added to this list as > well. Its proper functioning depends on Zotero being available, so the > current CI tests for Citoid include only syntax checking via jshint. In > this case, howev

Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-02 Thread Marko Obrovac
On 1 October 2015 at 22:43, C. Scott Ananian wrote: > We currently have several projects which can not be tested with our current > Jenkins test infrastructure, and as a consequence are hosting their primary > code repositories on github: > * RESTBase -- mi

Re: [Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-01 Thread Greg Grossmeier
> * iOS Mobile app > > -- > missing OS X platform If you want the gory details about the iOS decision, see: https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Retrospectives/Retrospective-iOS-Github-2015-08-03 Summary:

[Wikitech-l] RFC: Optional Travis integration for Jenkins

2015-10-01 Thread C. Scott Ananian
We currently have several projects which can not be tested with our current Jenkins test infrastructure, and as a consequence are hosting their primary code repositories on github: * RESTBase -- missing Cassandra support * iOS Mobile app