Comments on: Creating Your First Automated Daily Build with Delphi 2007 http://blogs.teamb.com/craigstuntz/2007/10/30/37765/ C# • Delphi • Entity Framework • Functional Programming • InterBase • MVC • .NET • Web Thu, 18 Mar 2010 05:41:36 +0000 http://wordpress.org/?v=2.6.2 By: Craig Stuntz’s Weblog : NDepend Review and Tips http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-9763 Craig Stuntz’s Weblog : NDepend Review and Tips Thu, 24 Sep 2009 19:42:10 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-9763 [...] will be useful to developers and teams who have a functioning continuous integration process (and you should) and want to impose standards on this sort of code which can be checked in to the repository. But [...] [...] will be useful to developers and teams who have a functioning continuous integration process (and you should) and want to impose standards on this sort of code which can be checked in to the repository. But [...]

]]> By: Craig Stuntz http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-3994 Craig Stuntz Tue, 14 Oct 2008 01:23:34 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-3994 Bo Chen Lin: Two words: "Source control." Bo Chen Lin: Two words: "Source control."

]]> By: Bo Chen Lin http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-3993 Bo Chen Lin Tue, 14 Oct 2008 00:55:45 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-3993 >Type msbuild YourProjectName.dproj This wont work on the build machine unless the two machine have identical settings of the IDE. But we can create an .msbuild file for the build machine and it imports the project file .dproj. The problem of this tech is there is not many docs tell you how to overwrite the settings of .dproj to suit the build machine such as paths. We can also specified paths in the .cfg file, but we don't know the priorities of settings in these three files. >Type msbuild YourProjectName.dproj

This wont work on the build machine unless the two machine have identical settings of the IDE. But we can create an .msbuild file for the build machine and it imports the project file .dproj. The problem of this tech is there is not many docs tell you how to overwrite the settings of .dproj to suit the build machine such as paths. We can also specified paths in the .cfg file, but we don’t know the priorities of settings in these three files.

]]> By: Randy Sill http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-3574 Randy Sill Fri, 23 May 2008 18:25:18 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-3574 Automated builds are a must and certainly are not that hard to set up. I'm using NANT and Subversion and have a build script that compiles all required resources, exes, dlls, then creates 3 installation packages and version dates them. I've been meaning to plug cruise control into the build process, but have not yet. One of the best advantages is consistency of the deliverables. As far as components versioning goes, I use a DCC32.cfg file to define the paths to the components a particular project requires. Every project can have different versions of components if required. My build machine only has the command line compiler and any required library files. I've also implemented builds in Virtual Machines which has the benefit of preserving an environment that may be hard to reproduce several years down the road. Automated builds are a must and certainly are not that hard to set up. I’m using NANT and Subversion and have a build script that compiles all required resources, exes, dlls, then creates 3 installation packages and version dates them. I’ve been meaning to plug cruise control into the build process, but have not yet. One of the best advantages is consistency of the deliverables.
As far as components versioning goes, I use a DCC32.cfg file to define the paths to the components a particular project requires. Every project can have different versions of components if required. My build machine only has the command line compiler and any required library files. I’ve also implemented builds in Virtual Machines which has the benefit of preserving an environment that may be hard to reproduce several years down the road.

]]> By: Alister Christie http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-3493 Alister Christie Thu, 24 Apr 2008 02:21:01 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-3493 msbuild was not found when typed at the command prompt. I also didn't have an option for "RAD Studio Command Prompt" - which if I did all would be good. If you have this same problem then you can just run rsvars.bat found in the bin directory, the full path being: C:\Program Files\CodeGear\RAD Studio\5.0\bin Then msbuild should run fine. The batch file just adjusts the PATH environment variable. Alister msbuild was not found when typed at the command prompt. I also didn’t have an option for "RAD Studio Command Prompt" - which if I did all would be good. If you have this same problem then you can just run rsvars.bat found in the bin directory, the full path being: C:\Program Files\CodeGear\RAD Studio\5.0\bin
Then msbuild should run fine. The batch file just adjusts the PATH environment variable.

Alister

]]> By: Joe Mele http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-1611 Joe Mele Sat, 10 Nov 2007 17:03:07 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-1611 Craig, I did one one better. I added the correct values to powershell for Delphi. The advantage of using powershell over and above the standard dos box is significant Joe Craig,

I did one one better. I added the correct values to powershell for Delphi. The advantage of using powershell over and above the standard dos box is significant

Joe

]]> By: Robin van Nooij http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-1312 Robin van Nooij Wed, 07 Nov 2007 07:58:23 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-1312 I'm also using CruiseControl.net, it took some time to get it configured for use with Delphi 5 and 7. But we are now using Delphi 2007 and the configuration was like 1 minute. I like the MS Build task in CC.net, made building an application so easy. I'm also creating my own version update tool. It also allows you to synchronize your build version with the cruisecontrol label. Robin I’m also using CruiseControl.net, it took some time to get it configured for use with Delphi 5 and 7. But we are now using Delphi 2007 and the configuration was like 1 minute. I like the MS Build task in CC.net, made building an application so easy.

I’m also creating my own version update tool. It also allows you to synchronize your build version with the cruisecontrol label.

Robin

]]> By: Bert Derijckere http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-1310 Bert Derijckere Wed, 07 Nov 2007 07:43:52 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-1310 Regarding versioning of components: I have made a simple component installer to easily install/uninstall any component or component pack. I've developped this for my current dayjob because we're upgrading to delphi 2007. To help everyone get all the components installed quickly, I wrote a simple installer/uninstaller. It uses an XML file to specify which path to add to Delphi's library path and/or browsing path, and which BPLs to register. I've even integrated the "big boys" like Raize Componets 3 and 4 and DevExpress 3 and 4. I still need to add DevExpress 6 though. I've built all packages and added BPLs and DCUs to subversion along with the source code. The BPLs en DCUs are registered with Delphi (so everyone uses the same version) and the source is registered in the Browsing Path. Now I still need to figure out how to link all our different projects with the correct version of all these components. I can't really use svn:externals on each project, because the components directory is about 600Mb (With DevExpress, Raize, JEDI, it adds up quite fast) Regarding versioning of components: I have made a simple component installer to easily install/uninstall any component or component pack. I’ve developped this for my current dayjob because we’re upgrading to delphi 2007. To help everyone get all the components installed quickly, I wrote a simple installer/uninstaller.
It uses an XML file to specify which path to add to Delphi’s library path and/or browsing path, and which BPLs to register.

I’ve even integrated the "big boys" like Raize Componets 3 and 4 and DevExpress 3 and 4. I still need to add DevExpress 6 though.

I’ve built all packages and added BPLs and DCUs to subversion along with the source code. The BPLs en DCUs are registered with Delphi (so everyone uses the same version) and the source is registered in the Browsing Path.

Now I still need to figure out how to link all our different projects with the correct version of all these components. I can’t really use svn:externals on each project, because the components directory is about 600Mb (With DevExpress, Raize, JEDI, it adds up quite fast)

]]> By: Michael McCurrey http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-961 Michael McCurrey Wed, 31 Oct 2007 21:21:50 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-961 It is almost trivial now to use CruiseControl.net to do your daily builds, it took me all of 1 hour to get it to work. I wouldn't even fiddle around with want scripts or anything like that anymore. It is almost trivial now to use CruiseControl.net to do your daily builds, it took me all of 1 hour to get it to work. I wouldn’t even fiddle around with want scripts or anything like that anymore.

]]> By: Shawn Oster http://blogs.teamb.com/craigstuntz/2007/10/30/37765/#comment-955 Shawn Oster Wed, 31 Oct 2007 18:48:01 +0000 http://blogs.teamb.com/craigstuntz/2007/10/30/37765#comment-955 Our semi-useful way of doing components is using svn's externals property inside of each project, so we end up with: \project1 \src \components (via externals) Problem is this only works for simple components and not the big boys like Raize, DevExpress or RemObjects and only for automated build machines. I've echoed for years and even during the latest round of betas that there needs to be a unified component packager that ships with Delphi to create component installers. If all components were packaged the same there would be a consistant installation method which could then in turn be scripted and versioned. Our semi-useful way of doing components is using svn’s externals property inside of each project, so we end up with:

\project1
\src
\components (via externals)

Problem is this only works for simple components and not the big boys like Raize, DevExpress or RemObjects and only for automated build machines.

I’ve echoed for years and even during the latest round of betas that there needs to be a unified component packager that ships with Delphi to create component installers. If all components were packaged the same there would be a consistant installation method which could then in turn be scripted and versioned.

]]>