During upgrade package feed url reverts to server name

Automated deployment for web applications and databases

Moderators: Mike Upton, justin.caldicott, Sean.newham, csmith, chirayu, DavidSimner, david.conlin

During upgrade package feed url reverts to server name

Postby jakenuts » Thu Nov 28, 2013 4:54 pm

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
jakenuts
 
Posts: 8
Joined: Tue Oct 13, 2009 10:40 pm

Postby james.billings » Mon Dec 02, 2013 3:13 pm

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?
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.

Postby jakenuts » Mon Dec 02, 2013 4:27 pm

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
jakenuts
 
Posts: 8
Joined: Tue Oct 13, 2009 10:40 pm

Postby james.billings » Mon Dec 02, 2013 4:29 pm

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!
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.


Return to Deployment Manager

Who is online

Users browsing this forum: No registered users and 0 guests