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.

Hello Jeff, There is currently a bug in the FeedCleanup task for Docker feeds. PG-1030 has been fixed for the next version of ProGet, but until then, disable the FeedCleanup task for any Docker feeds in /administration/scheduled-tasks.

This error means that the user running the installer doesn't have access to the database in the connection string in the config file on disk. You'll need dbo access to the database in order to perform the upgrade.

There doesn't appear to be; but we have a new issue (BM-3034) for this. If it's easy to do, we'll get it in ASAP!

Discussion should be moved to a new post or followed here: http://inedo.com/support/questions/6554

Hi Alana, Thank you for the update. I was quite surprised too when realised we can't use case insensitive collation in Postgres. But what if we have 2 columns, one contains data as is, and one contains normalised data, e.g. Login and LoginNormalized. The first one is indexed, the last one is used in queries. But I understand this leads to different schemas in SQL Server and Postgres. I completely agree we can bet on SQL Server, but I don't know its licensing options yet. Posgres is working well from my point of view, except this detail. Since a lot of web applications use Postgres and I haven't heard about case sensitive logins yet, I believe that solution exists. Thank you for all of your hard work on this awesome project!

As of v5.6, the "SQL Change Scripts" feature is designed with these principles in mind: Database Changes Done Right. Run once and only once Impossible to be “un-run In order to accomplish this, a metadata table is created in the database (__BuildMasterDbSchemaChanges2) to track which change scripts have already been run. Before running a script, this table is queried. Regarding "resetting" the idea that a script is run, the best bet is to delete and re-add it from BuildMaster. You can also restore that particular database.

OK ; in this case, can you provide a simple reproduction case that we can try? Like, a new application that reproduces this? And please send this as a ticket -- Q&A are generally the lowest priority when it comes to support, so we want to handle it through better channels :) The $ApplicatinName and $ReleaseNumber are standard test cases for us, so they do work in our config file replacement tests (which, are quite complex due to so many legacy cosniderations...)

The Operation does nto currently support this; ApplyLabelOperation.cs is the source code, so perhaps it wouldn't be too hard to customize?

I would also try to upgrade your new server to 4.7.6 as well, because I really can't think of anything in the ProGet software that would yield this behavior. The file's bytes are simply written to disk as they are received using streams and async methods. Moreover, we test with large packages and have a lot of users who have large packages, and none have reported issues.

It seems like something changed in security settings - Publish Packages task got "private" scope. [image: vo6hmcg.png] I droped "Publishers" and added them again, scope has been changed to "all feeds" and problem gone! [image: NEDd3NU.png] Seems it's an upgrade bug because the scope option can't be set in free version... [image: 8qyYRQ3.png]

And also see this post.