Hello

Yoav Landman <[email protected]> wrote on 19.04.2011 20:51:45:

> Which version of Artifactory are you using? (1.2.3 doesn't make sense).
> Is there any error in the Artifactory log when you deployment is
rejected?
> Did you try with the latest Artifactory release? (2.3.2 at the time
> of writing)

Oh sorry, that's a typo on my first posting. The installed version as the
error appears was 2.2.3. We updated this installation to the current
version 2.3.2 and the error still exists.

But possibly we found a solution. The virtual machine with Jenkins and the
virtual machine with Artifactory are located on the same ESXi host but the
Artifactory-VM was accessed using the hostname. Because of this the traffic
leaves the Jenkins-VM and ESXi host and came back to the Artifactory-VM.
Now we configured the artifactory plugin to use the real IP of the
Artifactory-VM instead the hostname, which solves the problem. The error
417 never appears again after this change.

So it may be a problem if Artifactory access out of the jenkins plugin is
done using hostname on such a hardware setup?


> After upgrading jenkins from 1.403 to 1.406 we run into problems with the
> deploy step to our local artifactory installation using the artifactory
> plugin. The plugin was updated from 1.4.2 to 1.4.3. Every job which
deploys
> to artifactory fails with the following message:
>
> Deploying artifacts to http://ho-buildres.hombi.ascom.ch:8081/artifactory
> Deploying artifacts of module: com.ascom.ecs3.buildconfiguration:ECS3
> Deploying artifact:
> http://ho-buildres.hombi.ascom.ch:8081/artifactory/r-2.1.x/com/
> ascom/ecs3/buildconfiguration/ECS3/2.1.0-SNAPSHOT/ECS3-2.1.0-SNAPSHOT.pom
>
> ERROR: Failed to deploy file: HTTP response code: 417. HTTP response
> message: Expectation failed
> java.io.IOException: Failed to deploy file: HTTP response code: 417. HTTP
> response message: Expectation failed
>             at
> org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException
> (ArtifactoryBuildInfoClient.java:468)
>             at
> org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile
> (ArtifactoryBuildInfoClient.java:388)
>             at
> org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact
> (ArtifactoryBuildInfoClient.java:287)
>             at org.jfrog.hudson.maven2.ArtifactsDeployer.deployArtifact
> (ArtifactsDeployer.java:138)
>             at org.jfrog.hudson.maven2.ArtifactsDeployer.deploy
> (ArtifactsDeployer.java:92)
>             at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform
> (ArtifactoryRedeployPublisher.java:252)
>             at hudson.tasks.BuildStepMonitor$1.perform
> (BuildStepMonitor.java:19)
>             at hudson.model.AbstractBuild$AbstractRunner.perform
> (AbstractBuild.java:644)
>             at hudson.model.AbstractBuild
> $AbstractRunner.performAllBuildSteps(AbstractBuild.java:623)
>             at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2
> (MavenModuleSetBuild.java:818)
>             at hudson.model.AbstractBuild$AbstractRunner.post
> (AbstractBuild.java:570)
>             at hudson.model.Run.run(Run.java:1386)
>             at hudson.maven.MavenModuleSetBuild.run
> (MavenModuleSetBuild.java:440)
>             at hudson.model.ResourceController.execute
> (ResourceController.java:88)
>             at hudson.model.Executor.run(Executor.java:145)
> Email was triggered for: Failure
>
>
> In the next step I updated our Artifactory installation from 1.2.3 to
1.3.2
> but nothing changes. Even the downgrade of Jenkins to 1.403 don't help,
the
> error still happens. So I'm running completely out of ideas. The error
4xx
> is a server error but on Artifactory I can't find any hint on the logs.
So
> what should I check/modify/fix now?


Kind regards,

Yves Schumann
R&D IT-Koordinator
Security Communication
______________________________
Ascom (Schweiz) AG


------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply via email to