Support

• A

  ProGet 6.0.10. Probable bug in npm?
  • ab.korneev_0401  

  4
  0
  Votes
  4
  Posts
  10
  Views

  

  hi @ab-korneev_0401 , By "debugging", we mean running the ProGet code inside of Visual Studio's "debug mode". That will show the errors let us see quickly how to fix them. I'm afraid it's not easy to identify the problem without it, since it's very likely a bug in the third-party repository you're using. Since it's not possible to provide that information, can you... create a server on AWS LightSail (or similar cloud service) Install the same type of third-party repository software and configure it in same manner upload one or two packages that reproduce the problem verify the problem in ProGet Then, send us the information of the server, and we can look at it through the debug mode
• A

  This topic is deleted!
  • alexpoter02_5776  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• D

  Object reference not set to an instance of an object error with packages from 3rd party connector
  • dm.sidelnikov_5266  

  12
  1
  Votes
  12
  Posts
  53
  Views

  

  Hi @dm-sidelnikov_5266, Glad to hear it! Please let us know if you have any other questions. Thanks, Rich
• 

  ProGet: include a Universal Package feed in a nuget config file?
  • MaxCascone  

  6
  0
  Votes
  6
  Posts
  15
  Views

  

  @mcascone I don't think it's new, but it's just used to specify the dependencies field in the manifest file; I'm thinking, perhaps, it might be similar/identical to the consumes field you added? https://docs.inedo.com/docs/upack-universal-packages-manifest The only thing Inedo tools use it for today is just displaying information in ProGet, on the dependencies tab. That may / may not be helpful.
• S

  Vulnerabilities: finding affected consumers
  proget • • sebastian...  

  9
  0
  Votes
  9
  Posts
  37
  Views

  S

  Hi @stevedennis, having a PackageLicense table would be great for two reasons: a) It would give as the ability to do some reporting on used licenses. b) There are lots of packages that use embedded license files. ProGet already has a feature where we can manually assign the corresponding license to a specific version of a package, but as far as I can tell, this is done by generating a pseudo URL for each package and assigning that URL to the corresponding license. While this does work fine as long as it is done only for a small number of packages, I'm not so sure how it affect usability (and maybe performance) when this is done on a larger scale. Having a separate table that connects packages (or package versions) to specific licenses might be a cleaner way to store and process that information. I'd have to check whether we could give you a dump of our database, but we are only just starting to use ProGet, so there isn't really too much data there yet. The fact that we are new to this is actually the reason we are so interested in reports about licenses and vulnerabilities: We are setting up workflows, etc. and at some point we want to completely block downloads of vulnerable packages or packages that use restrictive/unknown licenses, but before we activate hard filtering rules we want to get an overview on how this would affect products currently in development (so we can adapt our rules or define exceptions). At the moment we are generating data by integrating pgscan to our build pipelines and gathering download statistics for packages (and hope that we will be able to analyze that data in a useful way), so feel free to reach out in a month or so. Maybe we will have enough meaningful data to be of use for you guys by then. Cheers, Sebastian
• A

  API delete command did nothing :/
  • ales.bahnik_2824  

  7
  0
  Votes
  7
  Posts
  16
  Views

  A

  Hi @atripp , after yours testing I found mistake in URL - my URL was without /package/. When I use proper URL to request, package was succesfully deleted. Thank you for quick support and sorry about my novice mistake ;)
• 

  ProGet: move storage paths
  • MaxCascone  

  6
  0
  Votes
  6
  Posts
  21
  Views

  

  Hi @mcascone, Thanks for following up and letting us know this worked! Thanks, Rich
• K

  Permissions only work when set for specific user, not a group (LDAP)
  • kichikawa_2913  

  34
  0
  Votes
  34
  Posts
  54
  Views

  

  Hi @kichikawa_2913, Could you please open another topic for the Selenium.WebDriver.ChromeDriver issue? I think that is unrelated to the authentication issue. Thanks, Rich
• R

  Error trying to upgrade
  • Russell.Kahler_4399  

  6
  0
  Votes
  6
  Posts
  27
  Views

  

  Hi @Russell-Kahler_4399 , It looks like there was an error running the upgrade scripts to v4.7. That would have been a long time ago, and it's hard to guess what it could be, and it'd require a bit of analysis to figure out. I'd recommend migrating to a new instance; you can use Feed Importers in the latest version to pull all the content from your existing instance. It's possible to bypass the errors with inedosql resolve-error --all but I really wouldn't recommend it, since it could lead to more problems. Cheers, Alana
• 

  Proget: retention policy for branches in a package
  proget jenkins retention • • MaxCascone  

  6
  0
  Votes
  6
  Posts
  11
  Views

  

  @mcascone said in Proget: retention policy for branches in a package: This means mybranch and mybranch2 can be reduced to mybranch2. Sorry but wouldn't this be the reverse: *mybranch* will match *mybranch2*? What I mean to say.... because it's an AND conditional, the *mybranch* is effectively ignored. Everything that matches *mybranch2* will also match *mybranch*, but the opposite isn't true. E.g. mybranch1 won't match both conditions. @mcascone said in Proget: retention policy for branches in a package: in this feed, delete matches of 'mybranch', except the latest 3 versions of those matches, which would only impact the versions matching mybranch and leave all other non-matches untouched; Correct. And do note that you can set retention policies to run in dry mode, where nothing is deleted, to verify it's the behavior you want.
• 

  Forum Feature request: default category
  • MaxCascone  

  8
  0
  Votes
  8
  Posts
  10
  Views

  

  It seems to work normally now with the homepage setting to none. The default category is support. So I'm happy! Thanks!
• S

  ProGet Retention Rules: option to keep package statistics
  proget • • sebastian...  

  3
  0
  Votes
  3
  Posts
  7
  Views

  S

  Thanks for clarifying this! I did a test run with a package that has not been downloaded before and it seems you are correct: The total downloads per version (on the "Overview" and "All Versions" tabs) are reset to zero, but the statistics under "Usage & Statistics" seem to be unaffected.
• S

  Can we Migrate Proget to Azure
  • shilpa.christopher_1809  

  2
  0
  Votes
  2
  Posts
  18
  Views

  

  Hi @shilpa-christopher_1809, It looks like this didn't get posted to the Support category and it was missed. Yes, ProGet can be moved to Azure. We actually have a guide on how to move ProGet to Azure. Please let us know if you have any other questions! Thanks, Rich
• M

  BuildMaster with Postgres database
  • marc.ledent_9164  

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  Hi @marc-ledent_9164, BuildMaster requires SQL Server to run and cannot be replaced with PostgreSQL. But, you can use BuildMaster to manage the change scripts for a PostgreSQL database. You will just need to install the PostgreSQL extension and create a PostgreSQL database connection. You can learn more by reviewing our CI/CD for Databases documentation. Please let us know if you have any other questions! Thanks, Dan
• C

  ProGet Extension: Error initializing extensions manager
  • can.oezkan_5440  

  3
  0
  Votes
  3
  Posts
  14
  Views

  

  @can-oezkan_5440 just an update, we plan to ship this in the next maintence release in ProGet as PG-2111
• C

  License blocking vs Vulnerability blocking behaviour
  proget • • claes.hermansson_6271  

  4
  0
  Votes
  4
  Posts
  16
  Views

  

  Hi @claes-hermansson_6271, Great! Our recommend three-feed workflow (unapproved, approved, internal) is similar, and keeps the third-party packages in the first two feeds. This way, you can scan for vulnerabilities much more easily. As I understand it though, to get full coverage the pgscan tool needs to be installed on every build server, and the pgscan publish... command needs to be implemented in every build? This is correct. Dependency resolution is complex and often nondeterministic, so it can only really happen at build-time. Hopefully you can templatize pretty easily :) Cheers, Steve
• J

  NuGet Basic Authentication support
  • jan.primozic_9264  

  3
  0
  Votes
  3
  Posts
  20
  Views

  

  @jan-primozic_9264 thanks for posting the update! Please let us know if you can see a place for us to improve documentation :)
• 

  ProGet: no groupname option
  • MaxCascone  

  3
  0
  Votes
  3
  Posts
  7
  Views

  

  Hi, thanks - yep, it appears that plugin is assuming that field is not null. Good find! There aren't any errors from proget either in the output of the plugin upload in the jenkins console, or in the proget error logs, as far as i can tell. Plugin issue: https://issues.jenkins.io/browse/JENKINS-67923 Thanks again for all your great help!
• K

  "Backup" instances in HA environment unable to connect to Service Messenger.
  • kichikawa_2913  

  9
  0
  Votes
  9
  Posts
  20
  Views

  

  Hi @kichikawa_2913, Good catch! It looks like this is missing from our documentation. I'll work to get it updated this week! Thanks, Dan
• ?

  400 bad request
  proget nuget errors • • john brown  

  4
  0
  Votes
  4
  Posts
  34
  Views

  M

  The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. The main thing to understand is that the 400 Bad Request error is a client-side error. The cause of a 400 error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that's too large. If the server is programmed with a file size limit, then you might encounter a 400 error.