This issue was reported some time ago (
http://issues.hudson-ci.org/browse/HUDSON-6899).
I'll look into it. If there's no other elegant way to solve it, we'll skip
the plugin if the build cause
is the release plugin.
And regarding the credential, the next version will support default
credentials (http://issues.jfrog.org/jira/browse/HAP-76).
Regards,
Yossi
On Wed, Sep 29, 2010 at 09:52, <[email protected]> wrote:
> Hi all,
>
> I use the artifactory plugin in hudson and have it enabled for my jobs
>
> I also use the maven release plugin in hudson to deploy releases.
>
> Unfortunately those two collidate when performing a release.
>
> The release is done, but at the end the build fails with
>
> Deploying artifact: http://build-server
> /artifactory/plugins-snapshots/de/test
> /plugins/maven-consumer-plugin/0.2-SNAPSHOT/maven-consumer-plugin-0.2-SNAPSHOT.pom<http://build01-whm.ibfs.de:8090/artifactory/gis-fw-plugins-snapshots/de/gis-fw/plugins/maven-consumer-plugin/0.2-SNAPSHOT/maven-consumer-plugin-0.2-SNAPSHOT.pom>
> ERROR: Failed to deploy file: The target deployment path
> 'de/test/plugins/maven-consumer-plugin/0.2-SNAPSHOT/maven-consumer-plugin-0.2-SNAPSHOT.pom'
> does not match the POM's expected path prefix
> 'de/gis-fw/plugins/maven-consumer-plugin/0.3-SNAPSHOT'. Please verify your
> POM content for correctness and make sure the source path is a valid Maven 2
> repository root path.
> java.io.IOException <http://grepcode.com/search?query=java.io.IOException>:
> Failed to deploy file: The target deployment path
> 'de/test/plugins/maven-consumer-plugin/0.2-SNAPSHOT/maven-consumer-plugin-0.2-SNAPSHOT.pom'
> does not match the POM's expected path prefix
> 'de/gis-fw/plugins/maven-consumer-plugin/0.3-SNAPSHOT'. Please verify your
> POM content for correctness and make sure the source path is a valid Maven 2
> repository root path.
> at
> org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:310)<http://grepcode.com/search/?query=org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile&entity=method>
> at
> org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:234)<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>
>
> I can solve this problem by unchecking the "Deploy artifacts to
> Artifactory" option for the job before I ran the release. But when I check
> it after the release again it lost the credentials.
>
> This is not a big issue, but is there a way to omit the deploying to
> Artifactory when doing a maven release in hudson ? Or any other switch I can
> use to avoid the deployment ?
>
> or any other ideas ;-)
>
> Thanks
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
