administrators

Private

Posts

  • RE: 500 Error after upgrade

    Hi @stephen.schaff,

    This was actually a regression that has been fixed by PG-3432, which is included in the release we just now deployed. Although it primarily affects docker blob replication, there are also situations where it can prevent blob uploads from other sources as well. If you upgrade to 2026.17, the issue should resolve.

    -Greg

  • RE: Cannot connect to personal github repo on Buildmaster 26

    Hi @naturescenes13,

    I don't think this is actually an issue with BuildMaster and I instead think this is an issue with GitHub itself. Our GitHub implementation is actually implemented against the github.com API spec and not GitHub enterprise. With that said, the APIs we use actually align between both GitHub products. You can see our implementation here: https://github.com/Inedo/inedox-github/blob/master/GitHub/InedoExtension/Clients/GitHubClient.cs

    With that said, I tried to create a username with an underscore and GitHub completely blocks me from that saying it is an unsupported character. The error message I get is Username may only contain alphanumeric characters or single hyphens, and cannot begin or end with a hyphen. My guess is the some of the API's still accept the old usernames and some of them don't (most likely the newer ones). We probably would need to convert the underscore to some other character (like a - or something) to bypass that. Searching around I see this issue on other open source repositories that wrap GitHub's APIs have the same problem.

    Without being able to recreate the issue first hand, I don't feel comfortable trying to apply a fix without the ability to test the fix. Especially since underscores are not a supported character anymore.

    Thanks,
    Rich

  • RE: Expectations of a resource monitor set to "Create a build in a release"

    Hi @brandon_owensby_2976 ,

    Thanks for clarifying; so basically, you stop treating master as the "current release branch" once all the tickets in the sprint are closed. At that point, master becomes the "next release branch".

    If further work is needed later (e.g. fixing a regression discovered by QA), then you create a "current release branch" from the build's commit and use that branch.

    So, in that case, we recommend to mirror the real-world status in BuildMaster by setting the current release's branch to (nothing). Just do that when you create the "next release". That way, it won't match the new commit branch.

    As for creating a script... honestly I'm not really sure. It's just not a use case we've considered and would probably iterating releases with @ReleasesInApplication and doing a $CompareReleaseSequence to find the latest one. Maybe you'd have to psexec to get powershell to write it more naturally.

  • RE: Cannot connect to personal github repo on Buildmaster 26

    Hi @naturescenes13,

    Thanks for the detailed information. Let me run some test's on our side and I will provide an update within the next couple of days.

    Thanks,
    Rich

  • RE: Expectations of a resource monitor set to "Create a build in a release"

    Hi @brandon_owensby_2976 ,

    This is indeed by design. You've got two active releases that are associated with a single branch. So, a commit to that branch will trigger builds in both releases.

    From a best practices standpoint, you should not start new development work on a branch that is being validated for production. If there's an issue detected during testing, fixing that would involve undoing the new work and/or incorporating even more changes in the pipeline.

    Your best bet is to not have multiple releases targeting the same branch. If you want to start on a "new release to start new work" while a current release is in the pipeline, I would just create a branch in Git and work off that.

    Otherwise, I can't think of a work-around here without using some complex/convoluted scripting. There's just no way to programmatically "know" which release the commit was intended for.

    Hope that helps,

    Alana

  • RE: Support for setting Debian feed distribution/components via pgutil / API

    Hi @cyril ,

    We weren't able to get this in the Nov 13 release as you may have noticed; it ended up being a bit more involved. That said, I think that's a good idea, and we will try to incorporate all the "feed-specific" property types as part of this.

    Thanks,
    Alana

  • RE: Cannot connect to personal github repo on Buildmaster 26

    Hi @naturescenes13,

    Can you confirm which version of BuildMaster and the version of GitHub extension you are using? I tested with BuildMaster 2026.4, a classic GitHub PAT, and a personal repository and I'm not seeing any issues.

    Thanks,
    Rich

  • RE: ProGet 2026.16: Docker connector throwing exceptions

    Hi @Nils-Nilsson,

    It is a bug unfortunately. It's logged as PG-3432, and we have a SQL script attached to that issue that will resolve the problem. We will likely do another release soon to include this as well.

    -Greg

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

    Thanks for the heads-up @felfert !

    It looks like this has to do with some kind of change in the base image, though it didn't get spotted in our regression testing; we're aware of the issue now and have already "pulled" the tag.

    We believe we have a fix and hope to address first thing Monday morning.

  • RE: Deleting asset directory fails

    Hi @wechselberg.nisboerge_3629 ,

    It looks like the query is timing out after about thirty seconds. Does that line up with what you've seen? It starts deleting, and then fails?

    Are there a lot of assets in the directory? It could just be a bug/issue with the deletion code for large asset repositories.

    Thanks,
    Alana