0

I ran into an issue building the Bamboo deployment of a legacy application. The application has many version of the same DLLs, so when they are copied over as artifacts during the deployment process, they needlessly overwrite each other, adding an additional 15 minutes to deployment.

This was my original method of selecting and copying the required DLLs:

Get-ChildItem $sourcePath -Include $includedDlls -Recurse | 
Copy-Item -Destination $applicationDestinationRoot -Force
Ethilium
  • 1,224
  • 1
  • 14
  • 20

1 Answers1

1

After spending hours researching and piecing together different PS scripts, I assembled a solution:

Get-ChildItem $sourcePath -Include $includedDlls -Recurse | 
Group-Object BaseName | 
ForEach-Object {$_.Group[-1] | Copy-Item -Destination $applicationDestinationRoot -Force}

First, I had to group the files by their BaseName. Then take the grouping object of each DLL. Finally, selecting only the last FullName path of each DLL and copying that to the remote server destination.

Subsequently, if you wanted to take the first file instead of the last, simply replace $_.Group[-1] with $_.Group[0].

Edit: I've updated my answer with @Ansgar Wiechers' shorter version of the code.

Ethilium
  • 1,224
  • 1
  • 14
  • 20
  • 2
    `... | Group-Object BaseName | ForEach-Object {$_.Group[-1] | Copy-Item -Destination $applicationDestinationRoot -Force}` should suffice. – Ansgar Wiechers Aug 08 '18 at 14:01
  • This looks promising, but its throwing an error: "Copy-Item : The input object cannot be bound to any parameters for the command either because the command does not take pipeline input or the input and its properties do not match any of the parameters that take pipeline input." – Ethilium Aug 08 '18 at 14:09
  • Nevermind, I was making the error. Thanks @AnsgarWiechers! This worked and shrunk my code a bit. I've updated my answer to include your solution. – Ethilium Aug 08 '18 at 14:21