Closed Bug 1380531 Opened 3 years ago Closed 3 years ago

Write initial CircleCI configuration for BMO

Categories

(bugzilla.mozilla.org :: Infrastructure, enhancement)

Production
enhancement
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: dylan, Assigned: dylan)

References

Details

Attachments

(1 file)

PR
45 bytes, text/x-github-pull-request
dylan
: review+
Details | Review
As part of the cloudops migration, BMO needs a CircleCI configuration that builds a docker image for {master,development,production} branches.
Reading through https://circleci.com/docs/2.0/ it seems like the "image" I specify when using this
could just be anything, as I literally don't care what the executer docker container is, as all my code runs in the docker container that is built from the repo, right?

This is with providing a 'setup_remote_docker' step, of course: https://circleci.com/docs/2.0/building-docker-images/
Flags: needinfo?(ckolos)
You should use the centos:6 image for your docker container. It's immaterial which container circle builds with (until it isn't, of course, but we're not there yet :) )
Flags: needinfo?(ckolos)
(In reply to Chris Kolosiwsky [:ckolos] from comment #2)
> You should use the centos:6 image for your docker container. It's immaterial
> which container circle builds with (until it isn't, of course, but we're not
> there yet :) )

my image is already built. Or that is, it is already centos:6 and I think you've confirmed my question. Thanks!
Blocks: 1383355
Summary: Write circleci configuration for BMO → Write initial CircleCI configuration for BMO
Attached file PR
Attachment #8889002 - Flags: review?(ckolos)
Attachment #8889002 - Flags: review?(ckolos) → review+
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Out of curiosity, why CircleCI and not Travis?
In cloudops, CircleCI is used to automate the docker build/push process.
You need to log in before you can comment on or make changes to this bug.