| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmi:id="-DlaqJu4sEqMPk84qhJ6IEA" name="continuous_integration,_i8bUEL6cEdqti4GwqTkbsQ" guid="-DlaqJu4sEqMPk84qhJ6IEA" changeDate="2006-05-31T15:26:30.329-0700"> |
| <mainDescription><p> |
| [ Don't forget to talk about running developer tests. ] |
| </p> |
| <p> |
| [Content below taken from step “Accept Integrated Elements and Promote Build" in the Task “Integrate and Create |
| Build"... this Main Description needs to be cleaned up ] |
| </p> |
| <p> |
| Depending on the complexity and number of&nbsp;components to be integrated, it is often more efficient to produce the |
| target build in a number of steps, adding more&nbsp;components with each step, and producing a series of intermediate |
| 'mini' builds - thus, each build planned for an iteration may, in turn, have its own sequence of transient intermediate |
| builds. These are subjected to a minimal integration test&nbsp;to ensure that what is added is compatible with what |
| already exists in the system integration workspace. It should be easier to isolate and diagnose problems using this |
| approach.&nbsp; |
| </p> |
| <p> |
| Delivered&nbsp;components are accepted&nbsp;incrementally into the system integration workspace,&nbsp;having any merge |
| conflicts being resolved.&nbsp;It is recommended that this&nbsp;is done in a bottom-up approach with respect to the |
| layered structure, making sure that the versions of the&nbsp;components are consistent, taking imports into |
| consideration. The increment of&nbsp;components is compiled and linked into an intermediate build, which is then |
| provided to the tester to execute a minimal system integration test. |
| </p> |
| <p> |
| <font size="1"><img height="172" alt="" src="./resources/ac_intsy.gif" width="501" /></font> |
| </p> |
| <p> |
| This diagram shows a build produced in three increments. Some&nbsp;components are only needed as stubs, to make it |
| possible to compile and link the other components, and provide the essential minimal run-time behavior. |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |