Travis-Pls: Travis Builds That Don't Timeout
1–10 of 18 posts
Re: Travis-Pls: Travis Builds That Don't Timeout
#2So, we're circumventing tools that kill possible stuck jobs now? That doesn't seem like it'll play out well with Travis CI...
Re: Travis-Pls: Travis Builds That Don't Timeout
#3I use this script:
#!/bin/bash
set -eu
(while sleep 60; do echo Do not kill me yet!; done) &
"$@"Re: Travis-Pls: Travis Builds That Don't Timeout
#4I hear the frustration, but what about optimizing the build? Are there pieces that can be cached? What's the longest running part and why?
Re: Travis-Pls: Travis Builds That Don't Timeout
#5So, we're circumventing tools that kill possible stuck jobs now? That doesn't seem like it'll play out well with Travis CI...
Travis CI themselves offer a workaround for their own timeout in the form of travis_wait. This seems to be a slightly different alternative workaround that better meets the authors' needs.
Re: Travis-Pls: Travis Builds That Don't Timeout
#6Why 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.
Re: Travis-Pls: Travis Builds That Don't Timeout
#7Why 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.
I can imagine some cases where this might be necessary. But giving the middle finger to Travis leaves a bad taste in my mouth. Especially since the free offering is so generous and the 10 minute restriction seems completely reasonable.
Re: Travis-Pls: Travis Builds That Don't Timeout
#8so your flipping off the company that is testing opensource projects for free because your build process is wonky?
Re: Travis-Pls: Travis Builds That Don't Timeout
#9How about fixing your own build instead of exploiting a service that's doing your building and testing for you for FREE.
Re: Travis-Pls: Travis Builds That Don't Timeout
#10The 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.