New change workflows for changes not yet ready for full review (formerly Drafts).
The new PolyGerrit UI is mature enough for most uses.
Account data is stored in NoteDb.
NoteDb for change metadata is considered stable, and new sites use it by default.
NoteDb migration for change metadata is available.
Made several improvements and additions to the documentation to help users find the information they need.
This release contains schema changes. To upgrade:
java -jar gerrit.war init -d site_path
Support for draft changes and draft patch sets has been completely removed.
In most cases, the new Work-In-Progress workflow is a suitable replacement. Note that in the Draft workflow, an individual patch set can be a Draft. However, in both the new Work-In-Progress and Private workflows, WIP and Private apply to the whole change, not an individual patch set.
When upgrading from an earlier version, draft changes are migrated. This applies to all draft changes, or changes with draft patch sets (even if the highest patch set is not a draft), as follows:
The upgrade process prompts (once) for what Drafts should be migrated to; either WIP (default) or Private.
The migration means that some draft patch sets, which were previously hidden, might now be visible to some users who could not previously view them.
Change owners can make them private again using the “Mark Private” option in the UI, or using the REST API.
Historically, Gerrit would retroactively change votes on a label when permissions for the voting user changed. For example, if a user voted Code-Review+2, but then later lost permission to vote +2 (for example, was removed from a Maintainers group), all CR+2 votes by that user on open changes would suddenly appear as CR+1. In 2.15, this retroactive behavior no longer applies: the CR+2 votes remain CR+2, even if permissions were changed.
This new behavior makes label permissions more consistent with other permissions: usually, permission changes don‘t apply retroactively (you can’t un-submit a change), and the permission is only checked at the time an action is performed. It also fixes some technical issues and improves performance of reindexing changes.
Starting in the 2.14.x bugfix series, all release JARs and documentations are signed by the Gerrit maintainers. This policy will continue for all future releases.
By default, all Gerrit URLs generated and used by the UI include not just the change number but the project name as well.
In addition to providing more context to humans reading the URL, this new scheme improves performance under NoteDb, and paves the way for load balancing a multi-master installation with repository affinity.
Old URLs will continue to be supported, and simply redirect to the new URLs.
Almost all account data is now stored in NoteDb. The account data is migrated automatically during the upgrade process by running
The only account data not stored in NoteDb proper are the groups (remain in ReviewDb) and the reviewed flags which were moved to an external database (AccountPatchReviewDb) since 2.13.
For Gerrit slaves the branches that contain the account data must be replicated.
With this release, the new Gerrit storage backend, NoteDb, is officially supported for storing change metadata and is the default storage backend for new installations.
For existing sites, migration to the new backend may be done either offline or online in a running server.
Support for ReviewDb will be removed in Gerrit 3.0. Gerrit 3.0 will only support offline migration; to run an online migration, you must use the 2.15.x series.
The setup documentation now recommends setting up a user named
gerrit instead of
gerrit2. This username can be anything; the choice of name doesn't affect any functionality. However, some example commands in the documentation may refer to the new
gerrit user, so admins might need to tweak them to refer to
In 2.15, posting a review including a vote on any labels that does not exist or is outside of the permitted range based on the ACLs will now always result in a failure of the entire operation. Previously, if the “strict labels” option was set to disabled in the review input, votes to any invalid labels would be silently ignored. This option has now been removed from the REST API's ReviewInput as well as the SSH review command.
CI systems that rely on the non-strict behaviour of earlier Gerrit versions may require additional configuration to avoid casting votes to labels which are invalid for the change.
Following feedback on the 2.15 release a new configuration option
change.strictLabels was introduced in 2.15.2 to allow the new strict functionality to be optionally enabled. By default it is disabled to maintain backwards compatibility with previous release.
Implement admin interface (projects, groups and plugins).
Refreshed UI based on material design.
Add hashtag support.
Add support to show uploader on change screen.
Lots of bug fixes.
The draft change feature has been removed, and replaced with two separate features:
Changes can be ignored, or marked as reviewed, to reduce email notifications and keep dashboards cleaner.
When a change is reverted via the “Revert” button, this fact is recorded in the change metadata of the newly-created revert change, not just in the commit message as in the past. A new search operator
revertof: allows for searching for reverts of a given change.
Individual inline comments can be deleted after the fact by site administrators.
Users may be CCed on changes by entering their email address, even if they have not registered an account on the Gerrit server.
This feature is only available when using NoteDb.
When pushing new patch sets on a change or a series of changes, users can configure Gerrit to automatically publish any pending draft comments they have on those changes, avoiding the need to click through the web UI to publish all comments.
When diffing two patch sets of the same change that have different parents, some differences between the patch sets may be due to the rebase, instead of changes between the patch set and its base. These differences are now highlighted in the UI (PolyGerrit only), and are not counted towards the size of diffs.
When a push fails because the user does not have the required permission, the generic message
(prohibited by Gerrit) has been replaced with a detailed message describing the exact permissions required.
With this release, we have updated several sections of the documentation to make it easier for users to find the information they need. These updates include:
We have also made changes to improve navigation throughout the documentation.
ChangeInfo now records the change that this change was a revert of.
ChangeInfo now contains the submitter, for merged changes.
ReviewInput no longer offers the
strict_labels option. It will behave as enabled with earlier versions of Gerrit. The entire operation will now fail if any of the labels used are not within the user's permitted range based on ACLs or if the label is not configured for the project/branch.
New Java API for accessing plugins.
New Java API for accessing custom project dashboards.
getGroups method in account API to get a user's group memberships.
ChangeReportFormatter extension point for customizing the report output from
Instances of IdString used to return true when
equals was given a String instance equal to the IdString's URL-encoded value. This violates symmetry, so this behavior was removed: IdStrings now never compare equal to Strings.
It is now possible to replicate directly to another Gerrit instance.
Is is possible to enable replication to different Gerrit instance by using
gerrit+ssh:// as the protocol name followed by the hostname of another Gerrit server.
Username parameters are added to hook invocations.
When an account parameter is passed to a hook, it gets formatted as
Name (Email) or just
Name when the account does not have an email address. If the account‘s name is not set, the name is “Anonymous Coward”. From this information it is not easy for a hook to get the account’s username.
All hooks that take an account parameter now automatically also get a corresponding username parameter. For example if the hooks takes the parameter
--change-owner Name (Email) it will automatically also get the parameter
Update Apache Commons Codec to 1.10
Update Apache Commons Compress to 1.13
Update Apache Commons Validator to 1.6
Update Apache Mina SSHD to 1.6.0
Update AutoValue to 1.4.1
Update Blame Cache to 0.2-5
Update Bouncy Castle to 1.57
Update Dropwizard to 3.2.4
Update Gitiles Blame to 0.2-4
Update GWT to 2.8.1
Update Jetty to 9.3.18.v20170406
Update JGit to 184.108.40.206710071750-r
Update Joda-Time to 2.9.9
Update juniversalchardet to 2.0.0
Update Lucene to 5.5.4
Update Pegdown to 1.6.0
Update Polymer to 1.11.0
Update Soy to 2017-04-23
[elasticsearch "name"]section, with separate values
port, the servers are now configured as a list of
servervalues in the
[elasticsearch]section. This also fixes Issue 9383 where a “default” server
http://localhost:9200would be added by the site initialization even if other servers were already explicitly configured. During startup the list of configured Elasticsearch servers is logged at info level.
elasticsearch.passwordis specified, the
usernamecan be omitted and it will default to
elasticwhich is the default username configured when running Elasticsearch with security enabled.
log4j.configurationis set When the environment variable
log4j.configurationis set, log files defined by plugins were not created because the appender couldn't be found.
Change-Idin error message when
Change-Idline is not in the footer.
#), the change was created with a zero Change-Id. This was because lines beginning with
#are considered to be comments, and are stripped from the commit message by JGit before computing the Change-Id for the commit. Before attempting to create the change, Gerrit now strips out any comment lines from the commit message and returns an error if this results in the commit message being empty.
--generate-http-passwordoption to the ssh
set-accountcommand. To bring the ssh command more in-line with the REST API for a user, it is now possible to generate a new HTTP password. This allows ordinary users to generate a new HTTP password via ssh when they cannot log in to the web UI (e.g. due to being a service account). Access to the
set-accountcommand is also relaxed; normal users may use it to set a new password on their own account.
user.emailsettings were being read as-is, which would allow them to be configured with values that may interfere with standard email name/address parsing.
strict_labelsattribute was removed from the review input entity, and Gerrit no longer silently ignores invalid label scores. This caused breakage in CI systems that submit reviews post-merge and don't have different configurations for if the change is already merged or not. For example the Gerrit Trigger Plugin was broken, as discussed on the Gerrit mailing list. A new configuration
change.strictLabelsis introduced. When enabled, Gerrit will reject invalid labels, otherwise will silently ignore them. By default it is disabled, for backwards compatibility with previous releases.
reviewerin:search results when user is added as CC. The
reviewerin:search should only return users that were added as a reviewer, but was also including users that were added as CC.
http.addUserAsResponseHeader, the servlet response includes a ‘User’ header that contains the name of the logged in user, enabling reverse proxies to log the name of the user that issued the http request.
CacheImplinterface. An implementation is provided for postgresql.
submithook is invoked synchronously when a change is submitted. If it returns a non-zero exit status, a
MergeValidationExceptionis thrown and the submit is prevented. This adds back the ability to block submit by a hook which was removed in version 2.14 due to the reworking of the
commit-receivedhooks. The hooks were not singletons, which caused new instances to be created on every invocation.
elasticsearch.prefixwas not set, and Elasticsearch server-specific settings were not correctly set under
index.maxLimitfor Elasticsearch. When using Elasticsearch,
index.maxLimitshould not exceed the value of
index.max_result_windowconfigured on the Elasticsearch server.
index activatessh commands with Elasticsearch.
HEADreference failed because the passed reference name was not absolute.