There are reoccurring reports from the last couple of days about connection problems with repo1, here and on other lists. In your case Maven probably reaches out to look for metadata about the available versions of the pmd plugin, so the simplest solution would be to lock down the version of the plugins used in your project (which is also a good practice for maintaining reproducible builds).
You may also try to increase the network timeouts in the advance configuration of the repo1 repository. However, in some cases I saw that the connection phase may randomly take an unacceptable amount of time (>60 secs). On Fri, May 7, 2010 at 8:56 PM, David Biesack <[email protected]> wrote: > > We have CruiseControl performing builds via Maven (mvn -U ...), > Most of the time, builds work fine. However, from time to time (several > times a day), a build will fail > > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] The plugin 'org.apache.maven.plugins:maven-pmd-plugin' does not > exist > or no valid version could be found > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-pmd-plugin' does not exist or no valid > version could be found > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(DefaultLifecycleExecutor.java:1651) > .... > > when this happens, the entire build fails, and CruiseControl sends > developers email, > so they must take time to investigate this. Often, this clears up the next > time > CruiseControl tries to build the project automatically a couple minutes > later. > > (This plugin does exist in our artifactory in the repo1-cache; for example > > http://aclmvn.unx.sas.com/artifactory/repo/org/apache/maven/plugins/maven-pmd-plugin/2.5/ > shows > both the jar and pom.) > > I assume this failure is because of an update check from Central, which may > be timing out. > Can anyone confirm this? More importantly, is there a way to resolve or > prevent > or workaround this, either through Artifactory (i.e. adding a timeout/retry > strategy; > or letting it fall back on the cache if an update check times out) or > elsewhere (i.e. Maven). > > I thought about putting a wrapper around Maven so that if it gets such a > failure, it will > sleep for a short time, then try again (not no more than a few times) > instead of always > failing the first time, but that would be much more expensive (time, > compute > resources) than > a repository fix. > > Has anyone implemented such a workaround? > > ----- > > configuration details: > > > where Maven is configured with Artifactory 2.2.2 on our local server. Maven > is configured using the settings.xml traight out of Artifactory > (http://aclmvn.unx.sas.com/artifactory/webapp/mavensettings.html), > including > mirror: > > <mirrors> > <mirror> > <mirrorOf>*</mirrorOf> > <name>repo</name> > <url>http://aclmvn.unx.sas.com/artifactory/repo</url> > <id>repo</id> > </mirror> > </mirrors> > > as well as (abbreviated): > > <url>http://aclmvn.unx.sas.com/artifactory/libs-releases</url> > <url>http://aclmvn.unx.sas.com/artifactory/libs-snapshots</url> > <url>http://aclmvn.unx.sas.com/artifactory/plugins-releases</url> > <url>http://aclmvn.unx.sas.com/artifactory/plugins-snapshots</url> > > -- > View this message in context: > http://forums.jfrog.org/intermittent-plugin-failures-tp5020586p5020586.html > Sent from the Artifactory - Users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users >
------------------------------------------------------------------------------
_______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
