circleci

rm -rf /home/circleci/.gitconfig
borkdude 2019-05-22T19:12:05.015900Z

right now I’ve got this in a script (thanks to @slipset):

if [ -z "$CIRCLE_PULL_REQUEST" ] && [ "$CIRCLE_BRANCH" = "master" ]
then
    lein deploy clojars
fi
but I’ve also discovered this in the workflow config:
- deploy:
          filters:
            branches:
              only: master
but considering the condition I have in the script, I’m wondering how the below behaves if user foo does a PR from his master branch to my master branch…

borkdude 2019-05-22T19:13:08.016400Z

I guess it doesn’t hurt, since foo doesn’t have the right credentials anyway, but ok.

borkdude 2019-05-22T20:54:01.017300Z

when you’re building docker images on CircleCI can you cache the layers somehow, so on a new build it’s skipping the steps that are cached?

2019-05-23T12:16:38.020900Z

Before DLC We’ve had a similar setup to this: https://anonoz.github.io/tech/2018/06/17/circleci-docker-caching.html Which worked good as well (although not as easy to setup :P)

borkdude 2019-05-23T12:18:12.021300Z

well actually my thought was: maybe this is easier on CircleCI CPU, so they would benefit. but it seems that they want you to pay to enable it, so my assumption must be wrong. I actually don’t care that much, I can wait two minutes. (cc @marc-omorain)

borkdude 2019-05-22T20:54:41.017500Z

https://circleci.com/docs/2.0/docker-layer-caching/