From e65af39c36769dc61cf71735d77b6a5d4bbae370 Mon Sep 17 00:00:00 2001 From: Jenkins ConfDroid Date: Fri, 10 Sep 2021 12:41:08 +0200 Subject: [PATCH] recommit for updates in build 46 --- .scannerwork/report-task.txt | 4 ++-- doc/file.README.html | 2 +- doc/index.html | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.scannerwork/report-task.txt b/.scannerwork/report-task.txt index c0b68fc..b761a5a 100644 --- a/.scannerwork/report-task.txt +++ b/.scannerwork/report-task.txt @@ -2,5 +2,5 @@ projectKey=cd_apache serverUrl=http://sonarqube.confdroid.com serverVersion=7.9.1.27448 dashboardUrl=http://sonarqube.confdroid.com/dashboard?id=cd_apache -ceTaskId=AXvPKBFJ1C1yMMr1H4D8 -ceTaskUrl=http://sonarqube.confdroid.com/api/ce/task?id=AXvPKBFJ1C1yMMr1H4D8 +ceTaskId=AXvPS-uq1C1yMMr1H4D- +ceTaskUrl=http://sonarqube.confdroid.com/api/ce/task?id=AXvPS-uq1C1yMMr1H4D- diff --git a/doc/file.README.html b/doc/file.README.html index b696f50..5df2f3d 100644 --- a/doc/file.README.html +++ b/doc/file.README.html @@ -78,7 +78,7 @@ configurations specific to the particular use case.

**__!!! Attention: Never use this puppet module on systems which have been previously configured manually. It is impossible to predict how and -what would have been configured, hence previuos configurations outside the +what would have been configured, hence previous configurations outside the scope of this module may be overwritten! Automated configurations require a test environment to verify that the module suits the purpose intended by the user, as well as tune the parameters, before deploying into live diff --git a/doc/index.html b/doc/index.html index a97e5ef..997a86a 100644 --- a/doc/index.html +++ b/doc/index.html @@ -78,7 +78,7 @@ configurations specific to the particular use case.

**__!!! Attention: Never use this puppet module on systems which have been previously configured manually. It is impossible to predict how and -what would have been configured, hence previuos configurations outside the +what would have been configured, hence previous configurations outside the scope of this module may be overwritten! Automated configurations require a test environment to verify that the module suits the purpose intended by the user, as well as tune the parameters, before deploying into live