1466588 - Deploy ActiveData for Public Bug Snapshots

Status: RESOLVED FIXED

(Testing Graveyard :: Bugzilla-ETL, enhancement)

Description

[Kyle Lahnakoski [:ekyle]]

This bug tracks the software development, circleci work, and deployment of an ActiveData instance for public access to bug snapshots.

Comment 1

[Kyle Lahnakoski [:ekyle]]

Deployment can be done off of `bugzilla-etl` branch. The current tag is bugzilla-etl-18-06-28. 

branch - https://github.com/mozilla/ActiveData/tree/bugzila-etl
tag - https://github.com/mozilla/ActiveData/releases/tag/bugzilla-etl-18-06-28

We must define what the environment variables are so I can make a config.json file that uses them.

Comment 2

[Kyle Lahnakoski [:ekyle]]

I have a candidate docker image for the frontend service. It does not include nginx, which I assume you have elsewhere in your infrastructure to handle the encryption, and certs.

Here is a tagged version to test
https://github.com/mozilla/ActiveData/releases/tag/v2.0

Here is the source code tip
https://github.com/mozilla/ActiveData/tree/dev/resources/docker


ckolos: please review and get back to me on what other requirements must be satisfied.  Thank you

Comment 3

[Chris Kolosiwsky [:ckolos] (ckolos has left the building)]

Does this build a docker image via CircleCI? I'm not an admin in the mozilla github org, so I can't verify.

Comment 4

[Kyle Lahnakoski [:ekyle]]

Here is the circleci branch that produces an docker image as an artifact:

https://circleci.com/gh/mozilla/ActiveData/tree/bugzilla-etl

Notice the build has REPO_TAG environment variable (currently set to v2.0)

I am not sure how you want to set this environment variable; it is currently set using the circleci web admin interface (where the secrets are put). What is the sequence of events for tagging a revision and triggering a build?

I know what to do when there is NO tag, but I do not know if I build-then-tag, or tag-then-build

1) Someone (ekyle) decides a new version should be deployed
2) ekyle merges working version to `bugzilla-etl` branch
3) circleci build is triggered
4) circleci runs tests, and builds image from tip of bugzilla-etl
5) ekyle tags tip of bugzilla-etl if successful

Comment 5

[Chris Kolosiwsky [:ckolos] (ckolos has left the building)]

It's up to you on when you want to build a container.

The process you describe works fine for me; All I really care about is getting a working, deployable container. If you want to test your branches and not build until you've tagged (tag-then-build), then I think the method described here might work for you: https://circleci.com/docs/2.0/workflows/#git-tag-job-execution

Comment 6

[Kyle Lahnakoski [:ekyle]]

Please add docker variables to the circleci ActiveData project.  I will then add the script to push image to docker.

https://circleci.com/gh/mozilla/ActiveData/48

Comment 7

[Chris Kolosiwsky [:ckolos] (ckolos has left the building)]

done.

Comment 8

[Kyle Lahnakoski [:ekyle]]

it looks like a success

https://circleci.com/gh/mozilla/ActiveData/51


please review 

https://github.com/mozilla/ActiveData/blob/bugzilla-etl/.circleci/config.yml

Comment 9

[Chris Kolosiwsky [:ckolos] (ckolos has left the building)]

looks like it works, successful push to Dockerhub.