This util script can be used in case of rollback to ReviewDB during an unsuccessful
migration to NoteDB or simply while testing the migration process.
It will remove all the refs used by NoteDB added during the migration
(i.e.: change meta refs and sequence ref).
Change-Id: Ibe0317bc848795d7e0ba3e39284496404d6f0688
* stable-2.15:
Format BUILD files with buildifier
Format BUILD files with buildifier
junit.bzl: Fix name conventions warning flagged by buldifier
Bazel: Avoid using tools in action inputs
dev-contributing: Update recommended version of buildifier to 0.28.0
Change-Id: I20579e30a97b640d23df38e2bf129fea0003c548
* stable-2.14:
Format BUILD files with buildifier
junit.bzl: Fix name conventions warning flagged by buldifier
Bazel: Avoid using tools in action inputs
dev-contributing: Update recommended version of buildifier to 0.28.0
Change-Id: I7351d4c21d53255992170f750b6ef9e61d1d1716
Running recent buildifier version in warn mode reports this warning:
./tools/bzl/junit.bzl:60: name-conventions: Variable name "_GenSuite"
should be lower_snake_case (for variables), UPPER_SNAKE_CASE (for
constants), or UpperCamelCase ending with 'Info' (for providers).
https://github.com/bazelbuild/buildtools/blob/master/WARNINGS.md#name-convention
Change-Id: I2fd8490e95a1b103a9ece9c68f2d09c5e4f3fbb0
Bazel version 0.29 flipped the bit for this option:
--incompatible_no_support_tools_in_action_inputs to ensure, that tools
are not used in input, but instead passed as new parameter tools: [1].
Change I744ae1b28a already fixed some places, but missed the place
fixed in this change. The problem shows up when debugging of GWT code
with Bazel 0.27 and later.
Test Plan:
$ bazel build //gerrit-gwtui:ui_safari
[1] https://github.com/bazelbuild/bazel/issues/5826
Change-Id: I491d70361444e4fb41a1dc2b7dbe422969c090ff
Fix the NoteDb migration progress by converting its binary output
into printable characters that can be easily understood by humans.
Bug: Issue 11444
Change-Id: I6c2c6f036d8e5402ce72b7cdd53a4677b0f54521
Improvements in 5.1.8 - 5.1.11:
- include filekey file attribute (inode on *nix filesystems) when
comparing FileSnapshots
- optionally wait opening new packfile until it can't be racy anymore
- fix FileSnapshot's consideration of file size
- ObjectDirectory: fix closing of obsolete packs
- measure FileStoreAttributes per filesystem
- improve measuring file timestamp resolution
- measure minimal racy interval
- use Instant to increase resolution to 1us (limited by FileTime)
- persist FileStoreAttributes
- optional asynchronous measurement of FileStoreAttributes
- directory - FileStore cache
- cache user and system level gitconfig
- fix supportsAtomicCreateNewFile default to true
- fix non-deterministic hash of archives created by ArchiveCommand
- reproduce racy atomic update in PackedBatchRefUpdate and fix it
Release notes:
https://projects.eclipse.org/projects/technology.jgit/releases/5.1.8https://projects.eclipse.org/projects/technology.jgit/releases/5.1.9https://projects.eclipse.org/projects/technology.jgit/releases/5.1.10https://projects.eclipse.org/projects/technology.jgit/releases/5.1.11
Change-Id: Ia93eaee442096eabdb999c9c9a6fc0edeb10c0fe
Running buildifier at the head of master with -lint=warn shows
the warning:
native-proto: Function "proto_library" is not global anymore and
needs to be loaded from "@rules_proto//proto:defs.bzl"
Add rules_proto in the WORKSPACE and use it in the proto BUILD.
Change-Id: I54363f08cab3a184b6b3cd1ff6baaa38824aa9a3
* stable-2.15:
Bazel: Add fixes for --incompatible_load_{java|python}_rules_from_bzl
Bazel: Bump minimum supported version to 0.29.0
Lucene index configuration and docs.
Change-Id: I6c597cbc89fafece83c374e9b36c4c4c0126704f
* Update plugins/replication from branch 'stable-2.16'
to 60f470c96232d44c5fd83c75ac99174b356adcf5
- Persist replication task when pushing all refs
Create a replication event associated with the replication of all
refs, so that the completion of the operation would find a corresponding
task and will not throw an exception.
Another benefit also is the ability to replay pending replication
events for a push of all refs upon plugin restarts and configuration
reloads.
Bug: Issue 11424
Change-Id: I63a82ff128c98e0ab7e58b76fa8f8548eb74e915
* stable-2.14:
Bazel: Add fixes for --incompatible_load_{java|python}_rules_from_bzl
Bazel: Bump minimum supported version to 0.29.0
Lucene index configuration and docs.
Change-Id: I0a8c17c853746ca7367cc4b723b18f8d0f2b6094
This change is fixing "All Java build rules should be loaded from
Starlark" warning flagged by latest buildifier version: [1]. Python
rules are now also loaded from the Starlark.
Also extract codemirror library import to BUILD file. This is needed to
avoid cycle in the workspace file, after importing java rules from
Starlark.
[1] https://github.com/bazelbuild/buildtools/blob/master/WARNINGS.md#native-java
Change-Id: I36192c9465d988b25cf09c250e110f15850910cd
In I4b5a32a15d WCT tests invocation was switched from bazel to
bazelisk, but bazelisk location command was wrong. stderr and
stdout was erroneously redirected to the /dev/null, so that the
actual location of the bazelisk command was lost. Fix the location
detection command by redirecting only stderr but not stdout to the
null device.
Change-Id: I66cb33e0074675e00b0e58bb11413b5151a57533
After flipping of
--incompatible_disallow_load_labels_to_cross_package_boundaries bit in
Bazel: [1], currently documented way to import external dependencies
from plugins that implement standalone build mode doesn't work any more.
This change documents an alternative approach how to make it work,
without abandoning of standalone build mode.
[1] https://github.com/bazelbuild/bazel/issues/6408
Bug: Issue 10885
Change-Id: I7b1c4e9fa4f6ba8966efcde4cdee7d76d6f59d1c
* Update plugins/replication from branch 'stable-2.16'
to bfc9e0f05d1da46118723d846e9e450455d89b74
- ReplicationIT: fix flakiness
Fix the flakiness when checking for replication tasks stored
events on the filesystem and when replicating new projects.
Make use of the ReplicationTasksStorage for listing events
instead of listing the filesystem and allow disabling the deletion
so that the tests can have the time to verify the files existence.
Change-Id: Idfba7d177faed3c3ff45507b6f5b6aadb0bc5dd0
Reindexing performance in gerrit is very slow when running on larger
multicore servers.
When you have multiple index threads putting content into LUCENE index,
it falls behind and starts to throttle the content being merged.
Updated to allow us to configure and override the default AutoDetected
configuration of the Lucene index queue and the threads it uses to
merge (add/update) data into the index.
The auto detection in the Lucene index by default does the following:
1) It throttles the index writing to less than 20Mb/s.
2) On storage arrays it detects them as being slow spinning rust, and not
as faster SSD type systems. This in turn limits the lucene merge to only
1 thread and a limited queue size of 6.
These settings allow the control of each of the auto detected settings
and adjustment to suit your own server and storage performance.
Bug: Issue 11356
Change-Id: Ie1be338f5a31f5ad572d9fdec19775b2dd09aa5f
If bazelisk is installed, this bazel wrapper should be used to pick
the right bazel version specified in the .bazelversion file.
Change-Id: I4b5a32a15d190fd5733866dc18bbb1ed27a37f18
* Update plugins/replication from branch 'stable-2.16'
to a1b83633a72c46a9ad641342fc7fe1e30631fafb
- ReplicationIT: reduce execution time
Change-Id: I259aa073ae16234d2aaa556012cfa2f584aca748
* Update plugins/replication from branch 'stable-2.16'
to 53af4e7839eb4b386584446ff8c4a53a0b706180
- ReplicationIT: Split waitUntil to a separate class and fix it
The waitUntil method does not fail the test if the expected condition
is not satisfied within the timeout; it just returns.
Split it out to a separate class, to make it easier to test, fix
it, and add tests.
Change-Id: I6cbd6801bcfd07869dd56d3ab6b54c5ac7c8a691
* Update plugins/replication from branch 'stable-2.16'
to eef56952d3f5b05923ebcd07fdc1741a6bf9cc0e
- ReplicationIT: Fix typo in constant name
Change-Id: I349fc79f2b78d1d0bee23b516e37c29705f58a08
Since change Ie5c658488 it is no longer possible to disable the
PolyGerrit UI. The default UI is PolyGerrit, but can be switched
to GWT by a configuration setting. The documentation was not
updated and still claims that the PolyGerrit UI can be disabled.
Update the documentation to reflect reality.
Change-Id: I98ecbdfa8023f0e439f3f5d5e3613d02a6d0dfcd
* stable-2.15:
Set version to 2.15.17-SNAPSHOT
Set version to 2.15.16
Revert "CreateAccount: Fail early when invalid SSH key is given"
tools/eclipse/project.py: Fix typo of bazelisk
Migrate from old-style legacy .java provider to the new JavaInfo.
Support bazelisk or bazel in tools/eclipse/project.py
Rework imports in project.py
Update project.py to use argparse
Change-Id: If9388140c516f8ff2f5275eefe6cf65dad42449e
This reverts commit bd68b579e87736977df26bb6ef6a1649b635577f.
Reason for revert: Not needed after JGit update was reverted.
Change-Id: I6a27c05e7078d6874db66e1c0919622748e5bf75