1431276 - Build elmo/a10n Docker containers in CI

Status: RESOLVED FIXED

(Localization Infrastructure and Tools :: Automation, enhancement)

Description

[Miles Crabill [:miles]]

The standard Dockerflow [0] spec is to build production containers in CI. Cloudops uses CircleCI to build and push these containers to Dockerhub.

Once we have the repositories and Dockerfiles in place, we can work on the container build flow.

[0] https://github.com/mozilla-services/dockerflow

Comment 1

[Axel Hecht [:Pike]]

https://circleci.com/gh/mozilla-services/elmo-automation has builds now.

I spent a few trying to figure out why the build would break, and I hope I got an answer. gpg-agent has a couple of special files and sockets in GNUPGHOME, and it seems that sometimes the agent is already gone, and sometimes it's not. I added a command to explicitly stop the agent in https://github.com/mozilla-services/elmo-automation/compare/db3bd7598900...a2eedb6ea49b, let's see if that fixes it.

Miles, can you set up:
 DOCKER_DEPLOY: true
 DOCKER_USERNAME
 DOCKER_PASSWORD

to kick off uploads to docker hub? They'd go up as mozilla/elmo-a10n:latest and  mozilla/elmo-bb:latest

Comment 2

[Axel Hecht [:Pike]]

And https://circleci.com/gh/mozilla/elmo is building.

Elmo uses git flow, which means that builds from develop should only go on stage, and builds from master on prod. Do we need to do something on the image side to support that?

Also, the amount of test coverage that runs prior to building isn't full yet, the full combination of settings (compress etc) is only run on travis. And I cheat when setting up mysql, I `sleep 5` instead of doing something constructive.

Comment 3

[Miles Crabill [:miles]]

We have a full CI pipeline including pushing to dockerhub and mirroring to cloudops' docker registry configured.

Resolving this.