Fails to copy artifacts if you change the Build Number Format.

hi

I'm using team city 3.1.1
I'm not sure if this is a known bug, but....

I have a build that produces artifacts for another configuration. If i change the Build number format on the configuration that produces the artifacts (Say from to (6.1.0.{build.vcs.number.1}) The configuration with the artifact dependecy fails with the following error

: Failed to copy artifacts to destination directory: UI/Trunk/Bin/Release/
: Failed to copy artifacts

It only happens when i change the build number format.

Is there a work around other than not changing the default setting of the build number format??

Cheers

Alan

2 comments

Hello Alan,

Try dropping the space from the build number pattern. Our build numbers go
like this: 1.10-b http://jetbrains.net/tracker/issue/TW-4758 HTH, Andrei A> hi A> A> I'm using team city 3.1.1 I'm not sure if this is a known bug, A> but.... A> A> I have a build that produces artifacts for another configuration. If A> i change the Build number format on the configuration that produces A> the artifacts (Say from to (6.1.0.{build.vcs.number.1}) The
A> configuration with the artifact dependecy fails with the following
A> error
A>
A> : Failed to copy artifacts to destination directory:
A> UI/Trunk/Bin/Release/ : Failed to copy artifacts
A>
A> It only happens when i change the build number format.
A>
A> Is there a work around other than not changing the default setting of
A> the build number format??
A>
A> Cheers
A>
A> Alan
A>


0

yep.

Nice one, thanks for that.

Alan

0

Please sign in to leave a comment.