Re-running Travis-CI build?

[Dave Porter]

Hey, does anyone know how to trigger a re-run of Travis-CI for a particular build? I've got an open pull request here that lists a failed Travis-CI run; the run failed prior to running any unit tests, due to some ... pastebin gem something something. It looks like it just randomly died. There's discussion on the Travis-CI repo itself (here) of a "rebuild" button available to repo owners; Tyler, do you see anything?

Dave

[Tyler Keating]

I clicked on the "Restart" button, I think it's going again.

--

Tyler Keating

ty...@sproutcore.com

On Sep 24, 2013, at 12:03 PM, Dave Porter <dcpo...@gmail.com> wrote:

Hey, does anyone know how to trigger a re-run of Travis-CI for a particular build? I've got an open pull request here that lists a failed Travis-CI run; the run failed prior to running any unit tests, due to some ... pastebin gem something something. It looks like it just randomly died. There's discussion on the Travis-CI repo itself (here) of a "rebuild" button available to repo owners; Tyler, do you see anything?

Dave

--
You received this message because you are subscribed to the Google Groups "SproutCore Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sproutcore-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Dave Porter]

Success! Thanks Tyler.

[Umberto Nicoletti]

the error you just saw could be related to gem failing to find the pastebin gem because network error, load on the gem servers, etc

[Dave Porter]

Yup - I gather that there are lots of little reasons that a build could fail, so having the re-run button available is a very nice thing. (Less nice, for Tyler, is that he appears to be the only one with it.)

--