document how to get Travis CI running on your fork of tor

changed milestone to %Tor: 0.3.4.x-final

added 034-included-20180328 034-roadmap-subtask 034-triage-20180328 component::core tor/tor milestone::Tor: 0.3.4.x-final new-developers owner::Hello71 parent::25550 priority::medium resolution::implemented reviewer::catalyst severity::normal sponsor::3 status::closed tor-ci tor-doc type::task labels

Trac:
Keywords: N/A deleted, new-developers tor-ci tor-doc added

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.3.x-final

travis:

1. sign up for GitHub
2. fork https://github.com/torproject/tor/ (https://help.github.com/articles/fork-a-repo/)
3. go to https://travis-ci.org/ and log in.
4. press the profile button in the top right.
5. search for "tor". if you don't find it, press "Sync account".
6. enable "tor".
7. push to GitHub as usual. builds will show up at travis-ci.org and at #tor-ci.

cool! Do you think you could put this in a patch that we could put somewhere in doc/HACKING -- either in HelpfulTools or GettingStarted ?

I'd like us to have some official statement about the torproject/tor GitHub repository before putting these instructions anywhere official.

(I should probably draft one and have isis and other interested people review it, assuming we actually got the group account ownership transferred as planned.)

Trac:
Sponsor: N/A to Sponsor3
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final

Trac:
Parent: N/A to #25550 (moved)

I have a question - how do we want to keep scripts/instructions in sync with tor's own CI infrastructure?

For example right now I am using libevent and openssl provided by msys64 project, but the CI is building their own.

Also there are some compiler flags being set in the tor project CI that I might want to add.

How to keep all of this synchronized? Do we need to?

Trac:
Username: saper

Trac:
Keywords: new-developers tor-ci tor-doc deleted, tor-doc, 034-roadmap-subtask, tor-ci, new-developers added

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Trac:
Keywords: N/A deleted, 034-included-20180328 added

https://cgit.alxu.ca/tor.git/commit/?h=bug23883

Trac:
Status: assigned to needs_review

Trac:
Reviewer: N/A to catalyst

https://cgit.alxu.ca/tor.git/diff/?id=bug23883&id2=master

added fixup commit

Trac:
Status: needs_review to assigned
Owner: catalyst to Hello71

Thanks for the patch!

Do we want to recommend travis-ci.com instead of travis-ci.org for people who are new to Travis? It seems like Travis is recommending travis-ci.com for new users.

It should probably specify that #tor-ci is on the OFTC IRC network.

Maybe this needs a changes file?

Trac:
Status: assigned to needs_revision

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 .".

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.

amended commit pushed for review at same place.