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!

  • Ability to bulk delete SBOMs

    4
    0 Votes
    4 Posts
    12 Views
    atrippA
    @v-makkenze_6348 thanks for clarifying - that's not how we intended to use the feature, but hopefully the ProGet 2024 model will work better. In ProGet 2024, they are called Builds, and Builds have a Release Number. They are also auto-archived, and have a kind of Build Stage. Sorry but I don't yet have screenshots, but there is some documentation: https://docs.inedo.com/docs/proget-sca-builds
  • Small spelling error in image Usage Instructions

    2
    0 Votes
    2 Posts
    7 Views
    atrippA
    @v-makkenze_6348 Thanks, we'll add this to our "final touches" in PG2024 :)
  • Unknown licenses that are known

    2
    2
    0 Votes
    2 Posts
    9 Views
    atrippA
    Hello @v-makkenze_6348 , We're aware of this issue, and it's related to NuGet packages with four-part versions that end in zero, and the way the package is handled behind the scenes. It's a fairly involved/complex issue that we need to fix in a major version -- and we've already done that, in ProGet 2024 :) We expect it to release soon. You'll need to delete the cached package then re-add it. We've tested this exact scenario w/ SCA Builds/Releases. Thanks Alana
  • 0 Votes
    3 Posts
    23 Views
    J
    I'm afraid this is a bit too granular for us now, but it's something we can consider re-evaluating down the line, especially as we will likely want to add specialize permissions for projects, policies, etc. We expect that will happen later in the year, after ProGet 2024's new features get more adoption. We'll see if anyone else requests package-level permissions, etc. Thanks for the feedback, let's see if there is more demand. As for the Advanced, I put a note in ProGet 2024's final touches to address that. Honestly I thought those were only on Debug builds only, but clearly not... thanks for reporting! Glad to hear it is just an UI issue, I was worried users could mess with metadata. Cheers
  • Proget as registry proxy

    2
    0 Votes
    2 Posts
    21 Views
    stevedennisS
    Hi @aharalambopoulos_3520 , ProGet works as a "Private Docker Registry" which seems to be different than a "Docker Hub Mirror". Last time we researched Docker Hub Mirrors, they seemed to be primarily intended to provide image to certain geographic regions (like China) where Docker Hub content would otherwise be restricted. They could also be used to set up a "local mirror" of Docker Hub, but in all cases, it seemed to basically just redirect traffic from the default docker.io URL (or whatever) - so it wasn't intended to be used as "Private Docker Registries". In any case, Mirrors don't seem to be a good fit for ProGet; instead, if you wish to use nginx, we would advise to "privatizing" and "lock" images using sematic tag, so that you can be assured that corp.local/images/nginx is a tested/safe image with tags you control. Best, Steve
  • ProGet SAML group mapping

    5
    0 Votes
    5 Posts
    35 Views
    P
    Thank you very much for the information, we will get in touch with our account manager. We would greatly appreciate having this implemented as we need to manage over 150 users via SAML authentication.
  • apt Package file malformatted

    7
    0 Votes
    7 Posts
    29 Views
    F
    Thank you for taking time to sort this out with me! I greatly appreciate your efforts and will be happy, if this works out well. :)
  • proget 2023 - topology

    5
    0 Votes
    5 Posts
    17 Views
    U
    Hi @atripp , thank you very much.
  • proget 2023 - iis vs internal web

    3
    0 Votes
    3 Posts
    8 Views
    U
    Hi Alana, thank you very much. will do.
  • 0 Votes
    8 Posts
    22 Views
    P
    @atripp Thanks for the fast reply and the bypass. Best regards PhilippeC.
  • Sync BM from OT

    otter buildmaster
    9
    0 Votes
    9 Posts
    24 Views
    atrippA
    Hi @philippe-camelio_3885 , We haven't investigated or changed this code in very many years (especially within the last year), so I wouldn't expect a changed result. Can you try the same troubleshooting steps as above? To find out where the invalid JSON is? Maybe it's comma again? FYI - we use Newtonsoft.Json for both serializing and deserializing (as you can see from error). It's really odd to be generating invalid JSON, but that's what the message is It could be related to an obscure bug, etc. We just have no idea and haven't investigated in past year. Thanks, Alana
  • Unable to upload Debian Package.

    Locked
    15
    0 Votes
    15 Posts
    57 Views
    atrippA
    @frei_zs I'm also replied to your ticket (EDO-10276), but wanted to reply here as well. I'm going to lock this thread after, since it's a different issue. Unfortunately "tar" files are more of a convention than a standard, and not all libraries can read files created with different libraries. We are using one of the most "forgiving" tar libraries (we use four different ones!) in this particular scenario, but maybe aptly conventions aren't forgiving enough? FYI - here is what we're doing with the library public byte[] ReadControlBytes() { using var control = TarReader.Open(this.Control); while (control.MoveToNextEntry()) { if (control.Entry.Key == "./control") { var bytes = new byte[control.Entry.Size]; using var entry = control.OpenEntryStream(); ReadBlock(entry, bytes); return bytes; } } throw new InvalidPackageException("Package does not have a control file."); } We will need to inspect the file and see if we can determine what's wrong, and if it's an easy fix, we'll do it.
  • 0 Votes
    7 Posts
    27 Views
    atrippA
    @hashim-abu-gellban_3562 nice find, correct that was a typo :)
  • Unable to add license to package

    4
    0 Votes
    4 Posts
    17 Views
    atrippA
    Hi @v-makkenze_6348, It's hard to say for sure, but there's clearly some kind of database timeout problem here when running Projects_GetReleaseAnalyzerData . I suppose you could try running that directly, and see if it takes a long time? I suspect the issue is that you have too many active releases. This is a major issue with ProGet 2023's feature -- it was designed with the assumption that users would archive releases, but we've seen thousands in the field. If you have a lot of active releases, this cause some big performance issues. ProGet 2024 auto-archives builds (the new word for releases). Cheers, Alana
  • Proget Python connector to PyTorch Cuda Index

    proget python connectors pypi
    4
    0 Votes
    4 Posts
    12 Views
    atrippA
    Good news @m-karing_2439 , This works in ProGet 2024! More specifically, when rewriting/refactoring the PyPi feed, we added support for this "unconventional" repository - specifically, one that doesn't follow the /simple convention or use any of the JSON/warehouse api. Cheers, Alana
  • Apply License via API

    2
    0 Votes
    2 Posts
    10 Views
    atrippA
    @forbzie22_0253 you can use the same ProGet Free on multiple instances
  • ProGet Enteprise License Update

    2
    0 Votes
    2 Posts
    6 Views
    atrippA
    Hi @scott-wright_8356 , You can ignore that message; not sure how/why it occurred, but the consequence is that the message that the license key was updated wasn't immediately dispatched to the other nodes due to some timint issue. So that means it could take a few minutes for the other nodes to reflect the new license key. We should probably just ignore that error. let us know if you keep seeing "No primary service node has been registered." and we can investigate further. Best, Alana
  • VulnerabilityDownloader fails with error

    8
    0 Votes
    8 Posts
    24 Views
    J
    Looks like success! [image: 1711638528204-cde07fce-746b-406f-8e31-186207661cc6-image.png] Thanks for addressing this so quickly.
  • Timeout in build when running pgscan

    8
    0 Votes
    8 Posts
    24 Views
    ValentijnV
    Hi, I checked again and the number of packages is correct when the build succeeds. Had to run the build 9 times before I had a build that did not give a timeout. Before i counted the number of components in the SBOM but the app itself is also a component and i have two SBOM's so therefore i was missing two packages. I get the feeling that during the failing builds the SBOM is uploaded but not completely processed. So the next build its processed and thats when i see three SBOM's or four if the build succeeds. Still no clue why this is the only build that has these failures, its not our biggest or most complex product. We don't have many builds that contain both npm and nuget packages but there are others. All builds are run at least once a week so the others with two pgscans are ok.
  • Lots of Powershell and Conhost processes

    2
    1
    0 Votes
    2 Posts
    9 Views
    atrippA
    Hi @Justinvolved , This is not uncommon with PowerShell; in general the processes will be closed, but there are enough scenarios with long-running/hanging PowerShell scripts where those processes will report termination but the process will not be terminated. So they can stick around I'd recommend using the Inedo Agent instead, even if it's on the same sever. That gives better process isolation compared to the local agent, and you shouldn't see this behavior for too long. The local agent runs in-process. Cheers, Alana
Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation