Thanks for the report - I have logged the issue and included it as part of 4.0.8 (BM-1299).

What screen were you on when you clicked the button to re-execute? I can't seem to reproduce this in our testing environment.

I've added this as BM-1297,and it should be fixed in the next maintenance release of BuildMaster (4.0.8).

This should be resolved in v4.2 of the extension: http://inedo.com/buildmaster/extensions/perforce

To change the connection strings in BuildMAster, just edit the *appSettings.config files in the WebApp and Service directories.

As you recommended, I installed .NET 4.5.1 and it fixed it. FYI, the server locale is French (FR_CH). Thank you for your help. Regards,

Everything seems to be back in working order now.

Thanks for this report. This issue has been corrected as of ProGet 2.2.6.

This should work with out issue, too

I don't expect the flip contrast option to be added back. Can you just paste as plain text into Word or use a custom style?

Are you using the embedded/built-in SVN client, or are you pointing at your own svn.exe, and if so, what version is it? That behavior seems odd since BuildMaster explicitly instructs the command line client to ignore these types of errors: https://github.com/Inedo/bmx-subversion/blob/master/Subversion15Provider.cs#L318 As a workaround, I suppose you could run the command line under the same account that BuildMaster runs as and accept the certificate manually as you have likely done with your own account. If you need to accept the certificate as LOCAL SYSTEM, you can follow the steps here under Using LOCALSYSTEM Windows Service to accept it as LOCAL SYSTEM. It's also worth noting that for the non-interactive/trust-server-cert flags to be acknowledged, the hostname of the SSL certificate installed on the server must be the same as the one in the repo URL. Is it possible that your SVN server cert is assigned to an IP address instead of the hostname, or vice-versa perhaps?

Hi, this is a bug in the installer; can you set the AppPool to "Classic". There is in issue in some instances with Integrated pipeline, that will cause this.

Hi Alex My simple response would be. Follow all dependecies. ProGet should get all possible version variations of the dependecies. /Thomas

Thanks, we did not have the user set as "Full". This has solved the problem for us.

Thank you for reporting this. We've investigated the problem and the issue will be resolved in BuildMaster 4.0.7, which should be released very soon.

Hey Tod, Its when we execute the workflow, it hungs after the execution is started. the very first step after it starts, still I kept the work flow going on.. and it took 208mins to execute all the steps which generally shall take not more than 2mins... A simple app pool recycle on the target system takes more than 30mins. I verified the communication with the target system and the agent .. they are working fine... the ports and communication between both the servers is good did the telnet and its responding... I can transfer the data between both the servers using normal copy within seconds... so no network issues. I can see the agents as ready for the target system.

Hi Bryant, This is not supported as of yet, though we do hope to address it in BuildMaster 4.1. It is possible to write your own custom actions... and now that BuildMaster is on .NET 4.0 it wouldn't be so difficult to... query the database for the members of a server group do a Parallel.ForEach on the results, and perform the file transfer in that manner

Just go to Advanced Settings under Admin, change the UpdateCheck_Next value to an empty string, and click Save Changes. That should disable automatic update checking.

We've seen this error pop-up a few times, mostly if the ReleaseNumberScheme was altered on the table directly. This script will get fixed in a future release... but in the mean time... One fix is to purge the offending application or releases causing the problem. To purge releases, you need to use the method Releases_PurgeReleaseData. Of course, that may not be possible, so you can bypass this update script with this: DELETE [__BuildMaster_DbSchemaChanges] WHERE [Script_Id] = 612 INSERT INTO [__BuildMaster_DbSchemaChanges] SELECT '406239826673664', 612, 1, '10-RELNO. UPDATE Sortable Release Numbers v2', GETDATE(), 'N' UNION ALL SELECT '406239826673664', 612, 2, '10-RELNO. UPDATE Sortable Release Numbers v2', GETDATE(), 'N' UNION ALL SELECT '406239826673664', 612, 3, '10-RELNO. UPDATE Sortable Release Numbers v2', GETDATE(), 'N' hope that helps

It should work exactly as if you were running the command yourself as the user configured in the SSH agent in the working directory supplied in the Execute Command Line Action. What BuildMaster version are you running? We have just released 4.0.6 as a beta, but it's very close to becoming our official 4.0 release if you're interested in upgrading to it. Could you try to fully qualify the path to "asadmin" in the build script?