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!
ProGet: Feature Request: lock Repackaging to specific feeds, same as Promotions
-
I would like to be able to "lock" the feeds that a feed can Repackage into, just like we can for the Promote action.
We use Repackaging to promote packages into a Production feed, and we only want them to ever go into a specific feed based on their source feed. There doesn't seem to be a way to restrict the target feed when Repackaging, like there is when Promoting.
This would reduce the clicks necessary and the chance for error.
Thanks!
-
Hi @mcascone
Just to confirm, are you referring to this field?
I didn't get a chance to test (want to confirm I understand first), but the "Target Feed" field should be either:
- a be drop down of all NuGet Feeds (when "Promote To Feed" is not set)
- a dropdown of two feeds (current, and "Promote To Feed")
Is that not the case? If not let's get that fixed :)
Cheers,
Steve
-
Hi, thanks! Yes, that's the screen I'm referring to. I see the same behavior in NuGet feeds and Universal Package feeds:
Promote Package
respects thePromote To Feed
setting in the source feed'sManage Feed
settings:
Repackage Package
does not respect thePromote To Feed
setting:
We're on Version
5.3.43 (Build 4-proget53)
.
-
@mcascone thanks so much for confirming that! This may be fixed in v6 already, but I created the issue PG-2072 just in case it's not.
We should get it shipped in the next or folllowing maintenance release.
-
Thanks! I see on that YouTrack page that it's planned for v6.0.6. Will it not be ported back to v5? This would be motivation enough for me to upgrade. Not that I need motivation to upgrade, but it would certainly increase the priority.
-
Hi @mcascone,
Sorry about that. I'll get that backported to ProGet 5.3 also. This will be tracked in ticket PG-2074.
Thanks,
Rich
-
Hi, just wanted to say that i happened to look at the new releases available for v5, and saw that this is fixed in the latest release, 5.3.44.
Awesome! Thanks!