Thanks very much for the clarification

Aha, it will also be included in BuildMaster... not sure why I got stuck on Otter. I guess it was on my mind because we just had a maintenance release today :) This feature is also scheduled for BuildMaster v6.1.10 on July 19

Hi Jared, According to the docs - It’s currently not possible to mirror another private registry. Only the central Hub can be mirrored. However, we do support connectors to another repository and are nearing completion on a project for docker replication between ProGet instances. Thanks, Jason

hi Jonathan, can you help me with a test case on the duplicate server issue? Are you trying do an infrastructure import that has the same server name defined twice in the same JSON document?

Hi Tigran, We currently do not support pytest but will take this into advisement and treat this ticket as a feature request Thanks, Jason

Thanks Philipe; all operation documentation is automatically updated within the software once the latest version of the relevant extension is installed (i.e. the Windows extension in this case). The documentation on the website will also get updated with any minor version of the software is released, or the Inedo.SDK is updated. Hope this helps, -Tod

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\