Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    ProGet Basic: what counts as an "active build"?

    Scheduled Pinned Locked Moved Support
    progetsbomlicensing
    3 Posts 2 Posters 3 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M Online
      msicc
      last edited by

      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

      atrippA 1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer @msicc
        last edited by

        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

        M 1 Reply Last reply Reply Quote 0
        • M Online
          msicc @atripp
          last edited by

          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.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation