科技回声

Why does this exist? Great, let's get some stuck builds going on a great platform like Travis instead of fixing your awful build process.No, stop, and get this garbage out of here.

Why so mean? <a href="https://github.com/naftulikay/travis-pls/pull/2" rel="nofollow">https://github.com/naftulikay/travis-pls/pull/2</a>

so your flipping off the company that is testing opensource projects for free because your build process is wonky?

So, we're circumventing tools that kill possible stuck jobs now? That doesn't seem like it'll play out well with Travis CI...

I hear the frustration, but what about optimizing the build? Are there pieces that can be cached? What's the longest running part and why?

I use this script:<pre><code> #!/bin/bash set -eu (while sleep 60; do echo Do not kill me yet!; done) & "$@"</code></pre>

How about fixing your own build instead of exploiting a service that's doing your building and testing for you for FREE.

The use case mentioned in the README around Packer and building AMIs seems very valid to me. If Travis is fine with longer builds (they provide a way to avoid timeout) I don't see why everyone is pouring hate on this.