Mercurial version numbering breaks dependencies

If a library is built using mercurial as the VCS, and another project has an artifact dependency on this library then the artifact copying fails with:

"Failed to copy artifacts to destination directory"

See http://intellij.net/forums/thread.jspa?threadID=276550&tstart=0

Maybe this is because the version number is number:hash? Perhaps the non numerics in the hash are a problem?

0
5 comments

That's strange it should not be related. How did you specify artifact dependency? What artifact path do you use?

--
Pavel Sher

0
Avatar
Permanently deleted user

FYI I'm using 3.1 not EAP4

The destination folder is 'lib', the dependencies are typically *.dll, *.pdb etc.

If I use , instead of {build.vcs.number.1} for the numbering in the dependency then it all works fine when the dependant project is built.

Feel free to have a look. http://build.palaso.org The dependency in question is wesay, the dependant library is called palaso.

0

Please take a look at the agent log. Are there any exceptions?

--
Pavel Sher

0
Avatar
Permanently deleted user

INFO - jetbrains.buildServer.AGENT - Artifact downloaded from "Palaso Lib :: PalasoLib: Continuous (last successful build)" saved to: C:\BuildAgent\work\4f2a5db020d4d6d7\lib\PalasoReporting.dll
INFO - jetbrains.buildServer.AGENT - Artifact downloaded from "Palaso Lib :: PalasoLib: Continuous (last successful build)" saved to: C:\BuildAgent\work\4f2a5db020d4d6d7\lib\Palaso.Tests.dll
INFO - jetbrains.buildServer.AGENT - Artifact downloaded from "Palaso Lib :: PalasoLib: Continuous (last successful build)" saved to: C:\BuildAgent\work\4f2a5db020d4d6d7\lib\PalasoUIWindowsForms.pdb
INFO - jetbrains.buildServer.AGENT - Artifact downloaded from "Palaso Lib :: PalasoLib: Continuous (last successful build)" saved to: C:\BuildAgent\work\4f2a5db020d4d6d7\lib\icuuc40.dll
INFO - jetbrains.buildServer.AGENT - Artifact downloaded from "Palaso Lib :: PalasoLib: Continuous (last successful build)" saved to: C:\BuildAgent\work\4f2a5db020d4d6d7\lib\PalasoReporting.pdb
INFO - jetbrains.buildServer.AGENT - Artifact downloaded from "Palaso Lib :: PalasoLib: Continuous (last successful build)" saved to: C:\BuildAgent\work\4f2a5db020d4d6d7\lib\PalasoUIWindowsForms.Tests.dll
WARN - jetbrains.buildServer.AGENT - Failed to copy artifacts to destination directory: lib
INFO - jetbrains.buildServer.AGENT -
jetbrains.buildServer.RunBuildException: Failed to copy artifacts
at jetbrains.buildServer.agent.impl.DependencyResolverImpl.resolve(DependencyResolverImpl.java:116)
at jetbrains.buildServer.agent.impl.BuildAgentImpl$BuildRunAction.runActualBuild(BuildAgentImpl.java:1099)
at jetbrains.buildServer.agent.impl.BuildAgentImpl$BuildRunAction.run(BuildAgentImpl.java:1044)
at java.lang.Thread.run(Thread.java:595)
INFO - jetbrains.buildServer.AGENT - Publishing artifacts 'teamcity-info.xml' to root artifacts directory
INFO - jetbrains.buildServer.AGENT - Artifacts path teamcity-info.xml not found

0

Well, it does not help much. Anyway please try the latest version of plugin. It has the following fixes:
- version does not have prefix with colon (most likely this was the cause of the error with artifact dependencies since under windows files with names with colon cannot be created)
- timeout is increased for Mercurial commands (especially for clone)

--
Pavel Sher

0

Please sign in to leave a comment.