pgRouting / docker-pgrouting

Docker for pgRouting
https://hub.docker.com/repository/docker/pgrouting/pgrouting
GNU General Public License v2.0
64 stars 34 forks source link

Setup Github Actions #15

Closed dkastl closed 4 years ago

dkastl commented 4 years ago

@aruneko pgRouting was granted permissions to use Github Actions, so we could now setup CI to build Docker images. https://help.github.com/en/articles/about-github-actions

cayetanobv commented 4 years ago

Yes, Github actions are very interesting. BTW: I'm going to merge PR from dev to master.

aruneko commented 4 years ago

I think to build a docker image automatically, we have to place a CI setting file in pgrouting/pgrouting repository. Github Actions does not support hook from Github webhook. So we cannot run building process from other repository with webhook.

In my opinion, it is better to build 3 tagged docker images.

dkastl commented 4 years ago

True, it needs to be where the source code of pgRouting is. I read that all operating systems (Windows, OSX and Linux) are supported, so we could eventually replace AppVeyor and Travis altogether.

cvvergara commented 4 years ago

alpha is here: https://github.com/pgRouting/pgrouting/releases/tag/v3.0.0-alpha

master what in the near future is going to be beta

cayetanobv commented 4 years ago

Remember we have connected our DockerHub account to Github. Yesterdays PR merge (Dev to Master) built all images. You can see here all tags: https://hub.docker.com/r/pgrouting/pgrouting/tags

dkastl commented 4 years ago

So merging into master in the pgRouting repository builds all Docker images, but merging into develop does not build the dev Docker image?

dkastl commented 4 years ago

Since Github Actions is indeed more something we need on pgRouting's main repository, I'm closing this issue as the remaining question is also handled in #15.