Continuous Integration Process

Ξ May 8th, 2008 | → 0 Comments |
∇ Tools | ∇ , , , |

According to this article, a software application can easily be developed in a collaborative environment by using a tool that automatically integrates every developer’s effort daily. This is my favorite way to develop software.

Each successful integration is verified by the execution of an automated build of the complete project (including libraries, binaries and tests). In addition, after building the project you can also execute unit tests and/or integration tests. This enables the developing team to increase the degree of assurance on the implemented functionalities and reduce the time spent in the integration process.

Several softwares to support Continuous Integration development, but I only tried to use two of them:

  • CruiseControl, a potent tool targeted for enterprise development
  • Hudson, an easy to use, simple to configure tool (which I’m currently using with very good results)

 

backtrace… up 1

Ξ March 13th, 2008 | → 0 Comments |
∇ Computer, Software, Work | ∇ , , |

The themes presented in this blog are naturally evolving along with my day-by-day experiences. The last days (or should it be months) have been completely occupied with software developments tasks known as implementation, implementation, and more implementation… I must admit that C/C++ has become my second language.

Closely associated with source code production come the fine “art of debugging”. My favorite debugger is GDB (from The GNU Debugger Project).

Learning something new every day is somewhat of a life’s philosophy for me, and it is with big enthusiasm that I learn more about using GDB. The last example of a lesson learned was: how to use backtrace command to display the trace of the execution stack (which was not new to me), and navigate that same stack using the up and down commands and verifying the parameters passed to each function.

More details can be found in the Program Stack section of the GDB Quick Reference.