Michael Hart

Hmm, now that I've said that, I can't find out how to do it when you're not on a pull request – will poke around a bit more

Well... you can definitely see the last build of a branch, eg: https://github.com/lambci/lambci/branches (clicking the little tick or cross will take you to the build log)

There's also another sort of hacky way to do it using the compare view: https://github.com/lambci/lambci/compare/master@%7B1week%7D...master (scroll down to the bottom and you can see a link to each build with...

Oh nice! I'm not sure I'll include something exactly like that because ppl can exhaust your DynamoDB throughput pretty easily that way (because they can execute anything they want), but...

Yeah, fair enough. I think for most ppl it's a rare enough use case that they can just browse via GitHub (I could add a link to the static page...

You'd need to build gcc 5.4.0 for Lambda, store that tarball somewhere (eg, S3) and then download and unpack it before your build. The main thing to be aware of...

When you say you expect a failure response – do you mean that the build wasn't being marked as failed? What state was it in?

Gotcha – right, the problem is that it's impossible to know the full configuration until a git clone – because the config files can sit in the repository itself. So...

Oh nice move with the two stacks – can I ask what the reason for doing that was? Is it so that you can run different tasks in parallel (eg,...

@jhurliman interesting – is there any documentation on this? Or is the hostname literally the only difference? It would certainly be straightforward to add this as a config param – ...