@stevedennis

Should the text not say something like

There are no active builds...

Hi,

I clicked most builds but just can't find it.
Recently we deleted all projects and started anew using fullbuild numbers as SBOMS's started to accumulate for our quarterly releases. (not all projects have been changed yet though)

Anyway I uploaded ProGetVicrea.zip

Thanks for having a look.

Valentijn

We are using Version 2024.11 (Build 10)

In this screen it reports that a non-compliant license is in use in active releases.
But how can i find out which one and where?
We have dozens of projects and hundreds of builds but i can't seem the find it

I did a "Pull to ProGet" and ran analyze again and now the warning is gone.

Downloading the package did not help.

I'm pretty sure it was already in the cache, we clean the nuget cache on our buildservers weekly and everything is downloaded through Proget. The package downloads section shows the downloads.

There are a number of packages that show up with a compliance warning like this one

But when I look at the package it says everyting is ok

Thanks I made a backup and ran the script and it did clean up quite a few rows.
I'll try upgrading to 2024 again next week after we released :)

Strange that you can't see VicreaNeuronGegevensmagazijnContracts, I can't find bootstrap.less

VicreaNeuronGegevensmagazijnContracts indeed had a four part version number.
We deleted al versions of the package as the last download was in 2018.

I see these two warning in Diagnostic Center

The package is not cached or local to any feed; cannot determine if Unlisted.
The package is not cached or local to any feed; cannot determine if Deprecated.

But Details says none so I have no idea which package is causing this.

I uninstalled and installed the previous version, so we can build again.
Think the downgrade dropdown was empty because we got an IIS error at the end of each upgrade, maybe that's solved now too.

Hi,

I upgraded to 2024 and now I get errors in our builds and Visual Studio

Visual Studio simply says "Object reference not set to an instance of an object" and I can't browse for packages.

NuGet during the build gives a big stacktrace.

##[error]The nuget command failed with exit code(1) and error(Failed to retrieve information about 'NeuronTenantAuthenticationHttp' from remote source 'https://packages.vicrea.nl/nuget/Vicrea/FindPackagesById()?id='NeuronTenantAuthenticationHttp'&semVerLevel=2.0.0'.
  Object reference not set to an instance of an object.
NuGet.Protocol.Core.Types.FatalProtocolException: Failed to retrieve information about 'NeuronTenantAuthenticationHttp' from remote source 'https://packages.vicrea.nl/nuget/Vicrea/FindPackagesById()?id='NeuronTenantAuthenticationHttp'&semVerLevel=2.0.0'. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at NuGet.Protocol.RemoteV2FindPackageByIdResource.BuildModel(String id, XElement element)
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
   at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
   at NuGet.Protocol.RemoteV2FindPackageByIdResource.<>c__DisplayClass23_2.<<FindPackagesByIdAsyncCore>b__0>d.MoveNext()
...

When I browse to the url I get a lot of info back, not sure why the query starts at version 2.0.0
https://packages.vicrea.nl/nuget/Vicrea/FindPackagesById()?id='NeuronTenantAuthenticationHttp'&semVerLevel=2.0.0

I tried to downgrade but the version dropdown is empty.

Kinda stuck for now

I upgraded to 2024 and now I have these errors during analysis

ERROR: 2024-04-21 14:38:08Z - Unhandled exception analyzing pkg:nuget/VicreaNeuronGegevensmagazijnContracts pkg:nuget/VicreaNeuronGegevensmagazijnContracts@17.2.65 in Vicrea feed: 547`16`0`FeedPackageVersions_SetAnalysis`26`The INSERT statement conflicted with the FOREIGN KEY constraint "FK__FeedPackageAnalyses__FeedPackageVersions". The conflict occurred in database "ProGet", table "dbo.FeedPackageVersions".

The workaround for now is to restart the IIS application pool and start the proget service through the website.

Hi,

We are running Proget within IIS as the root project but we get this error each time we upgrade. Been working around it for a time but would like to fix it.

Any tips on how to solve this?

** Ensure ASP.NET Core Module is installed **

** Ensure IIS Site: $ProductName does not exist **
 DEBUG: Looking for Site "ProGet"...
 DEBUG: Does not exist. Creating...
 ERROR: You must specify binding information when creating a site.

ERROR: You must specify binding information when creating a site.

For most of our products we work with four releases a year and have many builds so the SBOM's add up.

We also have a cloud product where we deliver continously and used the buildnumer as Proget 'release' but then the number of releases got unwieldy. We fixed release number to 1.0 but then SBOM's add up again.

What i'm really looking for is a way to refresh the SBOM's for a release.

I like to keep the old releases (as we call them) so we see progress

Hi,

I have some unresolved issues like this

But when I look at the package is says it has a license

Using Version 2023.32 (Build 3)

After deleting a lot of SBOM's and running sp_updatestats on the database the timeout is gone (for now) but the Object reference errors are still there.

Hi,

I'm running into some timeout issues during release analysis so I wanted to reduces the number of imported SBOMs but you can only delete one at a time. A bulk delete action would be nice or a feature in pgscan to replace an SBOM instead of adding more and more each build.

Version 2023.32 (Build 3)