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!
What happened to the Deployment feed type?
-
Did you remove the Deployment type feeds? I'm not sure where it disappeared but it seems to be in 4.x, I only don't know as I hadn't tried to create a new one until now.
I know there is the Universal Feed but it is not implemented in the same way so in the current form it isn't useful for Deployment storage.
If that was the intent of the Universal Feed then you need to allow versions to include build numbers.
For our environment we need to store multiple versions of even builds, not for very long but we generally keep 5-10 builds. Now with the Universal feed type we cannot.We already have two Deployment feeds that continue to work as you had first implemented so I'm not sure why we can't continue to create new ones.
Thanks,
JonProduct: ProGet
Version: 4.1.1 -
A "deployment feed" was just a NuGet feed with different styling (different icon, and no command-line instructions). So, you can actually just create a NuGet feed to get the same effect.
Note that, in Otter and BuildMaster 5.1 (shipping today), we have the Ensure-Package, Deploy-Package, and Import-Package operations, which will much more naturally work with Universal Feeds than relying on NuGet.
-
Thanks, but what about the versioning of Universal feeds? Why restrict that to 3 places?
-
We implemented SemVer, which is effectively a standard now; the propietary versioning scheme that NuGet uses has caused so many problems over the years, and they're only starting to address them (for example, NuGet 3.4 undoes one of the more silly rules they followed, which was that 0.0.0 <> 0.00.0).
At this point, we would suggest to move to that, and use the metadata tags (1.0.0-x001) provided by the specification.
It's very possible NuGet will move to SemVer in a future version.
-
Good to know the other Nuget type tags exist for that, I forgot about those and had not tried those.
Changing our software would be a nice easy way but it is not something we can do. -
It's also worth noting, with Universal Feeds, you can put whatever additional metadata properties you'dl like in there, like <code>fullVersion: "3.2.00300201.X.400"</code>.
-
Sorry for a late follow up on this.
So one place where this solution falls apart is that your Jenkins add-on for BuildMaster does not support the meta-tags in the version field.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login