[GRASS-dev] [GRASS-user] Motion: Migrate SVN and trac tickets to github under OSGeo organization

GRASS GIS GRASS GIS developer
,
1

in case you’re not aware of it, it turns out that a number of continuous
integration services, like Travis-CI or AppVeyor, have concurrency limits for
the jobs at the GitHub organization level (ie if using OSGeo/, for all
repositories under OSGeo/ ). For Travis-CI, OSGeo pays Travis-CI for ~ 11
concurrent jobs. Primary users are currently GDAL and proj.4. For AppVeyor, we
use the free plan, which is limited to 1 concurrent job, and is sometimes the
reason for pull requests to take a significant time to be completed.

For the record, azure pipelines offers 10 concurrent jobs for Open Source projects + support for multiple operating systems.
https://azure.microsoft.com/en-us/services/devops/pipelines/

with kind regards,
Panos

2

On Mon, Apr 22, 2019 at 6:46 PM Panagiotis Mavrogiorgos
<pmav99@gmail.com> wrote:

in case you're not aware of it, it turns out that a number of continuous
integration services, like Travis-CI or AppVeyor, have concurrency limits for
the jobs at the GitHub organization level (ie if using OSGeo/, for all
repositories under OSGeo/ ). For Travis-CI, OSGeo pays Travis-CI for ~ 11
concurrent jobs. Primary users are currently GDAL and proj.4. For AppVeyor, we
use the free plan, which is limited to 1 concurrent job, and is sometimes the
reason for pull requests to take a significant time to be completed.

For the record, azure pipelines offers 10 concurrent jobs for Open Source projects + support for multiple operating systems.
https://azure.microsoft.com/en-us/services/devops/pipelines/

Thanks for the hint, added under
https://trac.osgeo.org/grass/wiki/GitMigration#CICDandQA

Best
Markus

3

Hi,

at time we don't have recent Windows builds.

In another email to the list Panos suggested:

On Mon, Apr 22, 2019 at 6:46 PM Panagiotis Mavrogiorgos
<pmav99@gmail.com> wrote:

For the record, azure pipelines offers 10 concurrent jobs for Open Source projects + support for multiple operating systems.
https://azure.microsoft.com/en-us/services/devops/pipelines/

Re: Appveyor there are these pipelines for inspiration:

build recipes in
- https://github.com/OSGeo/proj.4/blob/master/appveyor.yml
- https://github.com/OSGeo/gdal/blob/master/appveyor.yml
- ...

Is anyone willing to look into this?
Perhaps a way to get winGRASS up & running more easily and soon?

thanks
Markus

PS: I am happy to support in creating the needed accounts (they should
belong to the GRASS GIS project I suppose).

4

Hi,

čt 6. 6. 2019 v 22:48 odesílatel Markus Neteler <neteler@osgeo.org> napsal:

at time we don't have recent Windows builds.

I hope to have some time to put them in operation again in next days.

Re: Appveyor there are these pipelines for inspiration:

build recipes in
- https://github.com/OSGeo/proj.4/blob/master/appveyor.yml
- https://github.com/OSGeo/gdal/blob/master/appveyor.yml
- ...

Is anyone willing to look into this?

I don't know, but what could be tricky, to set up msys2 / mingw64
environment. Just reminder that GRASS is not possible to compile using
MSVS nowadays.

Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa