Sorry for asking such a basic question, but can anyone provide guidance/steps for creating a BuildMaster V6 application to monitor a source control repository and download/copy all the files from the latest version of the source when there is a checkin?

I have looked at any tutorials that I can find, as well as reading the current documentation; but I seem to be getting lost somewhere (or I'm making it more complicated than it needs to be).

I created this type of application in an older version of BuildMaster (possibly as old as v4), monitoring an on-site TFS server (using the Legacy TFS Extension, I think); and this is still running in v5 of BuildMaster.

We are working on moving our source control to Azure DevOps. I have now installed BuildMaster v6.2.5 (on a different server), which has the ability to monitor an Azure DevOps repository (see this item https://forums.inedo.com/topic/2876/has-anyone-created-a-buildmaster-repository-monitor-for-azure-tfvc), and I would like to create a simple BuildMaster application that is triggered by a checkin to a specific Azure DevOps repository and then does a "build" (download any changes in the repository to a local folder), and sends an email at the end of the process. I don't need a Visual Studio style "build/compile" step, and I don't need integration or testing or any of the other steps.

I would appreciate any suggestions or help, or links to any articles or specific documentation.

Thanks for the update. Looking forward to being able to use this monitor.

I discovered one more error detail. BuildMaster logged an error that it couldn't use the folder (for the "get latest" copy on the build server) because it belonged to a workspace for a different account.

I believe this is because I changed from using a domain account to a local account on the TFS server machine for the TFS connection from the BuildMaster machine.

I deleted the workspace for the previous account. I edited the TFS connection in BuildMaster, entered the account information for the local account that I am now using, and saved it without doing a "Test Connection". Now, everything seems to be working okay.

This installation of BuildMaster has been through many upgrades. Maybe someday I will do a full uninstall and a clean install of the latest version, and build new applications in that version, etc.

If anyone needs to know, I found (and then deleted as needed) the TFS workspaces as follows (this is using TFS 2017 and Visual Studio 2017).

On my workstation with Visual Studio 2017 installed, I ran the "Visual Studio 2017"-"Developer Command Prompt". This opens a command prompt window with all the appropriate environment variables set to allow the "TF" command to be used.

Then, run:
tf vc workspaces /owner:* /computer:* /collection:"http://URL-for-TFS-collection/"
to show all the existing workspaces (this shows username and workstation as well).

To delete an existing workspace, use a command like this (note that this uses the singular form "workspace" where the previous command uses the plural "workspaces"):
tf vc workspace /delete /collection:"http://URL-for-TFS-collection/" WORKSPACE-NAME;USERNAME-for-the-workspace

This will let you know if there are any pending changes in the workspace, and ask if you are sure you want to delete the workspace.

I discovered one more thing.

If I edit the existing source control provider for TFS that I have set up (or if I create a new one) - if I enter the (current, valid) password in the password field and then click "Test Connection", it works, but if I save the provider configuration, open it again and test the connection (with the already saved valid password), it fails with the 401 unauthorized error.

It seems like the provider configuration is not saving the account password, or is saving it incorrectly.

In BuildMaster, the setting for "Proxy.Enabled" was set to enabled; I have tried the setting for "Proxy.BypassOnLocal" set to both true and false with no change.

I also tried both a fully-qualified server name and just the server name in the URL for TFS, but neither changed the result.

In IIS on the TFS server, the IIS log included entries with 401.1 results with a win-32 status of 3221225581. I added the local account that I am currently attempting to use to the Remote Desktop Users group on the TFS server, and then successfully logged in to the server using remote desktop with that local account.

After that, I did get a one-time successful connection from BuildMaster to TFS, but it didn't seem to last. Now IIS on the TFS server is logging 200.0 results from this account when it connects, followed immediately by a 401.1 error with no user account listed in those log entries. BuildMaster still shows a 401 error.

I had BuildMaster version 5.8.3 installed and working correctly. I am using the TFS extension to retrieve the latest files from a TFS2017 repository, and this has also been working fine. The TFS repository is on a different (Windows) server in the same domain as the server with BuildMaster. The TFS extension in BuildMaster was using a domain account to connect to TFS.

I upgraded BuildMaster to v6.0.1, and also added the "TFSLegacy" extension. However, after the upgrade, the TFS "get latest" step stopped working, with something like an authentication or authorization error, I think.

Then I uninstalled the TFSLegacy extension, uninstalled v6.0.1, re-installed v5.8.3, and restored the database from the (v5.8.3) backup that was created by the installation of v6.0.1. Everything seems fine with the applications except that the TFS "get latest" step no longer works.

I have tried re-entering the account information in the SCM provider information, but a "test connection" returns errors like:

Provider error. Could not connect to TFS: Microsoft.TeamFoundation.TeamFoundationServerUnauthorizedException: TF30063: You are not authorized to access [URL for TFS]. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized. at System.Net.HttpWebRequest.GetResponse() at Microsoft.TeamFoundation.Client.Channels.TfsHttpWebRequest.SendRequestAndGetResponse(HttpWebRequest webRequest, WebException& webException)

On the server with BuildMaster, I can open a browser, and connect to the same TFS URL, and successfully log in with the account that I am using for TFS in BuildMaster. I also tried using an account that's local to the TFS server (not a domain account); this also fails with the same error, but that account also works from a browser.

Any suggestions for tracking down the cause of this error?

Product: BuildMaster
Version: 5.8.3

From a Google search, I found this article:
https://inedo.com/support/questions/699
Which led me to:
https://inedo.com/support/kb/1015/running-an-inedo-products-services-interactively

I tried the process in this article, and received an error message that the BuildMaster service could not connect to the SQL Server instance: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections."

I then checked the "SQL Server" service in the Services applet and found that it wasn't running (it was set to Automatic start), so I started it and it started successfully. After that, I was able to successfully start the "BuildMaster Service (INEDOBMSVC)" service from the Services applet.

Now, everything is running fine.

I still need to investigate why the SQL Server service did not start after a reboot.

On a Windows Server 2016 (Standard) server, I upgraded BuildMaster from v5.8.1 to v5.8.3 (the latest available version).

However, now the BuildMaster Service (INEDOBMSVC) will not start. I have tried rebooting the server, but the service still fails after reboot. The only error message that seems to be logged is: "Service cannot be started. The handle is invalid"; attempting to start the service from the Services control panel logs the same error.

The "BuildMaster Web Server (INEDOBMWEBSRV)" service is running fine.

If I open an administrative command prompt and attempt to start the service, using "net start inedobmsvc", I get the following output:
The BuildMaster Service (INEDOBMSVC) service is starting.
The BuildMaster Service (INEDOBMSVC) service could not be started.
The service did not report an error.

I may attempt to rollback to the previous version (I do have a database backup), but any suggestions for troubleshooting or fixing the current installation are welcome.

Product: BuildMaster
Version: 5.8.3

Those 2 steps are working now. I can work on adding back the other steps in the plan/pipeline.

Thanks for your help.

OK. I tried that, and I'm no longer getting the variable error.

Now I'm getting an error:
[...] Use a "for server ..." block to set the server context.

I think I can work on resolving that. If I still encounter errors, I will post another reply later.