pgRouting/docker-pgrouting

Setup Github Actions

dkastl opened this issue · 7 comments

dkastl commented

@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

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

aruneko commented

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.

  • 2.x.x (latest)
    • the tag provides stable version built from tagged master branch.
  • 3.0.0-alpha
    • the tag provides unstable version built from tagged master branch.
  • dev
    • the tag provides latest develop version built from head of develop branch
dkastl commented

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

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

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

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

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.