{"id":1911,"date":"2005-09-21T07:08:00","date_gmt":"2005-09-21T07:08:00","guid":{"rendered":"http:\/\/gurkan.wordpress.com\/?p=1911"},"modified":"2017-09-08T03:30:14","modified_gmt":"2017-09-08T03:30:14","slug":"poor-mans-tfs","status":"publish","type":"post","link":"https:\/\/www.havatopraksu.org\/blog\/2005\/09\/21\/poor-mans-tfs\/","title":{"rendered":"Poor Man’s TFS"},"content":{"rendered":"

Last weekend, I sat down and decided to install one of my crappy computer as
\na Source Control and
\n
\nContinues Integration<\/a> machine. What I need is
\nSubversion<\/a> source control and other
\nbits and pieces to have a fully functional
\nSource Control
\nSystem<\/a>.<\/p>\n

I put down my requirements first so that I can measure the quality of my work
\nlater.<\/p>\n

My requirements are:<\/p>\n

    \n
  1. A source control system is necessary to keep track of different
    \n\tprojects.<\/li>\n
  2. Source Control should be browse able with a browser.<\/li>\n
  3. Source code should be colored in browser for easy reading.<\/li>\n
  4. Source Control should be used for different technologies like .NET,
    \n\tJava, PHP, Pearl etc.<\/li>\n
  5. The System should compile the code automatically when there is a change
    \n\tin Source Control.<\/li>\n
  6. The System should deploy the executables to proper servers for further
    \n\ttests.<\/li>\n
  7. The System should run the Nunit tests and reflect the results.<\/li>\n
  8. An Issue tracking system should be exist.<\/li>\n
  9. Issue Tracking system should have a connection to Source Control. So
    \n\tthat each defect can be tracked down in code.<\/li>\n
  10. Development machines should be able to check-in and out the code<\/li>\n
  11. Developers should be warned if tests are not successful.<\/li>\n
  12. Developers should be informed when the defects are assigned to them.
    \n <\/li>\n<\/ol>\n

    After I put down my requirements, I have started to work. First off all, I
    \nhave installed a clean Windows XP Professional on a Celeron 500, 128mb ram, 40gb
    \nHD machine. I have installed IIS, Service Pack 1, and all other updates
    \navailable on     Windows Update<\/a>
    \nsite. .NET Framework 1.1 is also available from the Windows Update.<\/p>\n

    I knew, I was going to use Subversion as the bases of this continues
    \nintegration machine. It is free, open source and easy to install and use. I have
    \ndownloaded latest version from     www.tigris.org<\/a>
    \nand installed without a problem. Don’t
    \nforget to add the subversion\\bin directory to your PATH variable.<\/span> <\/p>\n

    Now, I need to create my repository database. Create a directory called
    \n"Repository" in your C: drive and enter the following command on DOS Shell:<\/p>\n

    C:\\>svnadmin create C:\\Repository<\/span><\/p>\n

    And also to secure the repository with a user id and password, I have changed
    \nconfiguration and added my name and a password to passwd file. I don’t know if
    \nthere is a way to hash the passwords in this file, it looks like so vulnerable.
    \nGo to
    \nC:\\Repository\\conf and open
    \nsvnserve.conf file with your text editor. Uncomment the lines below.<\/span><\/p>\n

    \n[general]<\/span><\/p>\n

    \nanon-access = none<\/span><\/p>\n

    \nauth-access = write<\/span><\/p>\n

    \npassword-db = passwd<\/span><\/p>\n

    Create a new file in the same folder
    \ncalled passwd<\/u><\/b> <\/span>and enter the lines below. This is a user
    \nname  and password pair.<\/p>\n


    \n[users]
    \ngurkan = asdfgh<\/span><\/p>\n

    I also need the Subversion service running all the time so that I don’t have
    \nto login to the machine and start the service manually. To install the
    \nsubversion server as a service I have downloaded
    \n
    \nSvnService<\/span><\/a>
    \nand copied SVNService.exe into Subversion\\bin directory<\/span>. To install the
    \nservice go to DOS shell and enter:<\/p>\n

    C:\\>SVNService -install -d -r C:\\Repository<\/span><\/p>\n

    And to start the service:<\/p>\n

    C:\\>net start SVNService<\/span><\/p>\n

    My first requirement is alright now. I have a fully functional Source Control
    \nSystem. My second requirement was to be able to browse the Source Control over
    \nthe intranet with a browser. So developers don’t need to install another
    \napplication to browse the Source Control. There are couple of choices for
    \nSubversion, I have downloaded     WebSvn<\/a>. WebSVN is
    \na PHP application so I also need the
    \nPHP<\/a> installed and configured to work with IIS. Download the 7.8meg zip
    \npackage. You may need other things later if you want to run MySql like
    \napplications. Extract the package to hard disk and add the directory where the
    \nphp5isapi.dll resides to your PATH variable. You also need to register this dll
    \nin Internet Information Services as an ISAPI filter. Right click on your Default
    \nWeb Site go to properties and ISAPI Filters tab.
    \nAdd php5isapi.dll by clicking
    \nthe Add button. Give the name php for the Filter Name.<\/span><\/p>\n

    I have extracted and copied WebSVN to the inetpub\\wwwroot directory and
    \ncreated an application on IIS on WebSVN directory.
    \nChange the name of the file
    \ndistconfig.inc to config.inc in WebSvn\\include directory.<\/span> I need to adjust couple of
    \nthings in config.inc file. These are:<\/p>\n


    \n\/\/ For syntax colouring, if option enabled…<\/font><\/font><\/p>\n

    \n\/\/My Enscript installation is in
    \nC:\\Enscript1639<\/font><\/p>\n

    \n\/\/Also C:\\Enscript1639\\bin is in PATH<\/font>
    \n<\/font>$config->setEnscriptPath("C:\\\\enscript1639\\\\bin");
    \n\/\/ To configure the repositories by hand, copy the line
    \nbelow, uncomment it and replace the name and path
    \n<\/font>$config->addRepository("Repository", "C:\\\\Repository");<\/font><\/p>\n

    .<\/font><\/p>\n

    .<\/font><\/p>\n


    \n\/\/ — BUGTRAQ —
    \n\/\/ Uncomment this line if you wish to use bugtraq: properties to show links to
    \nyour BugTracker
    \n\/\/ from the log messages.
    \n<\/font>$config->useBugtraqProperties();<\/font><\/p>\n

    When I was reading the file config.inc, I have seen an entry for colouring the
    \ncode. I thought, maybe this thing will make it easier for my third requirement.
    \nIt was requiring an Open Source application called
    \n    EnScript 1.6.3<\/a>
    \n(don’t forget to download dependencies). After a bit of
    \nreading about it I have realised that EnScript is a scripting engine based on
    \nstate definitions to produce colored html outputs. For each file extension you
    \nneed to have a state file in a certain directory to make it colored. As usual
    \nthere was no support for C# and VB.NET. I have found a state file on Sourceforge
    \nfor C# but no luck for VB.NET. You can download this file from
    \n    this link<\/a>. Also need to register the .cs
    \nextension in WebSVN’s config.inc file.<\/p>\n

     \/\/
    \n— COLOURISATION —
    \n\/\/ Uncomment this line if you want to use Enscript to colourise your file
    \nlistings
    \n\/\/ You’ll need Enscript version 1.6 or higher AND Sed installed to use this
    \nfeature.
    \n\/\/ Set the path above.
    \n<\/font>$config->useEnscript();<\/font><\/p>\n

    \n\/\/Register cs extension here<\/font><\/p>\n


    \n$extEnscript[".cs"] = "csharp";<\/font><\/p>\n

    There are also options for diff, gzip and sed (I don’t know what sed is). But
    \nyou need to install     CygWin<\/a> to get these. CygWin is a project to provide Unix
    \nshell tools on Windows 32bit systems. I have fired up CygWin installation and
    \nselected all the packages (that was a mistake). Installation took nearly a day
    \nbecause of the selected modules and all downloaded first before installation.\n<\/p>\n

    You need to provide paths for each application (diff, gzip and sed) in
    \nWebSvn’s config.inc file. It is good because developers can download executables
    \nas a zip file or look for differences between two versions of a file through the
    \nbrowser. This is great, because I have even more functionality than my initial
    \nrequirements and they are certainly very useful to have. Here are the lines in
    \nconfig.inc that you need to uncomment. Also download TAR  from
    \n    here<\/a> to be able
    \nto download an entire folder from WebSVN.<\/p>\n


    \n\/\/ $config->setSVNCommandPath("Path\/to\/svn and svnlook\/
    \ne.g. c:\\\\program files\\\\subversion\\\\bin");
    \n<\/font>$config->setDiffPath("C:\\\\cygwin\\\\bin");<\/font><\/p>\n

    $config->setSedPath("C:\\\\cygwin\\\\bin");
    \n\/\/ For delivered tarballs, if option enabled…
    \n<\/font>$config->setTarPath("C:\\\\Program Files\\\\GnuWin32\\\\bin");
    \n\/\/ For delivered GZIP’d files and tarballs, if option
    \nenabled…
    \n<\/font>$config->setGZipPath("C:\\\\cygwin\\\\bin");<\/font><\/p>\n

    .<\/font><\/p>\n

    .<\/font><\/p>\n

    .<\/font><\/p>\n


    \n\/\/ — TARBALLS —
    \n\/\/ You need tar and gzip installed on your system. Set the paths above if
    \nnecessary
    \n\/\/
    \n\/\/ Uncomment the line below to offer a tarball download option across all your
    \n\/\/ repositories.<\/font>
    \n$config->allowDownload();<\/font><\/p>\n

    Another thing to do is to define the port 3690 for Subversion on Windows XP’s
    \nfirewall <\/span>so that you can access from other developer computers. I kept the scope
    \nto subnet, so only internal network computers with this subnet can access to
    \nSubversion service.<\/p>\n

    To download binary files as zipped you need to add these:<\/p>\n

    \/\/ — FILE CONTENT —
    \n\/\/
    \n\/\/ You may wish certain file types to be GZIP’d and delivered to the user when
    \nclicked upon.
    \n\/\/ This is useful for binary files and the like that don’t display well in a
    \nbrowser window!
    \n\/\/ Copy, uncomment and modify this line for each extension to which this rule
    \nshould apply.
    \n\/\/ (Don’t forget the . before the extension. You don’t need an index between the
    \n[]’s).
    \n\/\/ If you’d rather that the files were delivered uncompressed with the
    \nassociated MIME type,
    \n\/\/ then read below.
    \n\/\/
    \n<\/font>$zipped[] = ".dll";
    \n$zipped[] = ".exe";
    \n$zipped[] = ".class";<\/font><\/p>\n

    After everything set up, I’ve logged in to my developer machine and installed
    \n    TortoiseSVN 1.2.2<\/a> which works with Subversion 1.2.3 and it also claims that
    \nthere is a fix for VS.NET web projects. I have uploaded a small .Net project to
    \nSubversion and browse to http:\/\/xpserver\/WebSvn (xpserver is the machine that I
    \nam setting up for Continues Integration) with Internet Explorer but I have got
    \nan error message. Apparently the IUSR_XPSERVER user didn’t have execute
    \npermission on cmd.exe<\/span> which is used by WebSVN to run Subversion commands.
    \nActually, giving this permission is a security risk but as long as this machine
    \nis in intranet and not accessible from outside, I think it is safe. I set the
    \nexecute permission and it worked like a charm. Now I can access to Subversion
    \nwith Internet Explorer and when I click onto a .cs file it is displayed colored
    \nlike in VS.NET editor. Also when I click onto executables like .dll or .exe, it
    \ndownloads the file zipped. So my requirements 2, 3 and 9 are realised.<\/p>\n

    I have also installed
    \n    BugTracker.NET<\/a> to coordinate issues and bugs in the
    \nprojects. One thing that I want is to hook issues to Source Code Control so that
    \nevery check-in and out process can be traced back to some issues, bugs or
    \nenhancements. When you right click on a folder which is a project checked-out
    \nfrom Subversion with TortoiseSVN, you will see an extra tab called Subversion
    \nproperties. <\/span>Here you can set
    \nbugtraq<\/span> properties. These properties will provide
    \nyou an extra field to enter issue number when you are using TortoiseSVN to
    \ncheck-in the project. This issue number will be a link to your issue tracking
    \nsoftware and this link is visible from WebSvn. Now, that’s what I call
    \nintegration.<\/p>\n

    <\/p>\n

    The bugtraq properties that I’ve used are:<\/p>\n

    bugtraq:label<\/b><\/u>: this is the label for the Issue\/bug number which will appear
    \non TortoiseSVN’s check-in dialogue<\/p>\n

    bugtraq.url<\/b><\/u>: This is the heart of this integration. The URL that you are
    \nproviding is the address of your bug\/issue tracking software with a parameter at
    \nthe end which will be replaced by issue number. So my setting is
    \n
    \nhttp:\/\/xpserver\/btnet\/edit_bug.aspx?id=%BUGID%<\/a>. The parameter %BUGID% will
    \nbe replaced with issue number.<\/p>\n

    bugtraq.message<\/b><\/u>: This will appear in WebSVN with the number linked to your
    \nissue tracking software<\/p>\n

    bugtraq:number<\/b><\/u>: Your issue tracking software may keep the issue sequence with
    \na combination of chars and numbers like IS1, IS2. If you give "true" for this
    \nvariable, only numbers can be entered when you are check-in the code.<\/p>\n

    bugtraq:warnifnoissue<\/b><\/u>: If "true" and the developer did not enter an issue
    \nnumber during the check-in, they will kindly be informed to enter.<\/p>\n

    \n<\/p>\n

    Now the real continues integration part comes. For this purpose, I am using
    \n    Cruise Control.NET<\/a> and
    \n    NAnt<\/a> (with
    \n    NAnt Contribute<\/a>). When there is a change on
    \nregistered projects the code should be checked-out and compiled. This will make
    \nsure that the test environment will always have the latest executables. After
    \ncompilation of the code, testers should get an e-mail or some sort of
    \nnotification about the changes and start testing for that particular change.<\/p>\n

    CruiseControl.NET comes with an easy to follow installation package. It also
    \ninstalls the service and creates Virtual Directory on IIS. Once you install,
    \neverything is ready to use. I have also unzipped NAnt to a
    \nfolder and added NAnt\\bin directory to PATH variable<\/span>.
    \nUnzip NAntContrib and copy bin directory
    \nto NAnt\\bin<\/span>. Download
    \n    this little
    \nproject<\/a> and unzip it to test NAnt installation. Open a dos prompt and get
    \ninto the project folder and enter:<\/p>\n

    C:\\><projectfolder>\\nant<\/font><\/p>\n

    You should get a BUILD SUCCEEDED message on the DOS prompt. If everything is
    \nworking we can change the ccnet.config to register the projects for continues
    \nintegration. Go to C:\\Program Files\\CruiseControl.NET\\server
    \ndirectory and edit ccnet.config<\/b> file. <\/span>Or you can download my copy
    \n    here<\/a>. Please read
    \nthe file and do the necessary changes before you run the Cruise Control service.<\/p>\n

    The port 21234 needs to be added to Windows XPs firewall to
    \nallow access from intranet for the Cruise Control.NET service<\/span>. This
    \nservice will be checked with either CCNet Tray application or
    \n    FireFox CCNet plugin<\/a> from the
    \ndevelopers computer.<\/p>\n

    If you browse to your continues integration computer with IE
    \n    http:\/\/xpserver\/ccnet<\/a> you will see something
    \nlike the below screen shot<\/p>\n

    <\/p>\n

    For the NAnt integration, pleas check
    \n
    \nmy other blog entry<\/a>. I think all my 12 requirements are realised. I am happy
    \nand humble. What is next?<\/p>\n","protected":false},"excerpt":{"rendered":"

    Last weekend, I sat down and decided to install one of my crappy computer as a Source Control and Continues Integration machine. What I need is Subversion source control and other bits and pieces to have a fully functional Source Control System. I put down my requirements first so that I can measure the quality […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[207,213],"tags":[],"class_list":["post-1911","post","type-post","status-publish","format-standard","hentry","category-bilisim","category-english"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p90nFK-uP","jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/posts\/1911","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/comments?post=1911"}],"version-history":[{"count":1,"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/posts\/1911\/revisions"}],"predecessor-version":[{"id":3524,"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/posts\/1911\/revisions\/3524"}],"wp:attachment":[{"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/media?parent=1911"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/categories?post=1911"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.havatopraksu.org\/blog\/wp-json\/wp\/v2\/tags?post=1911"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}