Hi, > Yes, that is the correct sequence when starting from scratch or when both > repos have interdependent changes. But for most changes, we don’t need > five distinct steps. Should we have 5 jenkins jobs?
A single job would do it as you can use anttask (or equiv) to run other build scripts. You could use a 3rd build script that uses the other two project build scripts containing these targets: 1) compile and run non sdk compiler tests 2) compile and run sdk compiler tests 3) compile and run sdks tests 4) compile and run both projects (i.e. targets 1-3) 5) make binaries 6) compile both projects and make binaries (i.e. targets 4 and 5) If I was setting it up in Jenkins could either just run target 6 or make 5 jobs each run a single target and have each job depend on the previous being successful. It depends to you if you want the dependancies in an ant script or in jenkins, but given this is dependancy related then maven may be better suited for the job. In the currently environment I'd probably go for it being in the build scripts as that is under version control rather than having multiple Jenkin jobs. Thanks, Justin
