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

Hi Mark, This bugfix will be included in v6.1.11 due out this Friday. Thank you for your patience. Thanks, -John

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 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

I fixed this incidentally in this commit: https://github.com/Inedo/inedox-git/commit/325562db2ea5996a1dc559f5997dca49cc9452df The fix is available as of v1.3.1 of the Git(Hub|Lab)? extensions :)

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 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\

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

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.

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

That is great news! feel free to reach out if you have any other issues.

Hi Vijay, please refer to this documentation to better understand file masks in our tools. hope this helps! Thanks, Jason

You are right, the PipelinestageName Variable is correctly set at the build level.. But, it is assigned with the last Pipeline used and it is a little confusing for what I am looking for (for each pipeline step correspond a DB string) Never mind, I will make the DB connection by hand Thank you for the spending time

That's great! Thank you Jhon.

FYI this has been added (in Subversion extension v1.1.0) and the available variables are documented here: https://inedo.com/support/documentation/buildmaster/builds/continuous-integration/source-control/svn#automatic-builds-continuous-integration-with-subversion

Hi Bret, A tutorial for TeamCity is here: https://inedo.com/support/tutorials/buildmaster/teamcity/choosing-specific-artifact-from-teamcity Future note, the TeamCity tutorial may be moved to https://github.com/inedo/inedox-teamcity/wiki as part of a docs re-organization. As for controlling Apache, this is done through the httpd command, which can be executed with an Exec operation in your deployment plans, e.g.: # Deploy to Apache { Exec httpd -k stop; # deploy artifacts... Exec httpd -k start; }

Hello Ali, The agent version is not shown in BuildMaster 5.x's server overview page, but you can view it by going to /administration/service-status and forcing a run of the AgentUpdater executer and then checking the log for something like Connected to localhost:46336 (v39.0.0.2); checking status... (in this case, the agent on localhost is v39.0.0.2, the version of InedoAgent distributed with BuildMaster 5.8.3)

Hi Alex , Thank you for your feedback . I understand better now . Of Course , I will share with you and the community , the way I'm doing when they are correctly setup , tested and approved . Best Regards , Andry

Good catch, that's a bug on the auto-generated versions page. Here is a better statement, which we've had for a while on our BuildMaster Roadmap Page: v4 is semi-retired, which means that we will provide very limited support to v4 users who have not yet upgraded, and will provide assistance in performing upgrades. However, we will no longer ship maintenance releases, patches, or other changes. I emboldened the key part; we're here to help, so please schedule some time with our engineers to help you upgrade. And for reference, please see KB#1151: Upgrading from BuildMaster v3 and v4