quickfix-developers

[Quickfix-developers] QuickFIX build pages, sneak preview

[<OM...@th...>]

QuickFIX build pages for windows vc6, windows vc7, and linux gcc 2.95.2 can
now be viewed on the public web site.  A Solaris page will be available
soon.  We intend on adding more configurations over time.

This automated build process is made possible by CruiseControl
(http://cruisecontrol.sourceforge.net/).  If you are not familiar with the
concept of Continuous Integration, I strongly suggest you take a look.

The QF build machines are monitoring the CVS repository. They will build
the code, and run all tests whenever they detect changes in the code base.
These pages give a lot of useful information about each build.

The most current builds can be found at:
http://quickfix.thoughtworks.com/cchtml/[windows_vc7].html
http://quickfix.thoughtworks.com/cchtml/[windows_vc6].html
http://quickfix.thoughtworks.com/cchtml/[linux-pgcc-2-95-2].html

I wanted the people on this list to take a look and provide comments before
I create a summary page on the website.

The first you thing you will notice up top is either a large green BUILD
SUCCEEDED or large red BUILD FAILED.  A build will be considered succesful
if it is able to compile, able to pass all of its unit tests, and able to
pass all regression tests.  Each succesful build will have a unique label
(i.e. [windows_vc6].8).

The other sections reported are as follows:

Unit Tests
---------------
Displays how many tests are run and how many failed.  All must pass in a
succesful build.  If any tests fail, a report will be show indicated what
test failed and on which line of code.

Regression Tests
---------------------------
Functional regression tests.  Displays how many tests are run and how many
failed.  All must pass in a succesful build.  Test names are followed by
either a green SUCCESS box or a red FAILURE box.  If a test fails, a
description of either why it failed or which message it failed on will be
displayed.

New Tests
----------------
Works just like regression tests except they do not have to pass in a
succesful build.  These are generally new features in development.

Modifications
-------------------
Complete list of any changes to the repository.  Shows who made changes to
the repository and at what time including check in comments.

Output
---------
Display of the actual console build.  In a failed build, this is where you
will find error messages.

--oren

Re: [Quickfix-developers] QuickFIX build pages, sneak preview

[Mustafa R. <m....@ka...>]

sorry for the stupid question - but where do I find the sources ?
When I browse through CVS I only see 7 month old code - independent
which tag I am using ....

----- Original Message -----
From: <OM...@th...>
To: <qui...@li...>
Sent: Friday, October 11, 2002 3:55 AM
Subject: [Quickfix-developers] QuickFIX build pages, sneak preview


> QuickFIX build pages for windows vc6, windows vc7, and linux gcc 2.95.2
can
> now be viewed on the public web site.  A Solaris page will be available
> soon.  We intend on adding more configurations over time.
>
> This automated build process is made possible by CruiseControl
> (http://cruisecontrol.sourceforge.net/).  If you are not familiar with the
> concept of Continuous Integration, I strongly suggest you take a look.
>
> The QF build machines are monitoring the CVS repository. They will build
> the code, and run all tests whenever they detect changes in the code base.
> These pages give a lot of useful information about each build.
>
> The most current builds can be found at:
> http://quickfix.thoughtworks.com/cchtml/[windows_vc7].html
> http://quickfix.thoughtworks.com/cchtml/[windows_vc6].html
> http://quickfix.thoughtworks.com/cchtml/[linux-pgcc-2-95-2].html
>
> I wanted the people on this list to take a look and provide comments
before
> I create a summary page on the website.
>
> The first you thing you will notice up top is either a large green BUILD
> SUCCEEDED or large red BUILD FAILED.  A build will be considered succesful
> if it is able to compile, able to pass all of its unit tests, and able to
> pass all regression tests.  Each succesful build will have a unique label
> (i.e. [windows_vc6].8).
>
> The other sections reported are as follows:
>
> Unit Tests
> ---------------
> Displays how many tests are run and how many failed.  All must pass in a
> succesful build.  If any tests fail, a report will be show indicated what
> test failed and on which line of code.
>
> Regression Tests
> ---------------------------
> Functional regression tests.  Displays how many tests are run and how many
> failed.  All must pass in a succesful build.  Test names are followed by
> either a green SUCCESS box or a red FAILURE box.  If a test fails, a
> description of either why it failed or which message it failed on will be
> displayed.
>
> New Tests
> ----------------
> Works just like regression tests except they do not have to pass in a
> succesful build.  These are generally new features in development.
>
> Modifications
> -------------------
> Complete list of any changes to the repository.  Shows who made changes to
> the repository and at what time including check in comments.
>
> Output
> ---------
> Display of the actual console build.  In a failed build, this is where you
> will find error messages.
>
> --oren
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>