#build-harness (2020-03)

Help with the Cloud Posse build-harness https://github.com/cloudposse/build-harness

2020-03-27

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Adding @ bot

discourse_forum avatar
discourse_forum
10:02:07 PM

@ has joined the channel

2020-03-18

2020-03-17

David Schmidt avatar
David Schmidt

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?

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@David Schmidt makes sense, but first we have heard of it.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Consider using a Docker container instead for build-harness?

1
David Schmidt avatar
David Schmidt

Ah, sage advice!

David Schmidt avatar
David Schmidt

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.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

This is probably why we don’t see it

    keyboard_arrow_up