[Board] Travis-CI & OSGeo

[María Arias de Reyna]

Hi,

I see this conversation is stalled so, let me summarize it a bit to see how
to approach it:

 * There is a need for more CI (Travis) threads on the OSGeo organization
of Github
 * Some of us are not keen to give money to private infrastructure if there
is an open source solution (Gitlab CI, Jenkins) and prefer to support open
source even outside OSGeo
 * Moving from Github to Gitlab will be a drawback to the projects (part of
the community will be left behind and lost). So, not an option ¿¿for short
term??.
 * We could add a Jenkins from OSGeo that atke care of what Travis is doing
right now. Advantage: we will have no restrictions. Disadvantage:
¿¿Integration on github??

Did I miss something here?

So, our best options look like:
 * Having the Jenkins that replaces Travis
 * Pay Travis more

And to decide we need to know:
 * Is having a Jenkins really an option here? Or something will be missing?
 * Will it be cheaper?

Who can answer this two questions?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20180501/907e733e/attachment.htm>