search

larsenwork / monoid

Customisable coding font with alternates, ligatures and contextual positioning. Crazy crisp at 12px/9pt. http://larsenwork.com/monoid/
7.86k stars 170 forks source link

Circleci seems to run with every push #57

Closed larsenwork closed 9 years ago

larsenwork commented 9 years ago

@chase Didn't we have "only run when changes are made to the source folder" working at some point or am I mistaken?

It's currently running even if it's just gh-pages being updated screen shot 2015-07-21 at 12 20 25

chase commented 9 years ago

We did, but I disabled it because you were annoyed that it came up with this error: Error

chase commented 9 years ago

Regarding the gh-pages thing, it isn't actually running tests thus the red No Tests label. It is taking up queue time because for some damn reason it is fetching the source cache and blocking actual builds.

I have a solution in mind, let me whip something up on my personal branch.

larsenwork commented 9 years ago

Cheers.

Could a simple (?) solution be to have a boolean variable in build.py called runCircleCI or something similar. So that circleci only builds when that's true and a build obviously changes the value from true to false?

chase commented 9 years ago

The simplest solution would be to just un-comment the code you see above. I'm going to put it in a file with a name that should make it more clear what it is doing, that way nobody gets confused about that really long error, haha.

I'm also making it so that the release branch isn't cached and is actually pushed off of a template branch. This will prevent the wait after I rebuild without the cache.

larsenwork commented 9 years ago

:clap:

chase commented 9 years ago

Also just figured out a way to not rely on prior release markers for Source changes, so that'll make things even quicker.

chase commented 9 years ago

So far we're down to 11:32 and better change checks. Not sure if that will be consistent, since CircleCI is STILL pulling a branch I tell it to ignore.