Remove CCACHE variables from taskcluster mozharness config

RESOLVED FIXED

Status

RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: mshal, Assigned: mshal)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
We already set the CCACHE_* environment variables in the Dockerfile when building the image, so we don't need to also set them via the mozharness config. Having them in two places is confusing, especially when I tried to change the path in the Dockerfile and found it wasn't working.
(Assignee)

Comment 1

5 years ago
Created attachment 8492303 [details] [diff] [review]
bug1070067
Attachment #8492303 - Flags: review?(jlund)
Comment on attachment 8492303 [details] [diff] [review]
bug1070067

Review of attachment 8492303 [details] [diff] [review]:
-----------------------------------------------------------------

how will we run hack on these outside of automation. I kind of like defining our env within mozharness so devs don't have to figure out automation environment. Though, I suppose we can just give them a docker image :)
Attachment #8492303 - Flags: review?(jlund) → review+
(Assignee)

Comment 3

5 years ago
Yeah, the idea is that you would just download the docker image and run it in there. You could still probably use taskcluster-emulator.py outside of the docker image, but until this patch the CCACHE_DIR was assuming you were in a container anyway (unless your username is "worker" :).
(Assignee)

Comment 6

4 years ago
We're all set here.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.