Continuous integration with SourceSafe source files and batch files

I want to create a continuous integration build system for .NET using only Windows batch files and Visual Source Safe.

I still offer the following batch file -

set ssdir=\\xxxx\vss
cd d:\mydir
"C:\Program Files\Microsoft Visual SourceSafe\ss.exe" diff "$/sourcedir" -R -Q > diffout.txt

This will cause the change to result in lines containing lines, such as “SourceSafe files other than local”.

My task is to find out if these lines are in the file, and then get and run MSBuild, if any. Then I planned to run the batch file every 10 minutes.

Anyone have any thoughts on how to do this? Or any other ways to continuously integrate an assembly without loading a complex assembly automation system?

Update: . We are pleased to use cscript or powershell, although not very familiar with these environments. My main goal is not to install third-party software

+3
source share
3 answers

cmd.exe is a dinosaur. Here is the version of PowerShell.

Set-Alias ss 'C:\Program Files\Microsoft Visual SourceSafe\ss.exe'
Set-Alias msbuild 'C:\Windows\Microsoft.Net\Framework64\v3.5\msbuild.exe'

cd d:\mydir

$diffs = ss diff '$/sourcedir' -R -Q

if ($diffs -match 'SourceSafe files different') {
    msbuild blah
}
+3
source

hudson is not a very difficult task to run. Even I managed to get it to work for a short period of time.

And while you're on it, replace sourcesafe ...

+4
source

- , . , , maven -, .

, , filewatcher, VSS Shadow Folders, MSBUILD.

+2
source

Source: https://habr.com/ru/post/1743279/


All Articles