#23883: document how to get Travis or GitLab CI running on your fork of tor -------------------------------------------------+------------------------- Reporter: catalyst | Owner: Hello71 Type: task | Status: | needs_revision Priority: Medium | Milestone: Tor: | 0.3.4.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: new-developers, tor-ci, tor-doc, | Actual Points: 034-roadmap-subtask, 034-triage-20180328, | 034-included-20180328 | Parent ID: #25550 | Points: Reviewer: catalyst | Sponsor: | Sponsor3 -------------------------------------------------+-------------------------
Comment (by Hello71): I decided to just point at https://docs.travis-ci.com/user/getting-started /#To-get-started-with-Travis-CI. I think we should have a page somewhere that shows the current team rotations. Here, I could write "if it doesn't work, ask #tor-dev or the current CI or community whatever member at <x>.". Good point about specifying the network. I think this doesn't need a changes file per CodingStandards.md, since nobody will wonder "why did we add the documentation to use Travis". maybe "why did we use Travis", but not why document it. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23883#comment:17> 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