| commit | 4bc26002c7cbcc4273830fefbb7a495e17f75805 | [log] [download] |
|---|---|---|
| author | Nodir Turakulov <nodir@google.com> | Tue Aug 18 18:24:37 2015 -0700 |
| committer | Dave Borowitz <dborowitz@google.com> | Thu Aug 27 17:38:19 2015 +0000 |
| tree | 5530b603b38bca6427cf95c49d05599aba603e0a | |
| parent | 6b7c621723699afd08e8507e4cba13db8731eabe [diff] |
ServletTest: base class for servlet tests There was some code duplication in servlet test classes. Also some of them created a servlet class (e.g. DocServlet) directly, and some of them used TestGitilesServlet. This change: * adds ServletTest class with methods buildHtml, buildData, buildText and buildJson. It uses TestGitilesServlet. * inherits all servlet test classes from ServletTest and removes a lot of duplicated code. Change-Id: Ie81c6cb4d6a4d3627d1dd462e89dfdf8f1ee54ee
Gitiles is a simple repository browser for Git repositories, built on JGit. Its guiding principle is simplicity: it has no formal access controls, no write access, no fancy Javascript, etc.
Gitiles requires Buck to build.
sudo apt-get install ant
cd ${HOME}
git clone https://github.com/facebook/buck.git
cd buck
ant
sudo ln -s ${PWD}/bin/buck /usr/bin/buck
cd /path/to/gitiles
git submodule update --init
buck build all
cd /path/to/repositories # Don't run from the gitiles repo. /path/to/gitiles/tools/run_dev.sh
This will recompile and start a development server. Open http://localhost:8080/ to view your local copy of gitiles, which will serve any repositories under /path/to/repositories.
If you'd like to use Eclipse to edit Gitiles, first generate a project file:
./bucklets/tools/eclipse.py --src
Import the project in Eclipse:
File -> Import -> Existing Projects into Workpace
The project only needs to be rebuilt if the source roots or third-party libraries have changed. For best results, ensure the project is closed in Eclipse before rebuilding.
Gitiles uses Gerrit for code review: https://gerrit-review.googlesource.com/
Gitiles uses the “git push” workflow with server https://gerrit.googlesource.com/gitiles. You will need a generated cookie.
Gerrit depends on “Change-Id” annotations in your commit message. If you try to push a commit without one, it will explain how to install the proper git-hook:
curl -Lo `git rev-parse --git-dir`/hooks/commit-msg \
https://gerrit-review.googlesource.com/tools/hooks/commit-msg
chmod +x `git rev-parse --git-dir`/hooks/commit-msg
Before you create your local commit (which you'll push to Gerrit) you will need to set your email to match your Gerrit account:
git config --local --add user.email foo@bar.com
Normally you will create code reviews by pushing for master:
git push origin HEAD:refs/for/master