This is an automated email from the ASF dual-hosted git repository.
adoroszlai pushed a change to branch HDDS-13541
in repository https://gitbox.apache.org/repos/asf/ozone.git
discard dbf1e73c257 also set sonar.ws.timeout
discard b0e3e7edb3f increase report submit timeout
discard 1e20e48ef15 increase sonar timeouts
discard 4fae9c3c284 HDDS-13541. Bump sonar-maven-plugin to 5.1.0.4751
add 9664324d23e HDDS-13522. Rename axisLabel for No. of delete request
received (#8879)
new 2c2290b40e8 HDDS-13541. Bump sonar-maven-plugin to 5.1.0.4751
new 1ea5d259967 set SonarQube properties in pom.xml
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (dbf1e73c257)
\
N -- N -- N refs/heads/HDDS-13541 (1ea5d259967)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
hadoop-ozone/dev-support/checks/sonar.sh | 8 ++------
.../common/grafana/dashboards/Ozone - DeleteKey Metrics.json | 4 ++--
.../grafana/dashboards/Ozone - DeleteKeyProgress Metrics.json | 4 ++--
pom.xml | 9 +++------
4 files changed, 9 insertions(+), 16 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
