Help with the Cloud Posse build-harness https://github.com/cloudposse/build-harness
Adding @ bot
@ has joined the channel
We have a number of teams (10-ish) running a number of PR builds daily through Travis - all of which are hitting github for the build-harness as well as a repo of extensions we built. I’m finding that we hit rate limiting pretty easily if we do unauthenticated curls to get the build-harness bootstrapped unless we use a github user and token. Since this differs from the nominal bootstrapping process, I wonder if others have hit a similar situation?
@David Schmidt makes sense, but first we have heard of it.
Consider using a Docker container instead for build-harness?
Ah, sage advice!
I pulled the docker image and took a look. So the question I have now is if it’s appropriate/possible to use it in an existing build system - i.e. to use the build-harness filesystem it already contains - or would a build need to be created inside of this container? Maybe seeing an example of how it’s used would help shape my brain.
This is probably why we don’t see it