How do I call Custom NuGet packages with restore in Bamboo

[Sean_Edler]

We are migrating a new project over to Bamboo and the Atlassian sweet + Octopus Deploy and currently when running the Build on Bamboo we get halted on the Command step to Call Nuget "Restore".
Our Nuget.Exe is mapped to the correct Build Server

the Argument is simply: restore "${bamboo.SolutionName}.sln"

We have also tried: restore "${bamboo.SolutionName}.sln" -source "\\TargetShare\Nuget\PP"

and
restore "${bamboo.SolutionName}.sln" -source "https://api.nuget.org/v3/index.json;\\TargetShare\Nuget\PP"

The error we get is: 

25-Jul-2019 16:08:50	Unable to find version '1.0.0' of package 'Custom.WebServices'.
25-Jul-2019 16:08:50	Unable to find version '2.17.1' of package 'SpireNuget'.
25-Jul-2019 16:08:50	Unable to find version '1.1.0' of package 'Radian.Integration.ClearCapital'.
25-Jul-2019 16:08:50	Unable to find version '1.0.0' of package 'Custom.Extensions'.
25-Jul-2019 16:08:50	Unable to find version '1.0.0' of package 'CustomGoogleMaps'.
25-Jul-2019 16:08:50	Unable to find version '1.0.2' of package 'CustomGoogleMaps'.

These are the names of the Custom packages that are created but currently hosted on a different Server.

Is it best to move these custom packages to the Build server and create a share so they can be updated as needed by the Dev/Build team? Or is it best to somehow make calls to the current server they are using for this already? 

If its best to make the calls, how do you set that up? 

if I put the share on the Build Server, how would one make calls to that, or is that even needed? 

Thanks in advance for anyone's assistance,

Sean

[Jimmy Seddon]

Hi @Sean_Edler ,

First, I love your profile pic!

We have custom nuget packages as well, and what we have done is to provide a nuget.config file and inside of that we list package sources that allows us to reference the nuget server we setup internally for our development to push and pull versions of our internally build nuget packages.

You can find more documentation on how the NuGet config files work here:

https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file

I hope that helps!

-Jimmy

[Sean_Edler]

Thanks Jimmy! I wanted FF7 when it came out so bad, I sold my SNES & Every game I owned to .... some type of game stop type store and had just enough for a Play station and FF7... Glad the game turned out awesome for me.

I am getting the config file from our developer and am going to open it up and look through it to see if I can see where any changes might be needed. I will keep you updated, thanks for the link and the help. 

[Sean_Edler]

This is still semi new to me as mostly our Developers have set this up in the past but this is in my lap now.

I have tried editting some files(Nuget.Config)

Right now that file only disables Source Control Integration

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<solution>
<add key="disableSourceControlIntegration" value="true" />
</solution>
</configuration>

I did try to add in Package Sources

<packageSources> <add key="NuGet official package source" value="https://api.nuget.org/v3/index.json" /> <add key="MyRepo - ES" value="https://MyRepo/ES/nuget" /> </packageSources>

Using this template and switching the variables to mine, but I got invalid Config file. What format would it have to be on?

Our Custom Nuget packages are located on a Share that is hosted on a separate Server

Thanks,

~Sean

[Jimmy Seddon]

Hey Sean,

No problem we all had to start somewhere.

Provided that when you added the package sources you put them ahead of the closing </configuration> tag.  That should be fine (that is exacly how mine is setup).

It only other thing to check would be to open the NuGet.Config file in a text editor that displays hidden control characters (like Notepadd++) to make sure you don't have any hidden invalid characters.

-Jimmy