Unfortunately, the npm client does not support using Windows Integrated Authentication. This means that, to getting this working, you will need to create a second web site in IIS (pointing to the same directory) without Windows Authentication enabled.

This is now fixed as of Inedo Hub 1.0.23.

Just for reference, I was able to get the correct digest of a tag and delete it with this PowerShell script... $image = "some_image" $some_image_tag = "some_tag" get digest $curlReturn = curl -I HEAD https://<proget_repo>/v2/<container>/library/$image/manifests/$some_image_tag foreach ($line in $curlReturn) { if ($line -match "Docker-Content-Digest: (.+)") { $digest = $Matches[1] Write-Host "$image digest is $digest" } } delete tag digest $URI = "https://<proget_repo>/v2/<container>/library/$image/manifests/$digest" Write-Host "Deleting tag $some_image_tag from image $image" Invoke-WebRequest -Uri $URI -Method Delete -Headers @{"X-ApiKey"="<proget_api_key>"; }

No need to share your retention logs; another user submitted them via a ticket. This will be fixed under PG-1671, scheduled for next release (two weeks from today).

@apxltd thanks for the reply it works fine for me I ve just put git , as it is available globally everywhere by default in all of our servers

Hello; this is already a planned change (PG-1657) , and it looks like it might make it in tomorrow's release!

Not yet; I saw an internal presentation on it, but I don't know the communication plan. Feel free to check with @apxltd directly... email or slack seem to be best ;)

We made and tested several changes to the installer a while back, but it's not something we regularly test/verify. Please share what you find work! Thanks.

Great question! The answer is, unfortunately, buried in the Formal Specifications. But long story short, you'll want to wrap the Get-Asset operation in a with executionPolicy = always block. For more information, note that there are three modes of executions: Collect Only - only ICollectingOperation operations will run; if the operation is a IComparingOperation, then drift may be indicated. All ensure operations implement both interfaces. Collect then Execute - a collection pass is performed as described above; if any drift is indicated, an execution pass is performed that runs: operations that indicated drift IExecutingOperation operations in the same scope as a drift-indicating operation that do not implement - IComparingOperation; this is all execution actions operations with an execution policy of AlwaysExecute; this can only be set on a Context Setting Statement Execute Only- only IExecutingOperation operations will run; all ensure and execute operations implement this interface So what's happening is that Get-Asset will never run in a Collect pass, where as Ensure-DscResource will always run in a Collect pass (but only in Collection mode). By forcing Get-Asset to always execute, it will run even in the collect pass. By the way: I would love to find a way to properly document the answer to this, so users don't get frustrated; any suggestions on where to edit the contents?

Nice OtterScript :) This will work, the variables won't "leak over" or anything like that.

Hi Ali, By default, an artifact retention policy operates on artifacts alone and does not consider builds/releases/etc. There is no current way to say "500MB of artifacts per release", however, you can combine 2 retention policies that should be close to what you want: Build retention policy: Only purge builds in deployed releases Only purge rejected builds Keep last (whatever you want) Artifact retention policy: Only purge artifacts in deployed releases Only purge artifacts in rejected builds Purge orphaned artifacts The key is "purge orphaned artifacts" which will only delete artifacts after its corresponding build is deleted. This allows you to provide the necessary granularity on the builds themselves, and let the artifact policy come in after and clean up the artifacts that no longer have an existing build. This can be extended to releases in a way, since any releases that get deleted will also have all their builds deleted. Hope this helps, -John

Any updates on this? I encounter the same issue and none of your comments helped .

The user running the install/upgrade needs to have dbowner rights on the ProGet database. The installer will give a database access error.

The error message is "cvs.badguy does not have the Feeds_AddPackage privilege", which means that the api key you've configured does not have that privilege. Please add it.

To simplify the import/export options, BuildMaster 6.2 only supports backing up / restoring to a "Package Source" (i.e. a ProGet feed); we may support for using a disk-based package source instead, but for now it's only a ProGet Universal feed. BuildMaster 6.1.5 lets you back-up to a feed URL. Note that BuildMaster 6.1.25 also has "Package Sources" (as a preview feature), which you can use to back-up all of your applications if you'd like.

Update is ok

Hi Philip, The next TFS extension v1.4.0 now has a TFVC monitor included. It's a little rough around the edges i.e. it monitors separate paths instead of branches for the time being. Let me know if you run into any issues with it. Thanks, -John

@jrasch I tried creating a retention policy, like my attached screenshot. However, it deleted all of the artifacts in BuildMaster, not just orphaned ones. Is there a way to delete just the orphaned ones? We are using Version 5.8.3 (Build 7) of BuildMaster. [image: 1580217495062-inedojpg.jpg]

Thank you

Hello; the agents don't currently support this, though this is something that we've considered for a long time -- some of our key customers have requested this as well. However, we've developed some interesting technical alternatives that make the pull-based agents largely moot (at least according to the folks who requested it originally); for example Romp and universal packages allow the client to self-install, or at least have an in-house BuildMaster or Otter instance that can manage installations based on packages.