@dean-houston Thank you for the insight! Definitely did not think of that as an issue.

We have been using ProGet for a while now and are really starting to expand how we use it. We have developers upload private, shareable NuGet/PyPi packages and mirror nuget.org/PyPi packages. We hadn't had multiple connectors for one type of feed until recently with NPM repositories and some new NuGet feeds for other vendors.

Has anyone found if associating multiple connectors to one feed made management easier or more difficult? If you introduce promoting packages, does that affect the decision to associate multiple connectors to one feed?

An example we have is mirroring the default NPM rpository as well as a FontAwesome NPM repository for a paid tier. It seems easier to associate both connectors to one "unapproved-npm" feed and promote allowed verisons to one "approved-npm" feed, but we also don't have an automated pipeline around promoting packages. So, we are still very earlier in discovering what works for us.

Any input/experience would be greatly appreciated!

Hello! We have been creating our own, internal, Terraform modules and would like to host them internally. Casting my vote to have this implemented!

@atripp I know this is an old topic, but I have not see anyone else ask about the Age field with uploaded symbols and I don't see it addressed here. We had a developer upload a .snupkg to a ProGet feed (hosted on Podman containers on Linux) and the age field does not make sense to me either. We are running Version 2023.15 (Build 4)

We are also experiencing this issue, what version will this be resolved in?

I second this! We also use Prometheus for metrics on as many of our tools as we can get.

@atripp restarting the container seemed to have resolved the issue, the secure credential does not show like that anymore and I was able to link a secure resource to it.

@atripp we only have one web node so traffic is only going to one instance.

Here is what shows after clicking on the TeamCity extension:

@rhessinger here is the Extensions page:

Here is the container log after starting up, it looks like the extensions load okay:

info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0 - 200 233 - 3.2996ms
Running Execution Dispatcher...
Execution Dispatcher completed.
Running Execution Dispatcher...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0 - 200 233 - 2.8641ms
Running Execution Dispatcher...
Execution Dispatcher completed.
Running Execution Dispatcher...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0 - 200 233 - 5.0181ms
Running Execution Dispatcher...
Execution Dispatcher completed.
Running Execution Dispatcher...
Execution Dispatcher completed.
Running Infrastructure Sync...
Infrastructure Sync completed.
Running Execution Dispatcher...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0 - 200 233 - 4.6794ms
Attempting to use shared configuration for BuildMaster.
Shared configuration file not found at /etc/inedo/BuildMaster.config.
No encryption key is configured. Credentials will be stored in plain text.
BuildMaster version is 7.0.21.1.
Current DB schema version is 7.0.21.1.
Starting the messenger...
Configuring proxy settings...
Checking for server and database time difference...
Starting the Event Listener Dispatcher task runner...
Event Listener Dispatcher task runner started.
Starting the Server Checker task runner...
Server Checker task runner started.
Starting the Execution Dispatcher task runner...
Execution Dispatcher task runner started.
Starting the Update Checker task runner...
Update Checker task runner started.
Starting the Infrastructure Sync task runner...
Infrastructure Sync task runner started.
Starting the Pipeline Stage Validator task runner...
Pipeline Stage Validator task runner started.
Starting the Repository Monitor task runner...
Repository Monitor task runner started.
Starting the Scheduled Promotion Dispatcher task runner...
Scheduled Promotion Dispatcher task runner started.
Starting the System Execution Cleanup task runner...
System Execution Cleanup task runner started.
Starting the Retention Policy Dispatcher task runner...
Retention Policy Dispatcher task runner started.
Initializing Server Checker...
Initializing Execution Dispatcher...
Server Checker initialized.
Running Server Checker...
Checking servers...
Server Checker completed.
Execution Dispatcher initialized.
Running Execution Dispatcher...
Execution Dispatcher completed.
info: Inedo.Web.BackgroundTaskQueueService[0]
      Background Task Queue is starting.
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://[::]:8082
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /usr/local/buildmaster
Initializing Event Listener Dispatcher...
Event Listener Dispatcher initialized.
Running Event Listener Dispatcher...
Checking for event occurrences after #0...
No event listeners need to be run.
Event Listener Dispatcher completed.
Running Execution Dispatcher...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0
Setting proxy configuration...
Initializing extensions in /var/buildmaster/extensions...
Loading DotNet extension from /tmp/Inedo/ExtensionCache/f6315c3b229fa3387291f6ed2860acff8156a66d/package/net5.0/DotNet.dll...
Loading Git extension from /tmp/Inedo/ExtensionCache/d72b402996bcfb39d53ea89306b0b9f99bdebb90/package/net5.0/Git.dll...
Loading GitHub extension from /tmp/Inedo/ExtensionCache/6d078cf74c73cb8253cc22f64b763f3354be2e70/package/net5.0/GitHub.dll...
Loading InedoCore extension from /tmp/Inedo/ExtensionCache/a97372944e4b7e10404a9c7a4e846b944543463e/package/net5.0/InedoCore.dll...
Loading Jira extension from /tmp/Inedo/ExtensionCache/dc2da12cdb46e606be47ee7ae37766778b7026e9/package/Jira.dll...
Loading Scripting extension from /tmp/Inedo/ExtensionCache/54259091ec39b1a2d22a7dbf039d26bd4593daf0/package/net5.0/Scripting.dll...
Loading Windows extension from /tmp/Inedo/ExtensionCache/3f1cf38d508f252d35c93e10c85435e41d929dfe/package/net5.0/Windows.dll...
Loading Jenkins extension from /tmp/Inedo/ExtensionCache/1e4510c2ecb2c4f9d6a20631d1e0a4174bdafa94/package/net5.0/Jenkins.dll...
Loading NuGet extension from /tmp/Inedo/ExtensionCache/e535b3c4766bf719a6949ef3fd7538b3fecc4da0/package/NuGet.dll...
Loading NUnit extension from /tmp/Inedo/ExtensionCache/71b4512fcd92ddf010a08c2fe8a07f6db5366de5/package/NUnit.dll...
Loading Python extension from /tmp/Inedo/ExtensionCache/511919953e90ac88aeb465de74ad46e07417a5b0/package/net5.0/Python.dll...
Loading TeamCity extension from /tmp/Inedo/ExtensionCache/b85e2ed12ff40cfdda3c896b7bbed5959005f24d/package/net5.0/TeamCity.dll...
Extensions manager initialization complete.
Initializing Infrastructure Sync...
Infrastructure Sync initialized.
Running Infrastructure Sync...
Infrastructure Sync completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://ohsedvcntnr01.summit.network:8082/0x44/BuildMaster.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications - 0 - 200 233 - 751.3204ms
Running Execution Dispatcher...
Execution Dispatcher completed.
Initializing Pipeline Stage Validator...
Pipeline Stage Validator initialized.
Running Pipeline Stage Validator...
Getting list of active builds...
Pipeline Stage Validator completed.

@atripp thank you for the info! What's the typical setup you see with other customers? Is all this described in documentation somewhere I missed?