You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you are behind a corporate proxy, DSpot amplification, triggered by python publisher.py -d /queue/Dpipeline pipelineid, fails because it can't download dependencies from Maven repositories, so it is needed to pass proxy configuration in some way.
Steps to reproduce
Having setup everything according to PR #840, the execution ends with following error stacktrace:
...
Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/maven-release-plugin-2.5.3.pom
[WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-release-plugin:2.5.3: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-release-plugin:jar:2.5.3
Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
[WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.240.215] failed: Connection refused (Connection refused)
[WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.240.215] failed: Connection refused (Connection refused)
[WARNING] Failure to transfer org.apache.maven.plugins/maven-metadata.xml from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.240.215] failed: Connection refused (Connection refused)
[WARNING] Failure to transfer org.codehaus.mojo/maven-metadata.xml from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.240.215] failed: Connection refused (Connection refused)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.726 s
[INFO] Finished at: 2019-09-16T15:34:59Z
[INFO] ------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'dspot' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/root/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
WARNING:root:Nothing will be submit since mongodb is not connected
cp: cannot stat 'target/dspot/output': No such file or directory
WARNING:root:PIPELINE MESSAGE: DONE , AWAITING FOR NEW BUILD ID
The text was updated successfully, but these errors were encountered:
Characteristics
Description
When you are behind a corporate proxy, DSpot amplification, triggered by
python publisher.py -d /queue/Dpipeline
pipelineid
, fails because it can't download dependencies from Maven repositories, so it is needed to pass proxy configuration in some way.Steps to reproduce
Having setup everything according to PR #840, the execution ends with following error stacktrace:
The text was updated successfully, but these errors were encountered: