gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Gump builds a-la-carte?
Date Wed, 03 Dec 2003 10:31:06 GMT

Since Gump will soon and most likely get a dedicated machine (hurray!) 
we can start using it as a continuous integration tool done on a 
per-commit basis. The really nice things is that every commit would thus 
be validated with the latest commits from elsewhere!

In this case IMHO we should not nag the project mailing list but the 
committer that has done the commit, so he has time to revert or fix it.
Project nags IMHO should be done only from the main Forrest clean-run.

Whaddayathink?

Taken from [1]:
"
Alexandria can be hooked into CVS using the loginfo file. loginfo 
contains scripts which should be run every time a CVS log entry is made 
(loginfo is recommended over commitinfo as commitinfo is called for 
every file committed and loginfo is only called for each log entry). 
Adding Alexandria to this file will allow the module to be built and 
tested everyt ime a change is made to CVS. Alexandria implements a 
simple locking mechanism which means that builds will not take place in 
parallel this stops multiple changes starting multiple parallel builds.
			
# The "loginfo" file controls where "cvs commit" log information
# is sent.  The first entry on a line is a regular expression which must 
match
# the directory that the change is being made to, relative to the
# $CVSROOT.  If a match is found, then the remainder of the line is a filter
# program that should expect log information on its standard input.
#
# If the repository name does not match any of the regular expressions 
in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name ALL appears as a regular expression it is always used
# in addition to the first matching regex or DEFAULT.
#
# You may specify a format string as part of the
# filter.  The string is composed of a `%' followed
# by a single format character, or followed by a set of format
# characters surrounded by `{' and `}' as separators.  The format
# characters are:
#
#   s = file name
#   V = old version number (pre-checkin)
#   v = new version number (post-checkin)
#
# For example:
#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
# or
#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
alexandria build test &

[1] http://jakarta.apache.org/alexandria/legacy/usage.html

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Mime
View raw message