Hi @mcascone , I admit this can be confusing and is unintuitive because these were added separately over time, and the weren't originally designed for how they're used today. We need to rethink/redesign this based on the use cases. I'm going to add this thread under the "promotion/repackaging workflows" topic for our next major version of ProGet. Once we know what we want to do, we can may be able to implement some changes as a preview feature in v6. FYI, this is exactly how the big API Key changes and feed/package usage instructions came about! https://forums.inedo.com/topic/3204/proget-feature-request-api-key-admin-per-user So stay tuned :)

Thanks @mcascone , I also added this to our "Promotion / Repackaging Visibility & Permissions Rethinking" task - sounds like something we can consider :)

Thanks very much for the clarification

Here is a working PowerShell example (v6.1+): Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/builds/deploy?applicationName=ApiTest&releaseNumber=1.2.3&buildNumber=1&key=<api-key>" For pre-v6.1 versions, the equivalent is: Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/packages/deploy?applicationName=ApiTest&releaseNumber=1.2.3&packageNumber=1&key=<api-key>" I have also put in a doc change request to clarify the endpoint names. Additional note: -UseDefaultCredentials would be required if Integrated Authentication were enabled.

There isn't currently, but there will be soon! Please see PG-1221 I can't imagine any reason at all this wouldn't be done, and it can go it the next maintenance release assuming it passes code review etc! Thanks much for the specific suggestion!

Package promotion is a paid feature; please see Features by Edition.

If you want to quickly add something like this are familiar with C#/.NET you can already create a custom package store to do this, see: Extending ProGet Beyond that, we will consider this as a first-class feature as you suggested. If you have any specific thoughts as to what would need to be configured for the hooks please add them to this thread.

Thanks for this post id did help me a lot. I did also get the message "Specified from feed '' does not exist." while trying package promotion. This message is missleading as the real issue was the http Client not passing all the content types as the server wanted. I did try with postman and powershell Invoke-WebRequest. Think the server is unecessary strict with handling the requests, but maybe there is a reason for that. Please consider adding a few "HttpClient" example to the documentation in different languages like powershell, java,c#. It would save the customer a lot of time. https://docs.inedo.com/docs/proget/reference/api/package-promotion

Thanks, I'll add this as a feature request; there should be a link on the "perform manual action page" that links to the execution, but you can see all current executions on the home page dashboard.

This can be done as a Promotion Requirement by implementing the PromotionRequirementBase; this class basically just returns a PromotionRequirementStatus that includes a text description and a PromotionRequirementState indicating if the build is eligible for promotion. If you'd like to see how any of the built-in promotion requirements are implemented, feel free to use Reflector or another disassembly tool, or just ask us for the source code for those items.

As written now, that promotion requirement is a very simple text-based match - anything more complicated would require a custom predicate.

Nevermind, the Build was already rejected.

It was very helpful.

Thanks look forward to it