During upgrade package feed url reverts to server name

jakenuts · November 28, 2013 10:54AM

I know this happens when I upgrade, its possible it happens more often as I seem to correct it a lot (when a deployment fails it's usually the reason). I set my package feed to http://deploy.mydomain.com:90/nuget so that I can reach it from my CI server. Often is returns to http://machinename:90/nuget and becomes inaccessible to external callers (as the machine name doesn't resolve to a public IP).

Thanks so much!

James

James B · December 2, 2013 9:13AM

Thanks for your post.

Is this the feed built in to DM that you're referring to? If so, then I think we do indeed default it to the local machine name. Are you editing the existing reference to it? What you could try doing is adding a second feed that uses the URL you need to work with, and that /should/ get left alone during upgrades?

jakenuts · December 2, 2013 10:27AM

Yup, its the built in one. I'll definitely try the secondary feed. I wonder how many users have their CI server, deployment server and deployment agents running within the same "network domain" (so that the machine name is resolvable). I've got the deployment and agent running on the production server to keep deployments quick, but since the build server is located elsewhere so as a default the machine name doesn't help when I publish. I realize of course that the internal nuget server is not recommended so perhaps I'll try to work out something else.

Thanks again!

James

James B · December 2, 2013 10:29AM

We've definitely heard of this sort of thing now and then, but I think most folks have everything within the same network, so name resolution doesn't break.

Post back if you're still having trouble!

During upgrade package feed url reverts to server name

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk