Support

• 

  NPM package version not available: unsupported archive type
  • maxim_mazurok  

  5
  0
  Votes
  5
  Posts
  9
  Views

  

  Hi @maxim_mazurok, I'm glad to hear that repulling the package fixed this. Do you have an anti-virus installed on your ProGet server? Is it possible to check that to see if the package was quarantined? Thanks, Rich
• J

  pgscan not sending --consumer-package-source
  • jeff.peirson_4344  

  7
  0
  Votes
  7
  Posts
  12
  Views

  

  I've merged this pull request and published v1.0.2 with the change. Thanks for the fix!
• I

  Best way to upgrade Proget from 3.7.6.2 to latest (5.3.33)
  • internalit_7155  

  4
  0
  Votes
  4
  Posts
  22
  Views

  I

  Hello I followed the advised migration path but I found out I had a sqlserver 2005 installed so I had to upgrade it to 2012 at least (the only one compatible with windows 2008R2). The upgrade to 5.2.32 went fine and was confirmed by the installer, just when starting the service it crashes. I had to update the serverurl as described here: https://inedo.com/support/kb/1014/changing-url-with-the-integrated-web-server After that the service started but connecting with a browser the Proget I see a white (empty) page. Is there a log I could check to find out what went wrong?
• P

  BuildMaster Set File Attributes Operation
  • paul_6112  

  4
  0
  Votes
  4
  Posts
  9
  Views

  

  Hi @paul-reeves_6112 , Of course, it should totally work in the usecase you described, I just wanted to explain how it got missed during testing :) In general, we recommend not including configuration files that contain environment-specific configuration in artifacts to begin with, or at least using include/exclude filters on the Deploy Artifact operation. Then, deploying using the configuration files feature. But that's just general advice of course. However, your use case sounds a little different, in that you want the configuration file deployed, but only the first time? I don't have a great solution to that, but the main downside I see is that engineers who manage/edit the configuration file (add values, etc), may be surprised when it's "not deploying" like they expect it to. Config files can be tricky to balance as you probably already know :) Cheers, Alana
• P

  BuildMaster Dark Theme
  • paul_6112  

  4
  0
  Votes
  4
  Posts
  7
  Views

  P

  Hi @rhessinger , Thank you 7.0.6 is much clearer for the log lines :-) Regards, Paul
• P

  BuildMaster Path Browser
  • paul_6112  

  4
  0
  Votes
  4
  Posts
  6
  Views

  P

  Hi @stevedennis , Now tested as working iv 7.0.6 thank you ! Regards, Paul
• P

  BuildMaster Advanced Application Settings Navigation/UI Options
  • paul_6112  

  3
  0
  Votes
  3
  Posts
  8
  Views

  P

  Hi @atripp , Great, thank you ! They are also removed from the Release Overview page. Thanks, Paul
• P

  BuildMaster Proxy Support for Application Templates
  • paul_6112  

  5
  0
  Votes
  5
  Posts
  12
  Views

  P

  Hi @atripp , This is great, thank you :-) Regards, Paul
• L

  ProGet Docker Connector to gcr.io not working
  • liuhan907_8630  

  6
  1
  Votes
  6
  Posts
  48
  Views

  L

  No, this is a new deployment. And health check errors only occur on the connectors of Docker Hub and GCR, while Quay and MCR are work final. At the same time, I can pull the image directly from gcr.io.
• A

  Proget software removed but still showing in hub
  • adrian.leeming_9656  

  4
  0
  Votes
  4
  Posts
  9
  Views

  A

  @atripp said in Proget software removed but still showing in hub: C:\ProgramData\upack\installedPackages.json) Brilliant that did it thank you. It would be nice to have a reinstall/repair.
• 

  Allow login cookies on ProGet to persist across browser restarts
  • hwittenborn  

  2
  0
  Votes
  2
  Posts
  6
  Views

  

  Hi @hwittenborn , I can definitely see how this could get annoying; this has been the design of our products for quite a while, mostly for simplicity/security reasons, and there hasn't been much demand for changing it. We're definitely open, so if other users are interested we'll certainly consider it. Most administrators prefer "short sessions" (i.e. logged out at browser close or with no activity) for their own management simplicity; if we were to add "long sessions" (the "Remember Me" checkbox using persistent cookies), then administrators would need to worry about which users are "logged in", for how long, and terminate those sessions. And then we'd have to add all the features to support that capability - so nontrivial. Best, Steve
• P

  BuildMaster Configuration File Template is not saved
  • paul_6112  

  5
  0
  Votes
  5
  Posts
  9
  Views

  P

  @rhessinger Hi Rich, I've tested 7.0.6-rc.2, this is now saving the template, thankyou. Regards, Paul
• J

  ProGet shows "(500) Server Error: Value cannot be null. (Parameter 'version')" when opening "Dependencies" tab of Maven artifact
  • jndornbach_8182  

  3
  0
  Votes
  3
  Posts
  16
  Views

  J

  @atripp Thank you very much! I upgraded to ProGet version 5.3.32 (Build 11) and the error is gone.
• K

  Cannot push NuGet package to LDAP secured feed.
  • kichikawa_2913  

  3
  0
  Votes
  3
  Posts
  11
  Views

  K

  I thought I did have anonymous View/Download on that feed, I did not. It's working now with the Api Key I set under administration, thank you!
• 

  Run proget container as non root
  • Crimrose  

  17
  1
  Votes
  17
  Posts
  42
  Views

  

  @kichikawa_2913 glad it's working now, you seem to have found the issue. FYI, you can also configure that value from Advanced Settings page under Admin.
• P

  PSCall does not work for script created at application level
  • paul_6112  

  8
  0
  Votes
  8
  Posts
  17
  Views

  P

  @atripp Hi Alana, Sorry for the delay; I had not checked in as I was watching for the v7.0.5 release.. Extension v1.10.5 looks good to me in solving this problem; thank you. Regards, Paul
• J

  [BuildMaster] Release Template Variable Restrictions Clarification
  • jharbison_7839  

  2
  0
  Votes
  2
  Posts
  4
  Views

  

  Hi @jharbison_7839 , We definitely need to update our release template documentation, but in the meantime... The "Allow all variables to be added" option allows you to freely add/edit/remove variable from the Build/Release pages, regardless of restrictions set-up by the Release Template. When it's not checked, only templated variables may be configured. This is not checked by default on new release templates, and prior to v7, there was no ability to edit variables using the template. So, checked = just like it was in v6.2 and earlier, and not checked is temlate-based editing. Alana
• S

  BuildMaster Automated BuildTriggers
  • sbolisetty_3792  

  6
  0
  Votes
  6
  Posts
  7
  Views

  S

  @atripp The links are very helpful... BM always showing the time in UTC...though I updated the server time to be localtimezone. So, the scheduling automatically changes the next run to be in the UTC format... once this is understood, I see that the cron based scheduling is working as expected... Thanks for your help.
• J

  EPERM unlink error with NPM packages
  • Jana.Rebmann_7461  

  7
  0
  Votes
  7
  Posts
  26
  Views

  J

  Hi Rich, I'll try what you suggested, thank you. We tried to upgrade NPM client, unfortunately this will use also a newer version of Node.js which has a different error handling that caused all our unit tests to break. So we skipped that option until all tests are fixed. The issue appears since one year now. It disappeared for 2 or 3 months but always came back. Thanks, Jana
• ?

  ProGet 5.0.x - Semantic versioning
  proget nuget update • • Rene Riedinger  

  5
  0
  Votes
  5
  Posts
  47
  Views

  S

  Hi, Please refer the below blog. You may have an idea on Semantic Versioning. https://www.meritedin.com/robust-api.html Please don't forget to take a look on the videos listed on their playlist.