Trigger Builds

Version 1 by Robin Shen
on Dec 24, 2009 08:09.

 
compared with
Current by Robin Shen
on Aug 17, 2010 12:45.

 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 2 changes. View first change.

 h1. Situation
 Project2 uses project1 through Maven or Ivy dependency outside of QuickBuild. When project1 finishes building, trigger project2 just to verify if project1 breaks project2.
  
 h1. Demonstration
 # Switch to [project1|http://demo.pmease.com/build/64.latest/], and hit the run button to build project1.
 # A new build of project1 will be generated, and a new build of [project2|http://demo.pmease.com/build/65.latest/] will also be generated when build of project1 finishes.
  # Switch to [project1|http://demo.pmease.com/dashboard/64], and hit the run button to build project1.
 # A new build of project1 will be generated, and a new build of [project2|http://demo.pmease.com/dashboard/65] will also be generated when build of project1 finishes.
  
 h1. Resolution
 Switch to [step definition of project1|http://demo.pmease.com/setting/steps/execution/64/], a step is defined to trigger project2 after build step of project1 is finished. You may add as many trigger build steps here as you want, or you can arrange the step executin order to trigger other builds in any order.
  Switch to [step setting of project1|http://demo.pmease.com/settings/64/steps], a step is defined to trigger project2 after build step of project1 is finished. You may add as many trigger build steps here as you want, or you can arrange the step executin order to trigger other builds in any order.