<div dir="ltr">Jeff, you're right, we should scare up a new PSC meeting to discuss. We're sitting on $2,500 that needs to be spent so covering a year to come up with a transition plan - if necessary - certainly seems reasonable. --Steve</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 2, 2020 at 12:23 PM Jeff McKenna <<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2020-11-02 2:05 p.m., Even Rouault wrote:<br>
> On lundi 2 novembre 2020 11:21:29 CET Jeff McKenna wrote:<br>
>> Hi devs,<br>
>><br>
>> It's important to point out that as of today Travis CI has changed its<br>
>> pricing model, so that Open Source projects get a free block of 1000<br>
>> minutes of build time (only about 16 hours), and will have to re-apply<br>
>> to get further blocks of time. Related blog:<br>
>> <a href="https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing" rel="noreferrer" target="_blank">https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing</a><br>
>><br>
>> To give you an example, I bet I used about 10 hours of build time on<br>
>> MapServer last week myself, yikes.<br>
>><br>
>> This change also means a move from <a href="http://travis-ci.org" rel="noreferrer" target="_blank">travis-ci.org</a> to <a href="http://travis-ci.com" rel="noreferrer" target="_blank">travis-ci.com</a> for<br>
>> this, for example:<br>
>><br>
>> - see our list of repositories at <a href="https://travis-ci.org/github/MapServer" rel="noreferrer" target="_blank">https://travis-ci.org/github/MapServer</a><br>
>> - see how none of our repositories are setup yet at<br>
>> <a href="https://travis-ci.com/github/MapServer" rel="noreferrer" target="_blank">https://travis-ci.com/github/MapServer</a><br>
>><br>
>> I have started the process and now have 1000 minutes for my own account<br>
>> on .com but am looking at how to set this up for MapServer and all of<br>
>> our repositories.<br>
>><br>
>> The knee-jerk reaction to this will be "we need to move to Github<br>
>> Actions/workflows for builds right away", but I think we should examine<br>
>> and discuss all options together before any quick decisions are made for<br>
>> the MapServer 'organization' (Github's term referring to all of<br>
>> MapServer's repositories).<br>
>><br>
> <br>
> A theorical alternative would be to see if Travis-CI would accept the<br>
> MapServer organization to share the paid premium plan of the OSGeo<br>
> organization, that is mostly used by GDAL, PROJ and GRASS. But I'm not<br>
> confident they would be willing. And I'm not sure either of the future of the<br>
> current OSGeo premium plan. I wrote to Travis support to see what their<br>
> billing changes would impact and their answer is far from being crystal<br>
> clear... It seems we'd have to choose between concurrency plans or usage based<br>
> plans as defined in <a href="https://travis-ci.com/account/plan" rel="noreferrer" target="_blank">https://travis-ci.com/account/plan</a> , but their maximum<br>
> concurrency plans is 5 instead of the 10 we have currently for OSGeo (and<br>
> originally we had 13 when we started on the paid plan). And the usage based<br>
> plan doesn't seem appropriate for open source projects and pull requests<br>
> mechaism as it implies to limit/control the number of users who submit builds<br>
> <br>
<br>
Yes, and it could make sense to actually use our MapServer budget to <br>
purchase one of the monthly plans for Travis CI builds (if you want my <br>
opinion this could be very worth it, as I'm all for paying for something <br>
to keep our architecture stable, instead of jumping to the next <br>
free-turning-proprietary-turning-paid service).<br>
<br>
For example: even the lowest/fewest concurrent job plans on <br>
<a href="http://travis-ci.com" rel="noreferrer" target="_blank">travis-ci.com</a> looks like a great option for the MapServer organization:<br>
<br>
- 1 concurrent job = $69/month = $828 yearly<br>
- 5 concurrent jobs = $249/month = $2,988 yearly<br>
<br>
I think spending the $828 out of the MapServer budget each year to have <br>
a dedicated (and stable) build environment just for the MapServer <br>
organization is a good plan. Only 1 concurrent job means that <br>
technically we can have some developers waiting sometimes, but as most <br>
times it is me doing the build, and recently the OSS/free Travis CI plan <br>
now takes ~1 hour to wait for our free build turn before the virtual <br>
machine spins-up, I think the dedicated instance would be a big <br>
improvement and even *less* wait times than the current free/OSS plan.<br>
<br>
-jeff<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a></blockquote></div>