* stable-3.1:
Update highlight.js
Add "Page ..." next to back and forward arrows
Fix the size of the commit message box
Bazel: Fix issues flagged by buildifier
Document that gerrit supports JDK 11
lib/lucene: merge jars using a java_binary rule
Change-Id: I9807d05de588e8437310ade18e2e5e9c84d2fe27
* stable-2.16:
Update highlight.js
Bazel: Fix issues flagged by buildifier
Document that gerrit supports JDK 11
lib/lucene: merge jars using a java_binary rule
Adjust Documentation/licenses.txt to reflect new name of merged Lucene
library due to "lib/lucene: merge jars using a java_binary rule".
Change-Id: Iae42e901c8756e46effd1302df9449e37c52f262
Asciidoc may fail to render link attributes for external links
supposed to open in a new window correctly. This change adds
:linkattrs: to the beginning of such files to force parsing link
attributes correctly.
Bug: Issue 12068
Change-Id: If18be60de646ff78f672239dd4fa435fd4fd92ab
To make it easier to stay on track when reading documentation, I
added ",role=external,window=_blank" to all links in the
documentation directory that were not pointing at another piece of documentation.
Change-Id: I94bf254c90f8ebce067c765be0a2932b755a045a
* stable-3.0:
Use consistent capitalization for term NoteDb in documentation
Document how to backup Gerrit
Update rules_closure to latest version
Change-Id: I91e82cc4cbf8336ca5c9b47fcb380dfacae6a57f
* stable-2.16:
Use consistent capitalization for term NoteDb in documentation
Document how to backup Gerrit
Update rules_closure to latest version
Change-Id: I4847dcda27466ece557641e9c579fcf70f7f88c1
Remove outdated references to ReviewDb. Where ambiguous terms like
"database" are used, make sure they are still technically accurate, or
else remove them.
After this change, all documentation should be up to date with respect
to the database backend, with the exception of note-db.txt itself.
Change-Id: I7134087dc56070788e81ada6ac504b3c8fe84c4c
ReviewDb no longer exists and NoteDb is now always used.
Change-Id: I01c613e5b3ace4a8874b270a692bd1972774e947
Signed-off-by: Edwin Kempin <ekempin@google.com>
ReviewDb is gone and we no longer need to initialize the database
section in gerrit.config on init.
Change-Id: Id77d3293db7c769f25033016bee398aad0054ba0
Signed-off-by: Edwin Kempin <ekempin@google.com>
* stable-2.15:
BranchApi: Add missing throws declaration on NotImplemented#reflog
FormatUtil: Fix Math#round() truncation error flagged by error-prone
ReflogIT: Add test coverage for reflog permissions
ChangeIT: Move reflog test to ReflogIT
ChangeIT: Fix and expand reflog test
BranchApi: Add method to get the branch's reflog
GetReflog: Move ReflogEntryInfo to a separate class in extension API
Fix http_archive rule in WORKSPACE
ConfigInfoImpl: Return raw byte value for effective value
TransferConfig: Move getEffectiveMaxObjectSizeLimit to ProjectState
ProjectIT: Factor out a method to set the max object size limit
Documentation: linux-quickstart - include Java 8 requirement
Documentation: Include Java 8 requirement in installation notes
Documentation: Remove 'install-quick' page in favour of 'linux-quickstart'
Change-Id: I895790a8b2f9e8439e91c15ba4ee9a5a14a4ee94
* stable-2.14:
ProjectIT: Factor out a method to set the max object size limit
Documentation: Include Java 8 requirement in installation notes
Change-Id: Ia68061cca3a46aa9744f2c1d6b9814eb2f092d30
We're still on Gerrit version 2.x but when we move to 3.0 it
will not make sense to have the user named "gerrit2".
Update all the documentation to refer to "gerrit" instead.
Also change the Jetty configuration to use "gerrit" instead.
Change-Id: I43a343669ac936b0585ee15e07d15643f9c3d6eb
* changes:
New daemon start/stop methods for use with Procrun
Correctly call ssh-keygen on Win32 with empty passphrase
Redirect output from ssh-keygen call to console to see potential errors
There were several different notations used for NOTE and IMPORTANT
sections that sometimes didn't even render correctly.
Change-Id: I744cb0922f4bb4c99282984a487761f2c1bd6d4a
Signed-off-by: Michael Ochmann <michael.ochmann@sap.com>
With the new stylesheet example blocks (delimited with ====) are
rendered as rather intrusive boxes with large padding in yellow
and grey.
This patch replaces the example blocks with simple code blocks
(delimited with ----) that better match the overall style of the
documentation.
Change-Id: Id95387cdb153332c2066e2d5e378697647dbca52
Signed-off-by: Michael Ochmann <michael.ochmann@sap.com>
Added additional entry points GerritLauncher.daemonStart and
GerritLauncher.daemonStop for use when hosting Gerrit in some other
process. The intention of this is to make it an easy fit to the [Apache
Commons Daemon Procrun][1]. This adds an easy way to host Gerrit with
embedded Jetty as Windows Service.
Also moved a bit of logic in Daemon from anonymous thread into the stop
method.
[1]: http://commons.apache.org/proper/commons-daemon/procrun.html
Change-Id: Ie1fd3b7fceb56e159dc7f02fbcf481b0fcdb08e2
The page with the title "Project Configuration" was referred to as
"Project Setup". Moreover, it was contained in a file with the name
"project-setup.txt".
Change-Id: Iab834981893967bfbcba8214e118689ea348b93b
Signed-off-by: Stefan Lay <stefan.lay@sap.com>
Configures the SSHD daemon to enable support the extra strength
ciphers -if- available in the current JRE. These extensions can be
installed by downloading the JCE policy files from Oracle and
following the installation instructions.
Change-Id: Idd934a29b049b61cddadde5bf797514fcbc654d9
We previous use the section title style like:
Section level 1
===============
Section level 2
---------------
Which have a problem in Asciidoctor that the number of "="s or "-"s must match
the number of characters in the header exactly, as a result it's easy to make
mistakes while changing the titles. Asciidoctor provides a better style like:
= Section level 1
== Section level 2
So we switched to this style.
Also fixed a bug in replace_macros.py, which will not cause any problem in the
old style.
Change-Id: I811dd7238735d98f662767c17086152cd69aea02
To correctly configure the daemon to start and stop with the operating
system, some lines need to be enabled in the gerrit.sh script.
Mention this in the documentation.
Bug: Issue 2188
Change-Id: Id423cff86e894907d45e27ebab89e1ec7100e08d
The documentation refers to an outdated site that does not actually
have any of the release binaries any more.
Update it with a link to the current releases site.
Change-Id: I78bb7235f77cf02d41e438967cdc78b5814ce8ae
This supports automatic site initialization on Gerrit server startup
when Gerrit runs in a servlet container. Both creation of a new site
and upgrade of an existing site are supported.
This feature may be useful for such setups where Gerrit admins don't
have direct access to the database and the file system of the server
where Gerrit should be deployed and, therefore, cannot perform the
init from their local machine prior to deploying Gerrit on such a
server. It may also make deployment and testing in a local servlet
container faster to setup as the init step could be skipped.
The site initialization will be performed only if the 'gerrit.init'
system property exists (the value of the property is not, used only the
existence of the property matters).
If the 'gerrit.site_path' system property is defined then the init is
run for that site. The database connectivity, in that case, is defined
in the etc/gerrit.config.
If 'gerrit.site_path' is not defined then Gerrit will try to find an
existing site by looking into the system_config table in the database
defined via the 'jdbc/ReviewDb' JNDI property. If system_config table
exists then the site_path from that table is used for initialization.
Database connectivity is defined by the jdbc/ReviewDb JNDI property.
Finally, if neither 'gerrit.site_path' property nor the system_config
table exists, the 'gerrit.init_path' system property, if defined, will
be used to determine the site path. Database connectivity, also for this
case,is defined by the jdbc/ReviewDb JNDI property.
Example 1:
Prepare Tomcat so that a site is initialized at a given path using
the H2 database (if the site doesn't exist yet) or using whatever
database is defined in the etc/gerrit.config of that site:
$ export CATALINA_OPTS='-Dgerrit.init -Dgerrit.site_path=/path/to/site'
$ catalina.sh start
Example 2:
Prepare Tomcat so that an existing site with the path defined in the
system_config table is initialized (upgraded) on Gerrit startup. The
assumption is that the jdbc/ReviewDb JNDI property is defined in
Tomcat:
$ export CATALINA_OPTS='-Dgerrit.init'
$ catalina.sh start
Example 3:
Assuming the database schema doesn't exist in the database defined
via the jdbc/ReviewDb JNDI property, initialize a new site using that
database and a given path:
$ export CATALINA_OPTS='-Dgerrit.init -Dgerrit.init_path=/path/to/site'
$ catalina.sh start
Change-Id: Ic3e8c993087d2fbb38e14479a539dc62495ad908
Gerrit administrators can put per-project themes in
$site_path/themes/{project-name}; the same header/footer/CSS filenames
are supported as for sitewide themes. These are inherited and cached
per-project and exposed via GET /projects/X/config.
Themes must be provided by a site admin rather than arbitrary project
admins, so the site admins can be responsible for making sure themes
do not introduce XSS vulnerabilities.
Change-Id: I065d9e6d4df9275b963bb142ec11f66b5604678b
Update the symbolic link commands to be absolute so they are more
universal in site setup. Additionally, fix the commands so that
the service is stopped/started with the proper name.
Change-Id: Ia426d5b087350db59e02b8bfc46e5a660644dccd
Separate the database setup instructions out into a shared file
so the same text can be included in the Tomcat install instructions
later.
Change-Id: I91dae81f8dc7ad361a40f7a76ec74ec69aaa4250
This splits all of the replication code out of the core server
and moves it into a standard plugin. A new listener API is used
inside of the core server to notify interested plugins of any Git
reference changes, which the replication code can hook into to
schedule its events.
Change-Id: I77ee4440a009c2ce1c62fb6a445c7e3c912245f9
The new document covers quick installation, new project and first upload.
It contains lots of quoted output, with a demo style to it.
Change-Id: I9404376b527368a8348da507422c3912085e63d9
Signed-off-by: Fredrik Luthander <fredrik.luthander@sonyericsson.com>
The installation instructions presumes much prior knowledge.
This is an attempt at making some of that knowledge less implicit.
Change-Id: I56195eedbe8c73248e2545a95f2237d16a1d54ed
This will allow users of different web servers to contribute
instructions for non-Apache web daemons.
Change-Id: I94763a428c109c0106e7bef40da1179fa7284165
Signed-off-by: Francois Marier <francois@debian.org>
This meant fixing old tables syntax, adjusting some overly long header
underlines and some other small issues.
Change-Id: I2701a5040d225454225034ed5ef7861580743707
Now that installation is more or less just one command with a guided
interaction asking configuration questions we can start to simplify
the user guide.
Change-Id: Id98f9843d29e1fe0b445c2a714ace9ec3938ff79
Signed-off-by: Shawn O. Pearce <sop@google.com>
Now that the 2.x code base is over a year old, and has been in
production for almost a full year, its time to stop calling this
'Gerrit2' and start referring to it by the complete project name,
Gerrit Code Review.
Change-Id: Ifb37dd63b94ed7e1b938511aa0fc2a6ad3c981d6
Signed-off-by: Shawn O. Pearce <sop@google.com>