[GRASS-user] Example project on GitLab

[Vaclav Petras]

On Wed, Nov 7, 2018 at 8:47 AM Bernardo Santos <
bernardo_brandaum at yahoo.com.br> wrote:

>
> thanks for that, it'll be very useful. I think a similar approach can be
> used to build repositories for addons within GitHub, right?
>

Yes, when you involve Travis CI.


> Do you see clear advantages of using GitLab instead of GitHub for this
> purposes?
>

One other reason besides the private repos mentioned by KenM, the CI is
much better integrated then GitHub and Travis CI, so for example, you don't
have to pass any tokens to connect them bidirectionally in order to publish
web pages build by CI. The built web pages on GitLab don't need to be part
of the repository which may have some drawbacks but it is mostly an
advantage I would say. This is all kind of related to the GitLab approach
to the project - it is a primary a project and Git repo is just part of it
(GitHub interface is built around a repo).

Another thing is that you can download all the data and upload it to your
own GitLab instance if you don't want to use gitlab.com anymore (at least
that's what they claim). This relates to the fact that (most of) GitLab
itself is actually open source (!).

I'm not sure if it is an advantage for real work, but I personally enjoyed
working with the GitLab WebIDE and I created the whole example just using
that although at this point is misses spell check and you need to commit in
order to run the code.

One disadvantage of GitLab is that the CI is Linux only while GitHub has
macOS and recently they added Windows too.

Best,
Vaclav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20181107/35f22121/attachment-0001.html>