Assuming ProGet.Service.exe is in C:\Program Files\ProGet\Service, there should be a folder named C:\Program Files\ProGet\WebApp. Does the WebApp folder exist?

Dependency resolution is handled entirely by the NuGet client, so it's hard to say why the NuGet client is hanging like that. There have been no changes to ProGet that would yield this behavior.

Each rule separately checks that all of its conditions are met before deleting a package. If any of the rules decide to delete a package, the package is deleted.

Hello Glenn, The payload will contain: Event_Code (BLDCPP) Event_Description (Build Promotion Completed) Release_Number Build_Number PipelineStage_Name For other types of event listeners, Event_Code and Event_Description are always included and the rest of the fields are from Event Details in the event log for that event type.

Hello Glenn, The next version of the YouTrack extension will include a Find-Issues operation, so you'll be able to do: YouTrack::Find-Issues ( Credentials: MyYouTrackCredentials, Project: IT, Filter: "version: $ReleaseNumber -resolved", Output => @IssueIDs ); foreach $id in @IssueIDs { YouTrack::Add-Comment ( Credentials: MyYouTrackCredentials, IssueId: $id, Comment: Testing BuildMaster/YouTrack integration. $ApplicationName $ReleaseNumber.$PackageNumber -> $EnvironmentName ); }

Thanks Alex. Looking forward for new version.

Hi Leo, can you try this? http://44.inedo.com/otter/artifactory-1.5.0-beta1.zip Note it will need to be manually installed by just copying the otterx file to your extensions folder.

Oh, that's certainly a mistake -- actually it came when the feature was released. But I've updated the index page, so it'll be updated at some point when site gets updated. The security API are also unspecc'd. That's something we plan to bring to all products, and will probably be much easier to spec out

I like the idea, but of course there's definitely some questions and things we'd need to think about before we can spec out the feature. Just some initial thoughts... Should this really apply to all applications, seems only a few might want to share one Pipelines and deployables are not global (well, you can have a global pipeline); what to do about that? Should UI restrict from choosing? Who can edit these? Admins only? How else will they behave differently? And then of course, there's the question of how this will tie into the (unspecc'd) "Projects" concept (cross-application releases)

This error appears to be related an extension missing. I would stop/start the agent, which should cause the extension to reload

Ah, I think the confusion here is because of the different meanings of the word "set". If you don't select the deployables in the release template, it will have the default deployables available in executions. That is, if you do for deployable Foo and Foo is a deployable in the application, it will execute the code inside the block. However, you can select specific deployables for a release and the for deployable Foo block will only be run if Foo is selected.

I found the issue. User error on my part. This is a small plan that handles this and I had a Legacy plan doing something similar but not using the Promote API. The pipeline was still pointing to that old plan and I just didn't notice the calls going to Proget. Then I was working on the new plan so as far as I knew it wasn't using the filename but in the old plan it was. Changed to the correct plan and the Promotion worked fine. Sorry for wasting your time on this.

There hasn't been a huge demand for Native TFS Repositories, so we haven't prioritized it. We don't have a ETA, since everyone who has asked for it just ended up using Git in TFS.

The person who initiated the executions is would be recorded in both versions (if not, a bug for sure), but in the free version, since everyone is effectively the same user, it's all recorded under "Admin" user (by design).

I certainly see the issue. Where this starts to get tricky from a UX perspective is that some folks have long stage, server, and plan names. So, we need a way to better represent this data in a compact view.

Hi Ben, When trying with the universal feed API endpoint: [image: Capture003.PNG] I'm getting the error: [image: Capture004.PNG] So authorization is ok, but now it seems like feed API is waiting for a Key the extension is not sending.

Hello Jeff, I've fixed PG-1034 and PG-1035 in the next version of ProGet. There is no configuration problem on your server.

Thanks for response. I created a new API Key. My environment IDs are as follows: Development = 1, Testing = 2, Production = 3, Build = 5 If I run the API call you provided above for Build environment, doesn't it mean I will need to resequence the rest of the environments too?

Can you provide a example for this not working? The Add-Member cmdlet interacts with PSObjects, but the OUt-String does interact with the host (which, is different than an output stream... and has some strange handling sometimes).

When a Windows Service doesn't start, the reason will be logged in the Windows Event Log. Usually, it's related to an inability to connect to the database. Note that, you can also run the BUildMaster Service interactively to diagnose as well.