-
I really like continuous integration . Having come from a company that didn't practice it at all (this was a time I used to regularly work 12 to 16 hours a day), I was so happy when I got into a company that actually practiced it. I found it to be a really effective mechanism to ensure that developers...
-
This InfoQ link on pipelined CI got my attention because it was something that I can relate to. The project we're working on used to build on our CruiseControl.NET build server in only three minutes; now it's taking more than 18 minutes to complete. And it's a dual-core 2 GB machine at that...
-
Normally, you don't have Visual Studio installed in build servers. Unless you're using the setup and deployment package which can only be compiled by the IDE executable devenv.exe, that's the time that you install VS. As such, you only have the .NET SDK installed and just uses MSBUILD to...
-
i agree that incorporating code coverage criteria in your build scripts is very restrictive, but you have no choice if your team is just starting out doing tdd or writing plain automated unit tests. how can you force them to learn to write automated unit tests if you will not be pressuring them? without...
-
We still have a job advertisement for a C# developer and one of the requirements is experience in agile software development using T est- D riven D evelopment and C ontinuous I ntegration setup. You can hardly find a .NET company in the Philippines which has this setup so I find it as a reward rather...
-
most of our .NET projects has a database project with three scripts in it, (1) create database script, (2) database shema script and the (3) default data script. for our pre-release, we packaged the database creation with default data in our Installshield project so we made use of the SQLScripts section...
-
coming from a project with number of unit tests in it (hundreds i believe), it's hard to work around our current project without it. we're near the release of the project and we still have 31 unit and integration test cases for the .NET client application. the count does not include my own set of unit...
-
Last week, I was assigned to fix a bug in my first project in my current company. The said application was released months ago and is currently being used by our client. Initially, the fix was just to move a particular line of code just above a conditional statement. I am all set, ready to commit, but...
-
I have been using CruiseControl.NET for a 10 months now and i love it. The only thing that puzzles me is why the java counterpart still does not have a client application like CCTray which just parks at the system tray and gives out build status notifications. The remaining time for the build is currently...
-
it is currently a public holiday today (end of ramadan) and i decided to come to work in the afternoon to do some changes on our build server and subversion repository. you can't really do some changes on the development servers on regular working days since it might cause delays on the developers (this...
-
For a long time now, our Cruise Control .NET dashboard is inconsistently generating NAnt outputs and timings reports. Sometimes, it was generated, sometimes a message of "Please make sure that NAnt is executed using the XmlLogger (use the argument: -logger:NAnt.Core.XmlLogger).". But the docs says when...
-
As we progress on our current project, our unit tests have now reached the thousand mark. Although some are poorly written (some hits the database), our build time has increased past the default NAnt task for CCNET of 10 minutes. It used to build less than 5 minutes and now we have doubled our build...
-
although msdn docs say that the proper format for assembly version is <major version>.<minor version>.<build number>.<revision> i was surprised that our current project is using a different format which is used by the nant build for our continuos integration setup <major version>...
-
i was creating this excel workbook reader module so i referenced the excel com interop assembly which resulted in a failing build in our build server minutes after i commit. the problem is because the said assembly is in my machine's global assembly cache, however, it is not existing in the build server...
-
whenever i have a major change in our projects (e.g. add, remove, rename files), i always try to check if i've broken something by running a nant build locally. everybody here is monitoring our build server and it is a bad impression to break something and hear bart simpson screaming. and the painful...