#22636: Add Travis configs so GitHub forks get CI coverage -------------------------------------------------+------------------------- Reporter: catalyst | Owner: | patrickod Type: defect | Status: | needs_review Priority: High | Milestone: Tor: | 0.3.2.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: continuous-integration ci testing | Actual Points: .5 best-practice unit-testing new-developers | travis | Parent ID: | Points: .5 Reviewer: catalyst | Sponsor: -------------------------------------------------+-------------------------
Comment (by isis): Replying to [comment:12 nickm]: > Sounds fine -- actually, if you just do a backport to 0.2.4, then when I merge to maint-0.2.4, it should merge forward cleanly to everything else. Okay, done in my `bug22636_0.2.4` [https://gitweb.torproject.org/user/isis/tor.git/log/?h=bug22636_0.2.4 branch]. This is for 0.2.4 through 0.3.0. I rebased out all the rust toolchain stuff, since that would fail and also waste time. [https ://travis-ci.org/isislovecruft/tor/builds/253404823 Tests pass]. My `bug22636_0.3.1` [https://gitweb.torproject.org/user/isis/tor.git/log/?h=bug22636_0.3.1 branch] is for 0.3.1. [https://travis- ci.org/isislovecruft/tor/builds/253406184 Tests pass]. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22636#comment:13> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs