|
CM Basics offers readers the answers to their configuration management "how-to" questions with tips from the experts, real-life case studies, product reviews and industry news coverage. Subscribe to the CM Basics RSS Feed - 
|
|
Written by Bob Aiello
|
|
Monday, 02 November 2009 15:10 |
 Maven is a popular build framework that is used by many technology professionals to manage large scale java application development. The Apache Maven website (http://maven.apache.org) states that "Maven is a software project management and comprehension tool". Maven builds are based upon a project object model (POM) which is coded in XML. Maven is used to manage a project's build, reporting and documentation from a central place. I have worked with both Maven 1.0.2 and the very popular Maven 2. For this article I used Maven 2.2.1 on RHEL 5.3.
|
|
Last Updated on Wednesday, 04 November 2009 10:36 |
|
Do you need agents? |
PDF |
| Print | |
E-mail |
|
Written by Bob Aiello
|
|
Tuesday, 01 September 2009 11:01 |
 Recently, I worked with a few of my colleagues to implement an Application Lifecycle Methodology (ALM) solution that included a full build infrastructure that provided most of the functionality of a Continuous Integration (CI) server. This was part of a rich and powerful technology solution that managed all aspects of the Software Development Lifecycle. During this effort, I realized that some of my colleagues did not fully grasp the scope and purpose of using a build agent.
|
|
Last Updated on Sunday, 06 September 2009 10:07 |
Running a Makefile from Ant |
PDF |
| Print | |
E-mail |
|
Written by Bob Aiello
|
|
Monday, 31 August 2009 13:05 |
 I recently got an assignment where I needed to run all of my build scripts from Ant. The reason was simply that the ALM solution that I was implementing could only accept build status return codes from an Ant directive. Since the project involved C/C++ all of the build scripts were written using GNU Make. My goal was to be able to execute the Makefile from within an Ant build.xml and receive the return code back in the Ant script. Here is how I approached the solution.
|
|
Last Updated on Sunday, 06 September 2009 10:07 |
Rules With Multiple Outputs in GNU Make |
PDF |
| Print | |
E-mail |
|
Written by Eric Melski
|
|
Tuesday, 04 August 2009 00:00 |
 One problem that Makefile writers sometimes have is the need to write a single rule that produces multiple output files, to accomodate tools that don't fit the standard one-command-one-output model generally assumed by make. The classic example is bison, a parser generator used in crafting compilers and interpreters. Bison takes an input file like parser.i and generates both parser.c and parser.h. The Makefile hacker is left with a dilemna: how do you express this relationship in GNU Make syntax? In this article we'll look at the obvious answer and why it is wrong. Then we'll look at a few alternatives, including the one and only way to truly capture the relationship in GNU Make syntax.
|
Deciphering a “hand-me-down” build |
PDF |
| Print | |
E-mail |
|
Written by Bob Aiello
|
|
Tuesday, 04 August 2009 00:00 |
 The conversation usually starts with my boss calling me into his (or her) office and asking me to help out with a task that has suddenly popped up. Usually, it is a matter of a developer leaving the organization and I need to quickly take over the build engineering that had previously been handled by this developer. If I am lucky, I may get a few minutes to shake hands with the departing colleague (luckier still if I can exchange links via my linkedin profile). But, more often than not, I just inherit a build that may or may not be in very good shape.
|
Installing a Web Application to an Existing IIS Website using Wix3 |
PDF |
| Print | |
E-mail |
|
Written by Jirong Hu
|
|
Tuesday, 04 August 2009 00:00 |
 [Editor's note: this article is a little longer than we usually run in CM Basics. However, build engineers are often thrust into the job of managing and supporting web servers so please take a look at Jirong's excellent article on handling deployment under IIS.]
This article describes a detailed procedure for installing a new web application under an existing IIS website, when Wix3 is used to create the msi file. This can be a common requirement in a large deployment. However, I find it's a lot of work to actually get it done and I hope this article can be useful to many other people like me. A complete set of sample code is also provided.
1 The Requirement
The SFS application I am working on used to have a fixed installation directory under the Default Web Site which is "C:\inetput\wwwroot\SFS". And one day we got a message from our deployment team:
|
|
Last Updated on Monday, 05 October 2009 09:18 |
Descrambling parallel build logs |
PDF |
| Print | |
E-mail |
|
Written by Eric Melski
|
|
Tuesday, 30 June 2009 12:00 |
 One of GNU make's many features allows you to shorten build times by running more than one command at a time. If your dependencies are all correct, or nearly correct, this can give you a significant improvement, and since it's built into the tool you get it "for free". But GNU make's parallel build feature -- often called "dash j mode," after the command-line option that is used to enable it -- is not without drawbacks. The worst of these is that GNU make parallel builds can produce incorrect results if the build dependencies are not sufficiently correct. Fixing that is way outside the scope of this column. But we can do something about the second biggest problem: the scrambled build log. It's not a perfect solution, as you'll see, but it addresses a large portion of the problem, and it's simple to implement.
|
|
Last Updated on Tuesday, 21 July 2009 14:40 |
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
|
Page 1 of 16 |
