Thanks @mcascone , I also added this to our "Promotion / Repackaging Visibility & Permissions Rethinking" task - sounds like something we can consider :)

Hi @mcascone , I admit this can be confusing and is unintuitive because these were added separately over time, and the weren't originally designed for how they're used today. We need to rethink/redesign this based on the use cases. I'm going to add this thread under the "promotion/repackaging workflows" topic for our next major version of ProGet. Once we know what we want to do, we can may be able to implement some changes as a preview feature in v6. FYI, this is exactly how the big API Key changes and feed/package usage instructions came about! https://forums.inedo.com/topic/3204/proget-feature-request-api-key-admin-per-user So stay tuned :)

Hi, just wanted to say that i happened to look at the new releases available for v5, and saw that this is fixed in the latest release, 5.3.44. Awesome! Thanks!

Hello Dan, Exactly what I needed. Thank you for the prompt reply! Mikhail R.

I can confirm that its working for us now. Thanks!

Hi @benjamin-soddy_9591, No problem "resurrecting" topics! We definitely want to hear from users about feedback/feature requests. We still haven't had anyone else ask for deprecation since this request, but I wonder if there's a better solution to solving your challenges than this feature. It sounds like you want to increase governance of your NuGet Packages, potentially with some sort of compliance in mind. The dotnet list package --vulnerable is probably not what you want for your organization; NuGet's Built-in Vulnerability Scanning is really limited, in part because it only reports on a fraction of known package vulnerabilities (164 as of today). It also won't block packages that you deem problematic, unlike ProGet's feature. The same is true with dotnet list package --outdated -- it's probably not what you want, because it relies on developers to have to know (1) to run the command, and (2) know what to do if there's an outdated dependency. There are better ways to manage third-party packages (see How to Create a Package Approval Workflow for NuGet), and you'd better served knowing who's consuming outdated packages (see Use Package Consumers to Track Dependencies Just some thoughts; like I said, we haven't had any demand for this feature, but these are proven solutions for improving governance of packages as organizations grow/expand their NuGet usage like you are. Cheers, Steve

Hi @brett-polivka, No problem! We are expecting this fix to be released on Friday. We will let you know if anything changes! Thanks, Dan

Thank you Nanci! The workaround fixed the issue and we will begin the upgrade process. Thanks!

Hi @colin_0011 , that certainly is an odd issue! We've never seen it before, but it's coming from the library we're using (libgit2). I don't really know what it means, or what's causing it (is it a number of files in the repository, etc.), but I just have a couple ideas. Restart server Clear the GitWorkspaces (C:\ProgramData\BuildMaster\Temp\Service\GitWorkspaces) Try using git.exe instead of the built-in library You can do #3 by setting GitExePath parameter on the operation, or configuring a $DefaultGitExePath variable at the server or system level in BuildMaster; this will force all Git source control operations to use the CLI instead of the built-in library It's possible the bug was already fixed in a newer version of the lbirary. What version of BuildMaster are you using?

Conda feeds are now available! https://docs.inedo.com/docs/proget-feeds-python-conda cc/ @stewart-ridgway_3626 @ben-hegarty_7893

Hi @kichikawa_2913, Thanks for following up and letting us know that you found the solution! Thanks, Dan

Hi @mcascone, So this is actually working as expected. We order by the version number itself instead of the upload date, which is why you are seeing that version on the bottom. When ordering, we order first by major, then minor, then patch. So in this case 1-PLATDEV > 1-develop, which is why 2.1.1-develop-2018 drops to the bottom. I believe we have sent this to you before, but just in case we have not. We have created an article for Best Practices for Versioning NuGet Packages in the Enterprise. This goes into a lot more detail on NuGet versioning. Thanks, Dan

Thanks for the insight into your process on this. It's interesting. For our part, I put everything I can on Confluence. I probably like Confluence as much as I hate Sharepoint and OneNote. (At least with OneNote I can actually create a document successfully.) Flow charts help a lot, which are super easy to create and maintain with the Draw.io integration into Confluence. I like confluence for its deep-linking into Jira as well.

Hi @Michael-s_5143, Glad to hear that post helped you out. We updated our documentation to include information about the ASPNETCORE_URLS information. Thanks, Rich

Hi @pwe, Thanks for updating us that you were able to figure this out. I have updated our documentation to include information about changing the internal port number. https://docs.inedo.com/docs/installation-linux-docker-guide https://docs.inedo.com/docs/installation-linux-supported-environment-variables Thanks, Rich

Thanks, I knew this one was a bit of a stretch. It'll be tough if not impossible to automate this in Jenkins, and is another tick on the "check out buildmaster" list.

@rhessinger said in buildmaster linux docker install: sa login failures: @mcascone slope game said in buildmaster linux docker install: sa login failures: docker exec -it inedo-sql /opt/mssql-tools/bin/sqlcmd -S localhost -U SA -P 'redacted' -Q 'CREATE DATABASE [ProGet] COLLATE SQL_Latin1_General_CP1_CI_AS' Hi @mcascone, This line has the issue. You created a database named [ProGet] instead of a database name [BuildMaster] as you stated in the connection string on the third command. Thanks, Rich Thank you very much for the explanation. It works now.

There is a lightweight standard for bom called cyclonedx though (https://cyclonedx.org/). Cyclonedx can be output as either xml or json, which can be consumed in an application such as dependency-track. The problem though, is that dependency-track consumes the bom file and does not keep it. Of course, it's possible to Asset Directory could be used as a bom repository, though pushing files to a git repository might be better in that regard, since it's easier to download the whole repo and compare files.

@Stephen-Schaff thanks! We are planning to rebuild all the users/groups/permissions pages in the coming weeks, so I'll also this as something for us to consider getting in

Hi @Stephen-Schaff, This checkbox will do the latter, i.e. "keep the newest 100 versions in each chart (up to 2,000 charts in total)" :) Note that you can also run retention policies in "dry mode" (it's a setting under Advanced Settings), to see how they would perform. Cheers, Nanci