You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm running an old ASP.NET web site. The DLL references are copied to the BIN folder. Contrast this with most modern programming frameworks that will add a relative reference (this method works with CI builds).
To work around this problem, I need to copy the 3rd party DLL into WebSite\Bin folder prior to running MSBuilds tasks.
My thought is to run a Script task just after Source Code Checkout. The problem I have is I don't know how to locate the 3rd party DLL on the CI build server. I know the present working directory is something like:
C:\bamboo\xml-data\build-dir\JOBNAME
I need to get access to the relative source control directory:
$\fullPath\3rdPartyDLLFolder\MyThirdParty.dll
So I can do something like this in powershell:
Copy-Item -Path $\fullPath\3rdPartyDLLFolder\MyThirdParty.dll -Destination \ProjectDirectoryOnBuildServer\WebSite\Bin
I'm other to other solutions if there's a better way.
I added powershell's ls command to my Script task. Then the bamboo log files told me which directories existed because it just output verbatim. My source control path was right there in the present working directory.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.