Good idea about the throw statement - I've added a feature request with suggested formal grammar to our public issue tracker as IEE-14. There are other things we'll have to take into account such as documentation updates and updating the visual plan editor to handle this, so it's not scheduled yet, but at least it is logged.

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.

Hello; I've added a feature request for this. There is no ability to do a "mass edit" like this I'm afraid.

Hello; Inedo.com currently seems to only communicate over TLS1.0; I don't have a timeframe for when that will be upgraded, but I want to add that we don't have any secure or sensitive information on inedo.com anyways. In the case of LDAP, it seems to me that there is some sort of issue with the LDAP code mapping your username. AD configuration can be very complicated I'm afraid, and it will involve a bit of back-and forth, with sharing potentially sensitive or company-identifying information. When you search for a user in ProGet, you will see a log of the domains, etc., being searched. Ifyou can publish that to a ticket, then we can investigate further.

Hi Josh, Sorry, this seems to be a v6 glitch! But we're on it :) I've submitted BM-3192 and then inedo-docs/#6 to update our documentation. Your understanding of how the feature is supposed to work is correct, and your use-case is how it's supposed to be. Thanks for reporting it !

Thanks Dean, I did a fresh install. The new settings are so minimal that I'm not sure people will notice the change. Crashes after the first one are silent, as before, making the user restart the service by hand and think "ProGet flaked out". What do you think about resetting the fail counter every few days? About using the "run program" hook to report crashes? Does Inedo automatically get crash reports? Thanks for your help. [image: RPpQu6V.png]

Based on the URL -- you must have created a Universal Packages feed. You'll need to create a NuGet feed. [image: create-feed.png]

hi Keith, We definitely plan on having an offline process, and welcome your feedback on it. You can read a bit about how the hub works (it's in beta, so please forgive the rough docs). Specifically, check out "Configuration and Offline Installs": https://inedo.com/support/documentation/proget/installation/hub/inedo-hub The Inedo Hub wraps Romp (more coming soon on that), so you could also use that to install ProGet as well, as a command line process. Does that help?

You shouldn't be receiving a "401" error from the public npmjs registry. If you are, my guess is that you have some sort of proxy or firewall selectively blocking outgoing access to certain queries to the registry. Once you resolve that, then p[roblem #2 will also be resolved.

We don't have any guides on this integration specifically, but the usual situation is that TC can't authenticate. The easiest thing to do is to allow anonymous publishing to the feed, but not overwriting. Otherwise, you can try to get the authentication to properly work, which typically involves sending username/password or configurating an API key properly.

Thank you, I was not aware of this. Seems to work

In this case, it seems like your machine has no internet access, and can't request a key from my.inedo.com; you can do it manually from that website.

Are you sure you're using the right server context when calling the BuildMaster Powershell Asset? If you print out the server name in your asset using $env:computername do you get back the expected server? If I create a simple plan ##AH:UseTextMode for server $MyServer { PSCall GLOBAL::Test_Powershell_Asset; } Where my powershell asset is defined as this one-liner Invoke-Expression C:\Path\To\PowerShell\script.ps1 Then I am able to run this script, no problem.

We've narrowed down the issue. It seems that the service user that ProGet is running with cannot see all the members of the LDAP groups. This can be fixed by changing the user to one that can see all members of the LDAP groups through this process: https://inedo.com/support/kb/1077/configuring-your-inedo-product-to-run-as-a-windows-domain-account

You can request it at my.inedo.com, or just ask as a note on the Otter Quote Request Form. What's nice about going through the pre-sales/quote process, is that we can work together beyond just random forum / Q&A posts, as obviously we are generally motivated to help you prove a success to enable a sale ;)

Hello; please fill out the contact form, and we will be able to you via email.

I see, that's an interesting idea. It seems like some sort of auto-generated documentation of sorts? I don't know if ProGet is the place for that data, but we don't have a feature to store such doumentation at this time. So, maybe you could auto-post it a documentation wiki of sorts and use the "Project URL" property to link to it?

It was my reverse proxy (apache). I had to set AllowEncodedSlashes to On. Problem solved.