Hi
just to check that I got It right ° somebody checks in code ° CI build happens --> compile, unit test, ... ° if this is ok, trigger the integration test What I do not get is when the database gets build. but what you can do is the following Whenever the database gets build, write a handshake file if it was ok or not. location for example c:\temp\database\ so the database build project looks like this : ° task 1 : delete all files in c:\temp\database\ ° task 2 : create a file bad.txt in c:\temp\database\ ° task 3: do your current database setup ° task 4 : delete file bad.txt in c:\temp\database\ ° task 5 : create file ok.txt in c:\temp\database\ now whenever an integration test begins, the first task should be check if c:\temp\database\ok.txt exists. if not, do not run the integration build (you can fail this build or do nothing, you can deside) with kind regards Ruben Willems On Thu, Mar 18, 2010 at 10:59 PM, splatteredbits <[email protected]> wrote: > > Project X creates the database, > > in the publisher section, use the ForceBuild publisher for the projects > > holding the integration tests > > > http://confluence.public.thoughtworks.org/display/CCNET/ForceBuildPublisher > > > We have about twenty integration test builds. Each integration test > build has a corresponding build which compiles the code and runs unit > tests. The integration test build gets triggered after every > successful compile/unit test build. > > It looks like using the ForceBuild publisher would change our trigger > from the compile/unit test build to the database build, which we don't > want. We don't want an integration test build to run if the database > build is currently failing. > > To unsubscribe from this group, send email to ccnet-user+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject. > To unsubscribe from this group, send email to ccnet-user+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
