1469302 - Allow t-b-v CircleCI job to upload artifacts

Status: RESOLVED FIXED

(Data Platform and Tools Graveyard :: Operations, enhancement, P1)

Description

[Jeff Klukas [:klukas] (UTC-4)]

I'm working on moving t-b-v to use CircleCI rather than TravisCI to take advantage of more advanced workflows and caching features.

I've updated envvars to do most of what we need for the artifacts upload:

https://circleci.com/gh/mozilla/telemetry-batch-view/edit#env-vars

There are AWS creds already available for that job, but they don't appear to allow uploading of artifacts to net-mozaws-data-us-west-2-ops-ci-artifacts.

Can we provide that CircleCI project with the same S3 access that the TravisCI job has [1]?

[1] https://travis-ci.org/mozilla/telemetry-batch-view/settings

Comment 1

[Jason Thomas [:jason]]

The current AWS credentials configured in the CircleCI t-b-v job has put access to net-mozaws-data-us-west-2-ops-mavenrepo. Are we planning on deprecating use of 'net-mozaws-data-us-west-2-ops-mavenrepo' and moving towards storing objects in 'net-mozaws-data-us-west-2-ops-ci-artifacts'?

For now I've provisioned new AWS credentials which include the same access as the credentials in https://travis-ci.org/mozilla/telemetry-batch-view/settings and retains put access to net-mozaws-data-us-west-2-ops-mavenrepo.

Comment 2

[Jeff Klukas [:klukas] (UTC-4)]

> Are we planning on deprecating use of 'net-mozaws-data-us-west-2-ops-mavenrepo' and moving towards storing objects in 'net-mozaws-data-us-west-2-ops-ci-artifacts'?

No, these two buckets are used for different things. t-b-v had both a CircleCI job configured which just uploaded the maven artifact and a TravisCI job configured that ran tests and uploaded the uberjar artifact.

Now, I'm proposing to spin down the TravisCI job completely and have CircleCI handle both the maven artifact and the uberjar artifact.

So, the creds you've provisioned should be perfect. At the conclusion of this work, we should be able to destroy the TravisCI job and associated credentials.

Comment 3

[Jason Thomas [:jason]]

Okay great. Please reopen if you have any issues.