Artifactory keeps both the actual stored file checksum and the checksum that
it receives from the client. The responses to checksum download/upload
depend on the checksum policy. You can configure Artifactory to either
return the
actual checksum or the checksum it received from the client.
Artifactory client that verify the checksums (like ivy or maven) will fail
if the checksum
doesn't match.
The behavior you described sounds completely logical (as long as the network
is to
blame for the wrong checksum).
Makes sense?
Yossi
On Tue, Oct 5, 2010 at 15:32, <[email protected]> wrote:
> Hi,
>
> we use hudson and artifactory for our builds. In one of our builds the
> upload to artifactory failed with
>
> ERROR: Failed to deploy MD5 checksum: Checksum error for
> 'de/xx-Interfaces/0.0.1-SNAPSHOT/xxx-Interfaces-0.0.1-SNAPSHOT.jar.md5':
> received '23acf72f29bf54b8a3a8c04ac8375ce7' but actual is
> 'd41d8cd98f00b204e9800998ecf8427e'
>
> java.io.IOException <http://grepcode.com/search?query=java.io.IOException>:
> Failed to deploy MD5 checksum: Checksum error for
> 'de/xx-Interfaces/0.0.1-SNAPSHOT/xx-Interfaces-0.0.1-SNAPSHOT.jar.md5':
> received '23acf72f29bf54b8a3a8c04ac8375ce7' but actual is
> 'd41d8cd98f00b204e9800998ecf8427e'
>
>
> at
> org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadChecksums(ArtifactoryBuildInfoClient.java:324)
>
> <http://grepcode.com/search/?query=org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadChecksums&entity=method>
>
>
> at
> org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:235)
>
> <http://grepcode.com/search/?query=org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact&entity=method>
>
>
> at
> org.jfrog.hudson.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:99)
> <http://grepcode.com/search/?query=org.jfrog.hudson.ArtifactsDeployer.deployArtifact&entity=method>
>
> at org.jfrog.hudson.ArtifactsDeployer.deploy(ArtifactsDeployer.java:61)
> <http://grepcode.com/search/?query=org.jfrog.hudson.ArtifactsDeployer.deploy&entity=method>
>
> at
> org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:108)
>
> <http://grepcode.com/search/?query=org.jfrog.hudson.ArtifactoryRedeployPublisher.perform&entity=method>
>
>
> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> <http://grepcode.com/search/?query=hudson.tasks.BuildStepMonitor$1.perform&entity=method>
>
> at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601)
> <http://grepcode.com/search/?query=hudson.model.AbstractBuild$AbstractRunner.perform&entity=method>
>
> at
> hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580)
>
> <http://grepcode.com/search/?query=hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps&entity=method>
>
>
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:595)
>
> <http://grepcode.com/search/?query=hudson.maven.MavenModuleSetBuild$RunnerImpl.post2&entity=method>
>
> at
> hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
> <http://grepcode.com/search/?query=hudson.model.AbstractBuild$AbstractRunner.post&entity=method>
>
> at hudson.model.Run.run(Run.java:1303)
> <http://grepcode.com/search/?query=hudson.model.Run.run&entity=method>
>
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:293)
> <http://grepcode.com/search/?query=hudson.maven.MavenModuleSetBuild.run&entity=method>
>
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> <http://grepcode.com/search/?query=hudson.model.ResourceController.execute&entity=method>
>
> at hudson.model.Executor.run(Executor.java:137)
> <http://grepcode.com/search/?query=hudson.model.Executor.run&entity=method>
>
> this might be happen sometimes, the problem then was that successive builds
> fail because they could not find this artifact in artifactory.
>
> I'm wondering... why ? If I browse Artifactory with the browser I do see
> the artifact. After running the failed project again and a successful
> deployment, the successive projects also work.
>
> is this just a bad coincidence or what is going wrong ?
>
> Thanks
>
>
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
> Spend less time writing and rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
