-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: CircleCI migration #277
Conversation
0b45b30
to
facd9d0
Compare
facd9d0
to
26e5c7f
Compare
1042d07
to
7e88364
Compare
89b39c1
to
fec996a
Compare
fec996a
to
94caf76
Compare
418b37f
to
d55620c
Compare
ec5102b
to
ade434c
Compare
887467c
to
9c8a134
Compare
d8db42c
to
966fce8
Compare
efa175e
to
4c284d5
Compare
5ddace2
to
7988c80
Compare
c8a86a3
to
bba85da
Compare
sudo mkdir -p $BUILDX_CACHE && sudo chown -R circleci:circleci $BUILDX_CACHE | ||
make images | ||
name: Configure buildx cache | ||
command: export BUILDX_CACHE=/tmp/cache/buildx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm no CircleCI expert, but does this do anything for other steps? I thought each step was ran in a fresh shell.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yip, each step is a fresh shell. Making this a command (line 9) allows me to reuse it for the e2e-test (line 194) and build-and-push (line 224) without needing to repeat (and maintain) it
No description provided.