Dear users and devs,
I’ve created an example project at GitLab. It is a GRASS GIS module written in Python. It uses GitLab CI to build the module and publish its documentation as a website.
https://gitlab.com/vpetras/r.example.plus
If you are familiar with GitHub, GitLab will feel familiar as well (we can discuss the differences later), but the following terminology comparison may come useful:
https://about.gitlab.com/2017/09/11/comparing-confusing-terms-in-github-bitbucket-and-gitlab/
Otherwise, I hope the project should describe itself and if something is missing or is not documented enough, your can submit an issue or a merge request.
Best,
Vaclav
PS: We can create a GitLab group for GRASS GIS and move this project there.
On Mon, Nov 5, 2018 at 2:43 PM Ken Mankoff <mankoff@gmail.com> wrote:
I think I will find it useful in helping some of my custom scripts to official plugins.
Glad to hear that! Thanks for sharing your code!
On Fri, Nov 2, 2018 at 7:08 PM Vaclav Petras <wenzeslaus@gmail.com> wrote:
Dear users and devs,
I’ve created an example project at GitLab. It is a GRASS GIS module written in Python. It uses GitLab CI to build the module and publish its documentation as a website.
https://gitlab.com/vpetras/r.example.plus
If you are familiar with GitHub, GitLab will feel familiar as well (we can discuss the differences later), but the following terminology comparison may come useful:
https://about.gitlab.com/2017/09/11/comparing-confusing-terms-in-github-bitbucket-and-gitlab/
Otherwise, I hope the project should describe itself and if something is missing or is not documented enough, your can submit an issue or a merge request.
Best,
Vaclav
PS: We can create a GitLab group for GRASS GIS and move this project there.
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
On Wed, Nov 7, 2018 at 8:47 AM Bernardo Santos <bernardo_brandaum@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
Hi Vaclav,
Thanks for sharing this simple demo. I think I will find it useful in helping some of my custom scripts to official plugins.
Cheers,
-k.
On Fri, Nov 2, 2018 at 7:08 PM Vaclav Petras <wenzeslaus@gmail.com> wrote:
Dear users and devs,
I’ve created an example project at GitLab. It is a GRASS GIS module written in Python. It uses GitLab CI to build the module and publish its documentation as a website.
https://gitlab.com/vpetras/r.example.plus
If you are familiar with GitHub, GitLab will feel familiar as well (we can discuss the differences later), but the following terminology comparison may come useful:
https://about.gitlab.com/2017/09/11/comparing-confusing-terms-in-github-bitbucket-and-gitlab/
Otherwise, I hope the project should describe itself and if something is missing or is not documented enough, your can submit an issue or a merge request.
Best,
Vaclav
PS: We can create a GitLab group for GRASS GIS and move this project there.
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Hi Vaclav,
thanks for that, it’ll be very useful. I think a similar approach can be used to build repositories for addons within GitHub, right?
Do you see clear advantages of using GitLab instead of GitHub for this purposes?
Best,
Bernardo Niebuhr
Em segunda-feira, 5 de novembro de 2018 17:50:38 BRST, Vaclav Petras wenzeslaus@gmail.com escreveu:
On Mon, Nov 5, 2018 at 2:43 PM Ken Mankoff <mankoff@gmail.com> wrote:
I think I will find it useful in helping some of my custom scripts to official plugins.
Glad to hear that! Thanks for sharing your code!
On Fri, Nov 2, 2018 at 7:08 PM Vaclav Petras <wenzeslaus@gmail.com> wrote:
Dear users and devs,
I’ve created an example project at GitLab. It is a GRASS GIS module written in Python. It uses GitLab CI to build the module and publish its documentation as a website.
https://gitlab.com/vpetras/r.example.plus
If you are familiar with GitHub, GitLab will feel familiar as well (we can discuss the differences later), but the following terminology comparison may come useful:
https://about.gitlab.com/2017/09/11/comparing-confusing-terms-in-github-bitbucket-and-gitlab/
Otherwise, I hope the project should describe itself and if something is missing or is not documented enough, your can submit an issue or a merge request.
Best,
Vaclav
PS: We can create a GitLab group for GRASS GIS and move this project there.
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Gitlab supports private repositories. Useful for early development for some people.
Please excuse brevity. Sent from tiny pocket computer with non-haptic feedback keyboard.
On Wed, Nov 7, 2018, 05:47 Bernardo Santos <bernardo_brandaum@yahoo.com.br wrote:
Hi Vaclav,
thanks for that, it’ll be very useful. I think a similar approach can be used to build repositories for addons within GitHub, right?
Do you see clear advantages of using GitLab instead of GitHub for this purposes?
Best,
Bernardo Niebuhr
Em segunda-feira, 5 de novembro de 2018 17:50:38 BRST, Vaclav Petras <wenzeslaus@gmail.com> escreveu:
On Mon, Nov 5, 2018 at 2:43 PM Ken Mankoff <mankoff@gmail.com> wrote:
I think I will find it useful in helping some of my custom scripts to official plugins.
Glad to hear that! Thanks for sharing your code!
On Fri, Nov 2, 2018 at 7:08 PM Vaclav Petras <wenzeslaus@gmail.com> wrote:
Dear users and devs,
I’ve created an example project at GitLab. It is a GRASS GIS module written in Python. It uses GitLab CI to build the module and publish its documentation as a website.
https://gitlab.com/vpetras/r.example.plus
If you are familiar with GitHub, GitLab will feel familiar as well (we can discuss the differences later), but the following terminology comparison may come useful:
https://about.gitlab.com/2017/09/11/comparing-confusing-terms-in-github-bitbucket-and-gitlab/
Otherwise, I hope the project should describe itself and if something is missing or is not documented enough, your can submit an issue or a merge request.
Best,
Vaclav
PS: We can create a GitLab group for GRASS GIS and move this project there.
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Gitlab supports private repositories. Useful for early development for some people
Please excuse brevity. Sent from tiny pocket computer with non-haptic feedback keyboard.
On Wed, Nov 7, 2018, 05:47 Bernardo Santos <bernardo_brandaum@yahoo.com.br wrote:
Hi Vaclav,
thanks for that, it’ll be very useful. I think a similar approach can be used to build repositories for addons within GitHub, right?
Do you see clear advantages of using GitLab instead of GitHub for this purposes?
Best,
Bernardo Niebuhr
Em segunda-feira, 5 de novembro de 2018 17:50:38 BRST, Vaclav Petras <wenzeslaus@gmail.com> escreveu:
On Mon, Nov 5, 2018 at 2:43 PM Ken Mankoff <mankoff@gmail.com> wrote:
I think I will find it useful in helping some of my custom scripts to official plugins.
Glad to hear that! Thanks for sharing your code!
On Fri, Nov 2, 2018 at 7:08 PM Vaclav Petras <wenzeslaus@gmail.com> wrote:
Dear users and devs,
I’ve created an example project at GitLab. It is a GRASS GIS module written in Python. It uses GitLab CI to build the module and publish its documentation as a website.
https://gitlab.com/vpetras/r.example.plus
If you are familiar with GitHub, GitLab will feel familiar as well (we can discuss the differences later), but the following terminology comparison may come useful:
https://about.gitlab.com/2017/09/11/comparing-confusing-terms-in-github-bitbucket-and-gitlab/
Otherwise, I hope the project should describe itself and if something is missing or is not documented enough, your can submit an issue or a merge request.
Best,
Vaclav
PS: We can create a GitLab group for GRASS GIS and move this project there.
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user