Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Document that we use `ts` automatically in Travis CI.

This commit is contained in:
Tim Abbott 2017-06-14 17:26:41 -07:00
parent 5e4acbaba3
commit fa87c6113d
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/travis.md
View File

@ -55,6 +55,10 @@ our configuration, you'll want to look at these closely.
## Useful debugging tips and tools ## Useful debugging tips and tools
* Zulip uses the `ts` tool to log the current time on every line of
the output in our Travis CI scripts. You can use this output to
determine which steps are actually consuming a lot of time.
* For performance issues, * For performance issues,
[this statistics tool](https://scribu.github.io/travis-stats/#zulip/zulip/master) [this statistics tool](https://scribu.github.io/travis-stats/#zulip/zulip/master)
can give you test runtime history data that can help with can give you test runtime history data that can help with
@ -66,12 +70,6 @@ our configuration, you'll want to look at these closely.
that every remote branch you push will be tested, which can be that every remote branch you push will be tested, which can be
helpful when debugging something complicated. helpful when debugging something complicated.
* You can
[use the ts tool](https://github.com/zulip/zulip/commit/da731c) to
get timing for every line of your Travis scripts (which can help
with performance debugging). Note, however, that `ts` always return
exit code 0, so with that patch, Travis CI will always report success.
[travis-fork]: git-guide.html#step-3-configure-travis-ci-continuous-integration [travis-fork]: git-guide.html#step-3-configure-travis-ci-continuous-integration
## Performance optimizations ## Performance optimizations