You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Arnout Engelen (Jira)" <ji...@apache.org> on 2025/02/28 09:01:00 UTC

[jira] [Created] (COMMONSSITE-176) commons-release-plugin should perhaps not connect to dist.apache.org during tests

Arnout Engelen created COMMONSSITE-176:
------------------------------------------

             Summary: commons-release-plugin should perhaps not connect to dist.apache.org during tests
                 Key: COMMONSSITE-176
                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-176
             Project: Apache Commons All
          Issue Type: Improvement
            Reporter: Arnout Engelen


We encountered the following error in a PR to commons-release-plugin:

Failure is:
Error:  Errors: 
Error:    CommonsDistributionStagingMojoTest.testSuccess:140 » MojoExecution Failed to checkout files from SCM: The svn command failed. [svn: E170013: Unable to connect to a repository at URL 'https://dist.apache.org/repos/dist/dev/commons/release-plugin'
svn: E000110: Error running context: Connection timed out
]{{}}
I suspect this is due to the GitHub actions runner being blocked from ASF resources (INFRA-26405). In parallel to eventually lifting those blocks, we could consider if {{CommonsStagingCleanupMojoTest.testCompressSiteSuccess}} really needs to connect to dist.apache.org when running regular unit tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)