We added basic support for this in BM-3197, though anything more complicated needs to be handled with a custom event listener. If you want to create a custom extension for this (and are an enterprise customer) you already have access to the source code at https://my.inedo.com, or you can request direct source access to our GitLab repository as well, just send a note via the contact form.

I think one approach you could take would be to utilize the Native API which, using your example, could be found at https://example.com/reference/api. You could call the Pipelines_GetPipelines endpoint, filter by "Active_Indicator" == true, then parse the "Pipeline_Configuration" xml for each pipeline looking for the "PlanName" attribute of the "Properties" element under the "Inedo.BuildMaster.Pipelines.PipelineStageTarget" elements. Here's a snippet of the "Pipeline_Configuration" I get back when I run this, to get a better idea. <Inedo.BuildMaster.Pipelines.Pipeline Assembly="BuildMaster"> <Properties Name="All" Color="#499e8d" Description="The pipeline that deploys to all environments on all stacks. " EnforceStageSequence="False"> <Stages> <Inedo.BuildMaster.Pipelines.PipelineStage Assembly="BuildMaster"> <Properties Name="Build" TargetExecutionMode="Parallel" AutoPromote="False"> <Targets> <Inedo.BuildMaster.Pipelines.PipelineStageTarget Assembly="BuildMaster"> <Properties PlanName="Main-Build" EnvironmentName="BuildFarm" DefaultServerContext="None"> <ServerNames /> <ServerRoleNames /> </Properties> </Inedo.BuildMaster.Pipelines.PipelineStageTarget> </Targets> From this you can see I have a Pipeline named "All" that has a stage named "Build" that calls the plan "Main-Build".

Found the follow-up issue as a user error. After upgrading to 6.0.x the feature worked as expected.

We don't have a tutorial or guide on creating one, but it basically just involves making a UserDirectory class, and then implementing the methods. Note that in BuildMaster 4.9, we changed the interfaces a bit to be more inline with ProGet. You can use a disassembly tool to see how the current ones work, or request the source.

I can confirm that this is fixed in version 3.3.7 of ProGet. It is now working like a charm.

These days, the general workflow has really evolved to assembling artifacts into "packages" and then pushing to a package manager; basically Build > Package > Deploy I think the reason is that it's much easier to deploy known packages (then assemble them from artifacts). In this case, ProGet serves as the Package manager step.

This depends on the setup, if you use Integrated Windows Authentication, you cannot have anonymous access to any feeds because the authentication will be required before the request even hits ProGet. However, there is an option on the "All Settings" page named "IntegratedAuthenticationEnabled" that when set to false will allow you to use the Forms-based approach using your Active Directory credentials. Another option with regard to the build server is to just copy the .nupkg files on disk to the feed's storage path, which will in turn be picked up by the indexer and added to the feed.