[Board] Travis-CI & OSGeo

[María Arias de Reyna]

Hi,

In my experience, I like Jenkins more than Travis and I think that
with an owned Jenkins we will be able to do much more than with the
Travis service, but I understand that I may be missing something
important here. So it is up to each project to comment if Jenkins
would be a nice solution or not.

At least for GeoNetwork, it's true that we have Travis linked to our
github (not inside OSGeo organization but on our own), but, at the
same time, what we really use is a Jenkins we have on our own
infrastructure. Every time I try to use Travis, it is unstable and
weird. We can't trust the testing results, for example. But that may
be me, or Java, or GeoNetwork, or who knows, that makes Travis
unfriendly with our project.

So, going back to the beginning of the thread: Even, will a Jenkins be enough?


On Tue, May 1, 2018 at 2:59 PM, Regina Obe <lr at pcorp.us> wrote:
>
>> Hi,
>
>> afaik, Jenkins can be configured, that it uses several "cores" - so one Jenkins instance can take advantage of more servers, so  it scales up pretty well.
>
>> Actually, in my previous work, we used jenkins quite extensively, developers and even power users were able to setup their own jobs,
>> which were taking fresh code from custom git repo ... it was more or less about writing the shell script, which did all the work
>
>> so, if there would be jenkins instance available in osgeo infrastructure, I would prefer it over travis (which pywps is using now)
>
>
> Yes Jenkins can scale fairly well especially when we throw slaves into the mix.
> I was more thinking about the logistics of delegating administrative rights and configuring slaves in a fashion that power users can configure their own and know what's available on each slave for their tests, cleanup of workspace etc.
> And also the interoperability of the projects.
>
> The main reason I like Jenkins is for PostGIS work we need to follow PostgreSQL developments which means we need to test against the head of not yet released PostgreSQL which is something not easy to do with travis.
>
> We also need to test against the head of GEOS and GDAL so one of the Jenkins bots we have uses the build output from PostgreSQL, GEOS, GDAL Jenkins jobs and does a matrix job (testing 5 versions of PostgreSQL including dev head) , GEOS head, GDAL head.
>
> There is a lot of potential for synergy, but also a bit of "If I need to test GDAL for PostGIS purposes and GDAL needs to test GDAL, but I don't necessarily need to run all the tests GDAL needs to run, where is the balance of power there".  So that's my reasoning for why a single Jenkins might not be sufficient.  It's doable but takes a bit of planning.
>
> As far as authentication we can use OSGeo LDAP and designate administrators from each project.  I think having 10 administrators that have full control of the instance from various projects that we all feel comfortable about working together is a workable solution.
>
>
> Thanks,
> Regina
>
>
>
>
>