Maven2 build cannot find artifacts from Artifactory repository

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Maven2 build cannot find artifacts from Artifactory repository

Ed Hillmann-2
Hi all.  I've just started out using Hudson in the following environment:

Maven 2.0.9
A local Artifactory server to cache artifacts

I'm trying to run a Project that, for a given Maven 2 project, runs
site:site and site:deploy.  I've scheduled the build to start
overnight (3am) and it fails with the following output

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] The skin does not exist: Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
-Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
    mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]


  org.apache.maven.skins:maven-default-skin:jar:RELEASE



This is new, as it has always worked from my command prompt.
Throughout the console, any attempt to retrieve updates from the
Artifactory server fails...

[INFO] org.apache.maven.plugins: checking for updates from deli.plugins.releases
[WARNING] repository metadata for: 'org.apache.maven.plugins' could
not be retrieved from repository: deli.plugins.releases due to an
error: GET request of: org/apache/maven/plugins/maven-metadata.xml
from artifactory failed
[INFO] Repository 'deli.plugins.releases' will be blacklisted

So the site generation is failing because it can't find the skins
because the check for updates failed.  The build also fails if I kick
off the build manually via the website.

Now, if I go out to my command prompt and execute the same thing,
everything works fine.  Checks for updates complete without errors
(there are no updates).  The users (me, and the Hudson account) have
the same artifactory permissions.

To cap it off, once I've built it manually, I can jump back into
Hudson, start the same build that was failing, and it will complete
successfully.  Until the next day, when the whole issue repeats.

I don't know what the cause is.  Is there any way I can enable logging
in order to see why the Hudson build fails every 24 hours?

Thanks for any help,
Ed

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Maven2 build cannot find artifacts from Artifactory repository

Kohsuke Kawaguchi
Administrator
I guess the root cause is that Maven is somehow failing to get the
file, so I'd try the maven -X option.

You can list '-X' along with the goals you list in Hudson configuration.

2008/5/22 Ed Hillmann <[hidden email]>:

> Hi all.  I've just started out using Hudson in the following environment:
>
> Maven 2.0.9
> A local Artifactory server to cache artifacts
>
> I'm trying to run a Project that, for a given Maven 2 project, runs
> site:site and site:deploy.  I've scheduled the build to start
> overnight (3am) and it fails with the following output
>
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] The skin does not exist: Unable to determine the release version
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
>    mvn install:install-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file there:
>    mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
>  org.apache.maven.skins:maven-default-skin:jar:RELEASE
>
>
>
> This is new, as it has always worked from my command prompt.
> Throughout the console, any attempt to retrieve updates from the
> Artifactory server fails...
>
> [INFO] org.apache.maven.plugins: checking for updates from deli.plugins.releases
> [WARNING] repository metadata for: 'org.apache.maven.plugins' could
> not be retrieved from repository: deli.plugins.releases due to an
> error: GET request of: org/apache/maven/plugins/maven-metadata.xml
> from artifactory failed
> [INFO] Repository 'deli.plugins.releases' will be blacklisted
>
> So the site generation is failing because it can't find the skins
> because the check for updates failed.  The build also fails if I kick
> off the build manually via the website.
>
> Now, if I go out to my command prompt and execute the same thing,
> everything works fine.  Checks for updates complete without errors
> (there are no updates).  The users (me, and the Hudson account) have
> the same artifactory permissions.
>
> To cap it off, once I've built it manually, I can jump back into
> Hudson, start the same build that was failing, and it will complete
> successfully.  Until the next day, when the whole issue repeats.
>
> I don't know what the cause is.  Is there any way I can enable logging
> in order to see why the Hudson build fails every 24 hours?
>
> Thanks for any help,
> Ed
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>



--
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Maven2 build cannot find artifacts from Artifactory repository

Ed Hillmann-2
On Fri, May 23, 2008 at 3:38 PM, Kohsuke Kawaguchi <[hidden email]> wrote:
> I guess the root cause is that Maven is somehow failing to get the
> file, so I'd try the maven -X option.
>
> You can list '-X' along with the goals you list in Hudson configuration.
>
Thanks for the help.  After displaying the debug for the Maven
process, it showed that the account hosting the Hudson application was
using an incorrect Maven local repository.  Once I configured the
Maven file settings.xml file correctly, it worked fine.  So, the error
was not Hudson's, it was my maven setup.

Thanks again for the help!

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]