Hi All,
I'm building a job chain where we have three types of build; C++, Python
and SQL. These build jobs churn out tarball distributions and will then
kick off downstream unit and integration test jobs which fetch artifacts
from the build jobs as needed using the Copy Artifacts plugin.
The SQL build contains sql to initialize the databases that the C++ and
Python integration test jobs use to set up the databases they run
against. So, the Python integration test jobs require a C++ tarball
(they use some libraries written in C++), a SQL tarball (to set up the
database) and a Python tarball (containing the software and tests to run).
In theory, this should work well in general, but I'm worried about the
case where a code and schema change are checked in as part of a single
subversion revision. This would kick off all three build jobs, but how
can I then make sure that the downstream test-running jobs only pull
compatible tarballs? (ie: they either need to be all before the
schema-change commit, or all after it)
As background, I was planning to use "copy from last successful build"
in the test jobs so that if someone breaks the SQL build (happens too
frequently) the C++ and Python jobs don't all turn red for no real reason.
thanks for any help!
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
