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…I guess it doesn’t hurt, since foo doesn’t have the right credentials anyway, but ok.
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?
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)
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)