We have moved our Jenkins system to an isolated part of our network. I can use a proxy to get plugins and keep them up to date, but I didn't find such a mechanism for the rest of Jenkins.
We are using Maven to deploy our build artifacts to our Maven repository. While attempting to do this, I got the following error: Legacy code started this job. No cause information is available Building in workspace /opt/tomcat/jenkins_home/jobs/keymanagement-safenet/workspace Promoting keymanagement-safenet #5 Marking build to keep forever. build hudson.plugins.promoted_builds.KeepBuildForeverAction@2f229b73 SUCCESS [workspace] $ /bin/sh -xe /opt/tomcat/apache-tomcat-7.0.27/temp/hudson5814028733721634406.sh + FILE_LOC=/mnt/jenkins/builds/keymanagement-safenet/5/archive/targets/archive + mvn deploy:deploy-file -Dversion=2.0.0 -Dfile=/mnt/jenkins/builds/keymanagement-safenet/5/archive/targets/archive/crypto.jar -DpomFile=/mnt/jenkins/builds/keymanagement-safenet/5/archive/targets/archive/pom.xml -Durl=http://admin:password@localhost:8081/artifactory/ext-release-local [INFO] Scanning for projects... Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-clean-plugin:2.4.1: Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1 Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom Yadda...Yadda...Yadda The main Maven repository is not visible to our system, so it can't download the required Maven plugins. I need to tell Jenkins to use a proxy to fetch these file but, I haven't seen anything in Jenkins to allow the use of a proxy in this situation. Is there a way to configure a proxy? Maybe using Tomcat? -- David Weintraub [email protected]
