From dc56e6eed62f8bcfaf62f3f57041f26ed87c3932 Mon Sep 17 00:00:00 2001 From: Andreas Dangel Date: Sun, 18 Apr 2021 16:57:52 +0200 Subject: [PATCH] [ci] Move doc to pmd/build-tools --- .ci/README.md | 38 -------------------------------------- 1 file changed, 38 deletions(-) diff --git a/.ci/README.md b/.ci/README.md index 71b1a31d47..ef88d0ef90 100644 --- a/.ci/README.md +++ b/.ci/README.md @@ -24,44 +24,6 @@ in clear text. --armor --passphrase="GnxdjywUEPveyCD1RLiTd7t8CImnefYr" \ --output .ci/files/public-env.gpg .ci/files/public-env -## Known Issues - -### Intermittent connection resets or timeouts while downloading dependencies from maven central - -Root issue seems to be SNAT Configs in Azure, which closes long running [idle TCP connections -after 4 minutes](https://docs.microsoft.com/en-us/azure/load-balancer/troubleshoot-outbound-connection#idletimeout). - -The workaround is described in [actions/virtual-environments#1499](https://github.com/actions/virtual-environments/issues/1499) -and [WAGON-545](https://issues.apache.org/jira/browse/WAGON-545) -and [WAGON-486](https://issues.apache.org/jira/browse/WAGON-486): - -The setting `-Dmaven.wagon.httpconnectionManager.ttlSeconds=180 -Dmaven.wagon.http.retryHandler.count=3` -makes sure, that Maven doesn't try to use pooled connections that have been unused for more than 180 seconds. -These settings are placed as environment variable `MAVEN_OPTS` in the workflow, so that they are active for -all Maven executions (including builds done by regression tester). - -Alternatively, pooling could be disabled completely via `-Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false`. -This has the consequence, that for each dependency, that is being downloaded, a new https connection is -established. - -More information about configuring this can be found at [wagon-http](https://maven.apache.org/wagon/wagon-providers/wagon-http/). - -## Remote debugging - -Debugging remotely is possible with . - -Just add the following step into the job: - -``` - - name: Setup tmate session - uses: mxschmitt/action-tmate@v3 -``` - -The workflow `troubleshooting` can be started manually, which already contains the tmate action. - -**Note**: This is dangerous for push/pull builds on pmd/pmd, because these have access to the secrets and the SSH session -is not protected. Builds triggered by pull requests from forked repositories don't have access to the secrets. - ## Local tests with docker Using the same docker container as described in [build-env @ build-tools](https://github.com/pmd/build-tools).