Hi Bohdan, For the feed migration please refer to this: https://inedo.com/support/kb/1168/migrating-a-proget-feed As far as Users/Api Keys.. are you using a Built-In user directory only? Thanks, Jason

Hi Jared, I am glad it is fixed. I will make a note of how you were able to get it resolved! If you notice anything else, let us know. Thanks, Jason

Hi David, It appears that only the start of a statement block shows in the execution log.. # Visible in execution log # This is not bisible in execution log { } # Visible in execution log # This is not visible in execution log { # This is not visible in execution log } # not showing in execution log Let me know if you have any specific examples that aren't working as expected. Here is the full documentation for OtterScript comments https://inedo.com/support/documentation/executionengine/otterscript/comments-and-descriptions Thanks, Jason

Hi Larry, Please refer to this documentation for a list of the ProGet license restrictions.

Hello, This documentation may help you determine the best approach for your solution: https://inedo.com/support/documentation/proget/feeds/nuget#nuget Please let me know if you have additional questions. Thanks, Jason

AllowFunctionAccess_Indicator is an Y/N indicator to allow access to the credential values if they are encrypted.

Hi Paraig, Replication between two different versions will likely work, though it would be a good idea to verify correctness when complete. We try to maintain backwards compatibility though we don't officially support this scenario (by this I mean we don't routinely test replication with older versions). In the event of a problem, another possibility is to replicate to another 4.6.7 instance, and then upgrade it to the latest version.

Hello, Thank you for your question. I want to make sure this gets prioritized properly. Can you submit this as a "ticket" instead? https://inedo.com/support/submit-ticket instead. Thanks in advance, Jason.

Hi David, You can view the results of a monitor that triggers a plan in the Admin > Executions page, filtering by "Build Trigger". You can also add some hack debugging to the plan that logs the built-in monitor variables to a file so you can see if it's triggering. If it's still not triggering, try configuring the monitor to a public instance of something on GitHub like https://github.com/Inedo/git-test.git to see if that works since GitHub supports the SVN protocols as well. Hope this helps, -John

Hi Eyal, What version of ProGet are you using? This was a known issue that should have been fixed in version 5.1 Let me know if this is not that case. Thanks! Jason

Hi Giuseppe, Unfortunately that is not part of our current API but it is a great idea and I would encourage you to complete our feature request process. https://inedo.com/open/feature-requests In the meantime I suggest using the import/export option in buildmaster to clone your applications. Thanks, Jason

Hi Simon, I am unable to recreate this issue. Please check to make sure the path exists at run-time and that the buildmaster agent has permissions to it. You can try to test this with a different path like c:\Buildmaster\rpt\

Brent, This our public Q&A forum, which is used for software technical support; as such, I've edited your message to remove your company and contact information. That said, we help organizations with compliance-related questionnaires on our products all the time, both sales and post-sales. Please reach out to your Inedo account manager or use our contact form, and send whatever security compliance forms/documentation you are trying to fill out, and we will do our best to advise and help.

Hi, We are still discussing this issue internally. I am wondering if the issue could be with the endpoint.. can you change to /nuget/default instead of /feeds/default/nuget Thanks, Jason

As a followup, support for the Portable PDB format in the symbol/source server has since been added to ProGet.

Jon, I haven't found too much on this besides what we already recommended. I did find this option specifically for Import-module : https://stackoverflow.com/a/28512164

Hi Bret, For question #1 - We have just published this documentation for TeamCity: https://inedo.com/support/documentation/buildmaster/builds/external-systems/teamcity This may give you a little more guidance on that subject. For question #2- all of our tutorials are here: https://inedo.com/support/tutorials but this one might be what you are looking for https://inedo.com/support/tutorials/buildmaster/continuous-integration/manage-pipelines-git Thanks, Jason

Apologies, I had seen the StackOverflow post first, so I responded here: https://stackoverflow.com/questions/56338757/proget-symbols-and-source-server-download-pdb-correctly-but-source-not-found/56397293#56397293

Yes. that is correct. I believe there is a plan to add security into the API.

Not sure what was wrong, but I resolved the issue by deleting the temp repo in C:\ProgramData\BuildMaster\Temp\Service\GitWorkspaces and restarting the BuildMaster service.