We have almost similar configuration: 1."Main Build" Job - triggered by SCM, make chekout, compiling code and unit-testing. Output file iz zip archive with application binaries which deployed into build - artifacts directory. 2. "Functional Tests" Job - triggered from upstream "Main Build" job, takes as a parameter path to newly created deployment zip, make functional testing. 3. "Smoke Tests" Job - triggered from upstream "Main Build" job, takes as a parameter path to newly created deployment zip, make smoke testing.
Also, "Main Build" job has configured "promouting builds" section, with promotion defined on downstream jobs completion. Promotion can include email-ext step where you can put anythig you want. On Monday, November 12, 2012 8:53:40 AM UTC+2, Sven Finsterwalder wrote: > > We have one main-job that calls two other jobs with parameters. > The first Job builds the product and the second job does some smoketests. > > The main-job now sends an email with the logoutput. My idea was to get all > logoutput in one log. > > >
