Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. dean-houston
    3. Posts

    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!

    dean-houstonD Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 233
    • Groups 1

    Posts

    Recent
    • RE: Proget docker update from 2026.14 to 2026.15 breaks Postgres DB

      Thanks @felfert ! Forgot to mention, but this was really helpful and we fixed the issue exactly as you had suggested; we believe that's what the postgresql container does on its own anyway.

      As for the "broken image" -- because we can't just have one error at a time right? There was a regression in replication that hit SQL Server, and that node just happened to be SQL Server at the time.

      Anyway... should work now!

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Tracking Image Deployments by Image instead of Tag

      Hi @stephen.schaff ,

      I'm afraid not; those particular feature (i.e. the database tables) are designed to hold the underlying tags, not the digests. It's non trivial change, and it aligns with best practices in using "immutable tags" -- especially when you're using version tags like 2.0.0.477'.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Can I create a policy exception for a vulnerable package

      Hi @bobmaurer ,

      You can Override it again, then select (unassessed) in the drop down. That will effectively delete it.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Bug: ProGet caches invalid Docker layer blob, keeps serving it

      Hi @cyril ,

      Thanks for this additional information; we plan to have this fixed via PG-3431 in the next maintenance release, scheduled for Nov 27. However, it should just be an extension fix, so you may be able to simply update the extension to have it resolved as well once we update that.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Bug: Configuring ProGet via the API/pgutil, fails on (certain) type conversions

      Hi @cyril ,

      Thanks for letting us know; we'll get this fixed via PG-3422, targeting the next maintenance release (Nov 13).

      FYI -- we will do it on the server-side, so no need to add an argument. These values are stored as a string (VARCHAR) in the database but converted to a typed value in the code (C#). So, we just need to add a type coercion to the API, similar to what the UI page does.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Support for setting Debian feed distribution/components via pgutil / API

      Hi @cyril ,

      We'll add support for this via PG-3420, targeting next maintenance release (Nov 13). Thanks for the suggestion!

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: ProGet Enterprise Edition Version 2026.14: Maven Feed - Cannot download remote Maven artifacts, if package cache is disabled.

      Hi @sebastian.heess ,

      Thanks for sharing all of the details; it looks like this is a regression in ProGet 2026.14; we'll get this fixed via PG-3419 in ProGet 2026.15.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: ProGet Basic: what counts as an "active build"?

      Hi @msicc ,

      Great question; so it's the same product/software (ProGet Enterprise), just with different packaging/quantity:

      • Essentials consists of a single license of ProGet Enterprise
      • Complete consists of two licenses of ProGet Enterprise plus Services

      It's not uncommon to have multiple licenses for non-production scenarios:
      https://docs.inedo.com/docs/proget/administration/license#licenses-for-non-production-testing-environments

      Licensing is per instance, which can be a single-server installation or a clustered (multi-server) installation.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Feature Request: Evaluate package based on policies before they are pulled with connector

      Hi @gisleso ,

      What you're describing has come up lately, though with a slightly different angle.

      I'm going to quote a variant of this, from a recent support ticket.

      We are trying to establish a policy where packages newer than 30 days are blocked on the package server level.

      Unfortunately, we are unable to use the feature they way it currently works, unless we are missing something.

      As soon as we block packages in any capacity, we are unable to do even the most rudimentary pip install or uv sync operations, as transitive dependencies cannot be downloaded (same for npm actually, but that is not an important package manager for us).

      I assume it has to do with how these package managers generally work:

      1. They construct a dependency graph from the available versions, taking various rules like locks and version ranges into account.
      2. After they built the graph, they will try and download the versions they have selected, which fails in most cases on ProGet, because the versions that are advertised by the index may not be available.

      We're a bit surprised by this behavior, because it seems like versions that cannot possibly be downloaded should not be present in the index.

      We think ProGet should not advertise versions in the index that it blocks.

      There are options with some package managers to take a cut-off date into account when calculating the dependency graph, but defining that in code on every single piece of code we have throughout the org defeats the purpose of having a central repository that should be able to do that.

      Are we missing something? Can we hide the versions that are noncompliant from the PyPI package index, or could that be enabled? This is a rather critical feature for us.

      And for more context, here's some of our response:

      This is a somewhat frustrating technical limitation; it comes down to the fact that we often can't know if a package is Noncompliant until we have the full metadata and even the package file.

      The API examples you shared illustrate this exact problem; consider what happens when you make that same request to PyPi.org (i.e. curl https://pypi.org/simple/certifi/). It's a long list of versions of that package, but there's no additional metadata.

      That means ProGet wouldn't be able to filter that list without querying the metadata of each version -- and that's just not technically feasible to do. Some clients can actually be configured to do that (like pnpm), but they can take a more context-sensitive approach. For example, they'll start by downloading B-1.2; then, if it's too new, it downloads B-1.1, and so on. Obviously a server can't know what the client wants with the data.

      Anyway, this is a known issue it's something we're researching. We call it "Metadata Suppression", but there are a few other major Developer Experience issues as well. The biggest one is that there's simply just no indication that these packages are being hidden by ProGet. So a Package Restore through ProGet will behave drastically different to the public repository, and eventually that will just lead to developers not trusting or using ProGet due to erratic behavior. That's a not a situation either of us (i.e. us as the software vendor, you as the platform ops team) want.

      Our general guidance is to simply not block downloads at all actually; we consider that an anti-pattern. It adds no protection whatsoever while substantially increasing risk by lowering the organizational security posture.

      Quite simply, developers will work-around what they consider "braindead policies" to get their job done. Upper management will not intervene nor punish them for delivering on time, etc. Ultimately the only consequence will be that no one will take your team (i.e. those enforcing policies) seriously. We've seen this happen time and time again; it's a version of "shadow IT".

      Instead, you should use pgutil builds scan and then consider these on a case-by-case basis if they are issues: https://guides.inedo.com/vulnerability-management/containment/

      To summarize, the "version dance" isn't realistic to do at the server level, for the reasons articulated above. Even if it were technically feasible, It would create a poor developer experience.

      THAT SAID -- we are considering an experimental approach. ProGet could "auto-yank" noncompliant packages. I'm envisioning something with three options for Noncomplaint packages:

      • Block File Download (not recommended)
      • Emit Deprecated in the API (experimental)
      • Allow Downloads (default)

      Will clients like pip and uv avoid deprecated, newer packages? We aren't users of these tools (or python at all), and we'd love if you could help us "test" this by manually deprecating some newer versions, and see how it handles dependency resoltuion.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: [ProGet] Feature Request/Inquiry: Feed settings when creating using PGUtil/API

      Hi @Nils-Nilsson ,

      That message appears to be coming from SetCommand.cs#L91... is it possible you're not on the latest pgutil (i.e. 2.4.2)?

      That would be my guess...

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Proget as MCP Server Registry/Gateway

      Hi @dan.brown_0128 ,

      Here's our current position on MCP Registries:

      From a quick read of the documentation, it looks like an "MCP Registry" is mostly just a JSON document that lists "MCP Servers". There don't seem to be "Packages" (i.e. an archive file with a manifest file) nor a "Central Repository" (i.e. a canonical location where OSS Models are stored), which means it's not a great fit for ProGet.

      Here's the current discussion on the topic: Request to support MCP registry; I'd encourage you to add your thoughts to that!

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: In what situations is `.AHPARAMETER` expected to do anything?

      Hi @jimbobmcgee ,

      Long story short, "we're not entirely sure anymore."

      You've picked up on the original intent: these are intended to provide UI-based inputs around script parameters. And they do "mostly" show up in the use case you identify (i.e. when creating a Job Template for the first time)... but they are overall a glitchy feature.

      They were also intended to allow for Param()-like support to other scripting languages, so you'd simply need to add that header to the script and it would just "work" in OtterScript and job templates.

      From an engineering standpoint, we had planned to improve all of these after Otter 2022 (when they were first released), but our R&D priorities suddenly shifted. So we haven't had time to revisit them (or other Otter features we wanted to do), and they're basically in that same glitchy state 🙄

      Personally I thought they were a pretty neat idea, and it's just unfortunate we weren't able to take them further. But, so it goes with development priorities...

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: [ProGet] Incorrect package publish date affecting policies

      Hi @amy.j ,

      Looks like the code was actually merged in and shipped, but that status wasn't reflected on the YouTrack issue, so the note didn't get added to the release.

      Anyway I've modified the status and manually updated the release notes now.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Retention Policies for PR Builds

      Thanks @brandon_owensby_2976 , we appreciate the additional context and it makes a lot of sense.

      Just to give you more context on our end on why we aren't changing the software here very much, we aren't focusing very much on "download-try-buy" channel for BuildMaster (i.e. the way you're evaluating the product). Instead, it's sold as the technology to help implement Lean Platforms transformation, which necessities improving the development workflows.

      One thing we'll be releasing as part of BuildMaster 2026 (coming fairly soon) are features to better handle parallel release tracks across multiple applications, including this new calendars feature:

      83bf00df-3a5c-4dcb-a5af-17b12f39a1b6-image.jpeg

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Retention Policy - Ability to have policy run per group (e.g. Application)

      @brandon_owensby_2976 fantastic!!

      Thanks much; I'll let our technical writing team review/accept it, They should within a day or so

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Retention Policy - Ability to have policy run per group (e.g. Application)

      Hi @brandon_owensby_2976 ,

      We can certainly update the documentation; what would you suggest to change?

      https://github.com/inedo/inedo-docs/blob/master/Content/BuildMaster/administration/retention-policies.md

      Feel free to submit a pull request as well :)

      As for how we handle feature requests, it either gets "added to our roadmap" or not. If not, then it just stays "in the ether" until it comes up again.

      When it comes time to plan for a release (e.g. BuildMaster 2027), we choose from items from that roadmap (it's an internal checklist) or shift them to next year.

      After a few shifts, we remove it from the list and goes back "to the ether". Redoing Retention Policies in BuildMaster were on the roadmap for an extremely long time, but there are just so many areas of improvement that kept coming up instead. And that's why it's not on our roadmap now.

      The forums are a great way for users to vote or share ideas, so this someone can always reply to this post in the future.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Retention Policies for PR Builds

      @brandon_owensby_2976 I definitely do not recommend it, but if you are intent on creating something that automatically promotes feature branch builds to a "rejected" stage, you could code a custom PromotionRequirements.

      You'd be much better doing something on the GitHub side that promotes a build using the API, however.

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Retention Policies for PR Builds

      Hi @brandon_owensby_2976 ,

      While it's technically possible to create a custom repository monitor (see the Subversion one), I'm not sure if I'd recommend it for this use case.

      Did you see our guidance here on build clean-up?

      https://docs.inedo.com/docs/buildmaster/builds-continuous-integration/buildmaster-ci-git-workflows/buildmaster-git-feature-branches#cleaning-up-feature-branch-builds-with-retention-rules

      In a feature branch pipeline, a build should still be promoted to a final stage ("merged" or something), and once that happens it's status can be set to Rejected. So, instead of worrying about whether the PR is merged/deleted, just delete rejected builds after X days.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: ProGet license restrictions in CI

      Hi @cyril ,

      Thanks for checking; that would be fine. Note you'll have to enter a license key in your scripts (free is fine), as ProGet will not automatically create a license key.

      Aside from various features missing from Free edition, one restriction is that ProGet Free can't connect to other instances of ProGet. The software will generally enforce this as well.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: [ProGet] Debian connector Components: all creates empty local index for Ubuntu 20.04/22.04

      Hi @daniel.pardo_5658,

      This behavior is somewhat expected.

      I'm not really a Debian expert or anything... but when it comes to a Debian repository index, all is actually the name of a component.

      When we look the index files, we can see:

      • ubuntu-jammy has all components
      • ubuntu-jammy-updates has no all components
      • ubuntu-jammy-security has no all components
      • ubuntu-noble has all components
      • ubuntu-noble-security has all components
      • ubuntu-noble-updates has all components

      I would have thought that any means "any component", but apparently it doesn't. So I guess you have to specify that list if you want it to work.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • 1 / 1