Adam Spiers ([email protected]) wrote: > I'm really keen that I (or James, or anyone else) don't become the > bottleneck on Travis builds. I really think it needs to be a > team-wide responsibility, e.g. if anyone sees test failures and thinks > they may have caused them, that they take the lead in resolving them. > That's especially true right now based on the other mail I just sent > to the list, since we're in a situation where pull requests are not > automatically tested prior to merge, and consequently trunk is at much > higher risk than it should be. > > To this end, I have already spent quite a bit of effort trying to > ensure that the whole testing setup is properly documented in a way > that everyone can understand, e.g. > > https://github.com/crowbar/crowbar/blob/master/doc/devguide/testing/travis.md > https://github.com/crowbar/crowbar/blob/master/doc/devguide/testing.md > > That said, I do admit that it is currently missing a "how to > troubleshoot Travis test failures" section, and that is a sore > omission - thanks for helping me realise that! However I have no time > to write this since I have to start preparing the rspec talk for > tomorrow, and anyway, I think I've done far more than my fair share of > documentation work recently ;-) So can I suggest that someone else > take ownership of writing this, and use it as a good exercise in > learning about the Travis builds in the process? Shouldn't be a big > job, and of course I'm happy to answer any questions which may arise.
Oh well, for some reason I ended up doing this myself %-) https://github.com/crowbar/crowbar/pull/1747 _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
