<![CDATA[ProGet Basic: what counts as an "active build"?]]>Hi everyone,

We're looking at ProGet Basic to replace our current multi-tool setup, about 100 devs, single instance. Only our pipelines publish, devs just consume.

I am trying to work out how the 1000 active builds (or projects?) limit will impact our lifecycle if we start pushing SBOMs with pgutil. Here are my questions:

  • Is a build one single CI run, or a release that multiple runs roll up into?
  • What happens at 1000? Does it stop accepting new builds or just warn?
  • Do old builds age out on their own, or do we clean them up ourselves?

Also, is there somewhere to see the current count?

We are basically trying to figure out if we can stay on Basic or should budget for Essentials.

Thanks in advance,
Marco

]]>https://forums.inedo.com/topic/5825/proget-basic-what-counts-as-an-active-buildRSS for NodeWed, 02 Sep 2026 06:04:55 GMTTue, 01 Sep 2026 14:35:13 GMT60<![CDATA[Reply to ProGet Basic: what counts as an "active build"? on Wed, 02 Sep 2026 04:53:34 GMT]]>Hi @atripp,

the archive-on-promotion pattern answers the build question, thanks for that.

Your linked blog posted brought up more questions:

  • which edition covers load balancing: Essentials or Complete?
  • Since licensing is per server, does a two or three node cluster need one licence or one per node?

I need a realistic upper bound before we can start testing.

]]>https://forums.inedo.com/post/19988https://forums.inedo.com/post/19988Wed, 02 Sep 2026 04:53:34 GMT<![CDATA[Reply to ProGet Basic: what counts as an "active build"? on Wed, 02 Sep 2026 01:26:42 GMT]]>Hi @msicc ,

I would definitely budget for ProGet Enterprise, as you 100 devs is generally where a load-balanced setup really starts to make sense. It depends on so many factors, but a handful of simultaneous package restores can yield thousands of simultaneous requests by machines more powerful than a typical ProGet server (i.e. developer workstations), each which generally has to reach to connectors.

That basically leads to a DDoS against your server. See How to Prevent Server Overload in ProGet to learn more.

As for active builds,

  • a build is an entry under SCA > Projects > Builds; typically one build per CI run, but you might do more
  • only the first 1000 active builds are analyzed; so everything else will show as inconclusive
  • you can configure different stages to automatically archive other builds upon promotion; this is what we recommend

To estimate, I would do a multiple of your active, nonlibrary projects. It's certainly feasible to have multiple active builds per project (e.g. one in build stage, one in testing, another in production), but a lot of that depends on your configuration.

Hope that helps,
Alana

]]>https://forums.inedo.com/post/19987https://forums.inedo.com/post/19987Wed, 02 Sep 2026 01:26:42 GMT