Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Unable to find version of package



  • We have deployed a new version of one of our nuget packages to our private proget server (latest version). The build works fine from within Visual Studio 2013. Our solution's nuget.config file has been updated with our private package source. All other packages are found and downloaded properly.

    When we attempt to run the build from BuildMaster (v. 4.9.7) we receive the following error:

    C:\BuildMaster_SVCTMP_A14\Src.nuget\NuGet.targets(92,9): error : Unable to find version '1.3.1.0' of package 'AdvantageIndustries.AIAuth'.
    C:\BuildMaster_SVCTMP_A14\Src.nuget\NuGet.targets(92,9): error MSB3073: The command ""...nuget\NuGet.exe" install "C:\BuildMaster_SVCTMP_A14\Src\BLIS.Web\packages.config" -source "" -NonInteractive -RequireConsent -solutionDir "..\ "" exited with code 1.
    Done building project "BLIS.Web.vbproj" -- FAILED.
    Build failed (msbuild returned 1).

    The package is available on the Proget website feed and can be installed/upgraded without issue using Visual Studio's Package Manager Console.

    Any suggestions you have would be greatly appreciated.

    Thanks,
    Philip

    Product: BuildMaster
    Version: 4.9.7



  • It's hard to say what the issue is, but most likely it's related to the package sources not being set. There are multiple places to configure private sources for nuget.exe, so it's likely it's not configured properly on the BuildMaster server...

    We also have a guide here, which may be of assistance: Troubleshooting Failed Builds and Deployments



  • The issue turned out to be a problem with uploading the package to ProGet. ProGet was reporting the package was available in our feed and we were able to download the package through the website however the package was not available through the nuget feed.

    Deleted and re-uploaded the package a couple times and it finally took. Issue resolved thanks to help from Inedo's great support team! Thanks!



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation