Yes, create a custom task from the Users & Groups > Customize Tasks page that has the Overwrite Packages subtask, and then restrict it at the system level.

The NuGet URL should be http://proget.edlund.dk/nuget/Edlund , not /feeds/

Both of these are paid services, and your best bet would be to follow the tutorials to see how to configure them. While they both offer similar outcomes, they do so quite differently. We don't have a simple comparison at this time, but if you find more through your research, please do share!

Awesome Ben, thanks for the quick action! I've followed the issue, will I get an automated notification when it's known in which version the fix is going to be available?

Hello Ben, thanks for help. I can confirm that node.js v 6.11.4 with slash at the end of URL works ;)

Hello Dmitry, I don't think there's currently a way to delete Docker images through the API. The blobs are deleted by the FeedCleanup scheduled task. You can run the task manually from /administration/scheduled-tasks, and it will run automatically once per day by default.

Hi Alana, Thanks for your reply. I ended up submitting a bug Ticket which I need to respond to. But in response to your comment, The Agent and the runtime user are both the same account. Aside from the simple script above, I also tried to get it to return the value, and it would only return 's' in once case, error in another , or indicate the value was part of a Dictionary, which I'm guessing is meaning its within an array. Tod Hoven is my contact for the issue that I will be working with, but at the moment my BuildMaster instance is offline, so I will be following-up once our environment is back online. I'll try and remember to update this thread with the fix once we have it... -Trent

The FTP extension can help with this

We identified a cause of this, and it was fixed in PG-1121 in ProGet 4.8.6

I see, so the actual problem is that you don't have the ability to create or manage AD Groups? Yes, that is certainly annoying... You will probably be better off working within your organization to change this policy. It's awfully silly, and totally defeats the purpose of using AD to begin with. That said, we will consider adding a "teams" feature for a future version.

Basically, the template doesn't represent valid OtterScript, and that's why there is an error. Basically, this is not a valid OtterScript statement: $Increment(${index}, 1); You can, however, do this: set ${index} = $Increment(${index}, 1); Except, the "set" statement is not supported in a text template, which means you cannot do what you're doing. You could probably work something out with $foreach $i in @Range(...), but it could get a little messy.

Yes, if you create a Artifact Retention policy with these options: Only purge artifacts in deployed releases Only purge artifacts in rejected packages

ProGet Basic includes support via tickets submitted at https://my.inedo.com in addition to this QA forum (which is more often community supported) for each year purchased of Annual Licensing. If you choose the Perpetual option, the 1st year is included, and then support may be renewed each following year for 20% of the "then-current" licensing price.

Issue was due to the noexec option on the /tmp partition. Remove the noexec option and remount the /tmp.

I see what happened, I looked under Servers where I would have thought that info would be but instead it's under General in the docs.

Can you provide the full stack trace? It will be logged in Admin > Errors.

Based on that error, it sounds like ASP.NET 4.5 is not enabled on your server; this is a separate role feature you must install on your computer/server. It could also be a configuration error, as the message suggested, and you've prevented proget's web.config from removing those handlers at the machine level. In this case you'll need to use the built-in web server, or fix the configuration.

There's nothing jumping out in the logs that's off, it likely is bad information that the client is sending. Most likely it's stemming from the fact that, your package is about 100x as big as a NuGet packages (i.e. .NET libraries) are intended to be. Microsoft will probably never prioritize support for this sort of package, so it's not going to be high on our list either to work-around either. I would recommend you to find a different way of solving whatever problem you are trying to solve in a different way. If you're packaging applications, you should consider a format actually built for such purposes, like the Universal Package Format or Romp packages.

This is a false positive; unfortunately we seem to be the target of many of them :( See http://inedo.com/support/kb/1113/anti-malware-false-positives-code-signing-and-safety-of-inedo-products Please report the false positive, because some of the virus total companies will not let us do it, only their customers.

I'm pretty sure mike you don't need to copy the folders one at a time and wait for pickup...you could copy all the packages at once. And watch out for that powershell script -- it will copy all files in all subdirectories into the current directory, so if your subdirectories contain things other than packages you should add a filter to it.