Artifacts

Answered

In packaging i need to copy same binaries to different destination in artifacts

In below example it create artifacts for only for Link2 and not for Link1.

eg:

Source/abc/Comm/bin/release/ => package.%system.Build_Number%.zip!/Link1
Source/abc/Comm/bin/release/ => package.%system.Build_Number%.zip!/Link2

I need to have same binaries in Link1 and Link2.

Any one Can help me on this.

0
3 comments

As you can see in the following link, this is a known limitation. Please click watch and vote to stay informed when it gets updated.

https://youtrack.jetbrains.com/issue/TW-44880

In the meantime, you can push the artifacts to different destination files/folders, instead of different folders within the same file. You have later the option to use the "Download all" link to download all the artifacts as a packaged zip. You can also make your own packaging through a build step with a command line script.

0
Avatar
Permanently deleted user

In packaging i'm able to create same binaries to different destination in artifacts

In below example it create artifacts for Link1 and Link2.

eg:CMD1

Source/abc/Comm/bin/release/ => package.%system.Build_Number%/Link1
Source/abc/Comm/bin/release/ => package.%system.Build_Number%/Link2

 If i use below command it create artifacts for only Link2 and not for Link1

eg:CMD2

Source/abc/Comm/bin/release/ => package.%system.Build_Number%.zip!/Link1
Source/abc/Comm/bin/release/ => package.%system.Build_Number%.zip!/Link2

The only difference between CMD1 and CMD2 is .zip!

Any one Can help me on this.

0

As I already mentioned, this is a known bug. Please refer to the link in my previous answer for the bugtracker.


There are several workarounds:


-Create your own packaging in a new build step.


-Publish them as 2 separate folders and use the "Download all" button in the Web UI


-Publish the artifacts normally, then create a new build configuration that depends on the artifacts and makes them available through 2 folders, then pushes the 2 folders into the same zip file:
First build config would do:
Source/abc/Comm/bin/release/ => artifacts


Second build config would depend on "artifacts", post them twice to a local copy such as:


artifacts => Link1
artifacts => Link2


Then the build config publishes the artifacts this way:


Link1 => package.%system.Build_Number%.zip!/Link1
Link2 => package.%system.Build_Number%.zip!/Link2


Because the origins are different, this will be properly placed inside the zip separately.

0

Please sign in to leave a comment.