Polis: Set up docker build server

[patcon]

Re-ticketed from https://github.com/pol-is/polis-issues/issues/139#issuecomment-622499996

ballPointPenguin: Github actions, or the others, would be a good path to explore for what I'm calling "build server". I think. I haven't tried GitHub actions yet but I'm hopeful.

A build server will not only make running polis easier in the future, but will also immediately act as a QA measure to ensure that the docker images correctly build from scratch.

cc @ballPointPenguin @joshsmith2

Summary

prior suggestions: travis, circleci, github actions. patcon suggested not confining ourselves to any one platform at first. metasoarous, ben, patcon all ok with either circleCI or GitHub Actions.

To Dos

• [x] Set up first-pass nightly docker builds in Github Actions -- @patcon https://github.com/pol-is/polisServer/pull/282
• [x] create docker hub org: https://hub.docker.com/u/polisdemo
• [x] create poliosdemobot docker hub user
  
  
  
  • [x] add credentials to password gdoc
  
  
• [x] add metasoarous to the docker hub org as owner
• [ ] ...

[patcon]

Gitter context

patcon:

anyone have a sense of whether auto-publishing docker images from this repo via github actions would support quality assurance in this project? re: https://github.com/marketplace/actions/build-tag-publish-docker

@crkrenn:

As for CI, have you or others used Travis CI? It is free for open source.
https://levelup.gitconnected.com/devops-essentials-continuous-integration-and-deployments-of-docker-applications-with-aws-373f60daf320

patcon:

thanks! i used to use travis a ton, then moved to circleCI as it has more versatile use of scheduled eecutions and chainable workflows, and now I'm using GitHub Actions for the extensibility and the fact that each run gets a GitHub key for interacting with GitHub API itself, which is nice

metasoarous:

I have a preference for circleCI, FWIW

patcon:

ah gotcha, thanx :) are you sharing that as a decision you'd like to make, or a contribution to ongoing discussion. (either is fine, just want to make sure i understand)

metasoarous:

It seems like it integrates pretty well with GitHub actions, which is a major plus, and I'm familiar with the folks who worked on it. If there's a strong case for another tool I'm open for hearing it, otherwise let's call it decided.

[patcon]

As prior art, this is how mailcow works/builds:

• https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml
• https://github.com/mailcow/mailcow-dockerized/blob/master/.drone.yml
• https://github.com/mailcow/mailcow-integration-tests
• https://github.com/mailcow/mailcow-dockerized/tree/master/data/Dockerfiles

(mailcow is a very highly used project with official install via docker)

[patcon]

Forgot to share this, but I created a temp org for messing around until we have the real one:
https://hub.docker.com/orgs/polisdemo

Speak up if interested, and I'll add you!

Wanna be assigned on this issue, @ballPointPenguin?

[patcon]

Docker hub users and orgs share namespace, and "polis" is taken:
https://hub.docker.com/orgs/polis

We can reclaim it:
https://success.docker.com/article/how-do-i-claim-an-inactive-docker-id

1. (3) Username Squatting. You may not and may not allow any third party to engage in username squatting. Accounts that are inactive for more than six months may be terminated at our discretion and without further notice. We take into account several factors when determining what conduct is considered to be username squatting including, without limitation:
   
   
   
   1. The number of accounts created
   
   
   2. Creating accounts for the purpose of preventing others from using those account names
   
   
   3. Creating accounts for the purpose of selling those accounts
   
   

I'll submit a support request to see if we can claim it.

[patcon]

Made a general ask in a non-specific way:
https://twitter.com/patconnolly/status/1258855193413910529

(though not the best word, "nonprofit" seems to capture the spirit of what polis is better than "startup" rn)

EDIT: Sent followup email via https://hub.docker.com/support/contact/

[ballPointPenguin]

Awesome. Thanks for doing that. Feel free to assign me the issue as well.

[patcon]

Summary of gitter convos:

• Ben is manually pushing container builds to polisdemo docker hub org
• @colinmegill offered edge.pol.is for per-commit or nightly builds (@metasoarous can support)
  
  
  
  • @ballPointPenguin offered polisdemo.tech domain to be used for same (or some other purpose
  
  
• colin suggested nightly builds to edge.pol.is
• colin suggested tagged releases on pol.is
• patcon suggested tagged releases be an automated process that happens every x weeks off mainline like clockwork, so long as there's _something_ new to add (+1 ballpointpenguin)
• on call, we decided we're good with GitHub Actions or CircleCI

[patcon]

@ballPointPenguin is it ok if I experiment with docker hub pushes via github action?

• https://help.github.com/en/actions/language-and-framework-guides/publishing-docker-images#publishing-images-to-docker-hub-and-github-packages
• https://github.com/docker/build-push-action

[ballPointPenguin]

@patcon please do

[patcon]

Messing around here: https://github.com/pol-is/polisServer/compare/dev...patcon:patcon/67-build-server-actions https://github.com/patcon/polisServer/actions

EDIT: PR created https://github.com/pol-is/polisServer/pull/282

in chat, colin +1 with using polisdemo.tech for now, but asked for adequate disclaimers so ppl know it's community infra and doesn't come with strong guarantees.

Also, after exploration, we'll put effort into migrating the things we learn work, into polis infra like edge.pol.is (so polisdemo.tech won't default to becoming the de facto official place)

[patcon]

I think we're good to close this now, since we've got GitHub Actions workflows running nightly..? Def speak up if we should re-open :)