Even worst, when the slow build is actually triggered, the sources is
not updated. It is triggered on some previous source version.
Scenario :
initial state :
Fast build last run on source version 10.
Slow build last run on source version 10
action :
I commit source version 11.
consequence :
Fast build update to source 11 and run.
When fast build finishes successfully, slow build starts but on source
version 10 instead of 11.
2007/11/14, Etienne Charignon <[EMAIL PROTECTED]>:
> I setup a configuration with two projects, a fast build triggering a
> slow build, using the command
> project.triggered_by = [SuccessfulBuildTrigger.new(project, "fast_build")]
>
> as follow :
> Project.configure do |project|
> case project.name
>
> when 'fast_build'
> project.build_command = 'ruby run_fast_build.rb'
>
> when 'slow_build'
> project.triggered_by = [SuccessfulBuildTrigger.new(project,
> "fast_build")]
> project.build_command = 'ruby run_slow_build.rb'
>
> else raise "Don't know what to build for project #{project.name.inspect}"
> end
> end
>
>
> This worked very well on the first launch but then I committed new
> changes while the slow_build was running. The fast build detected it,
> run it and finished before the end of the slow_build. At the end of
> the slow_build, it has not been triggered on the new source version.
>
> Etienne
> --
> Étienne Charignon
> http://etienne.charignon.free.fr
>
--
Étienne Charignon
http://etienne.charignon.free.fr
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
