On 10/5/15, 5:19 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> I think you may not have picked up the full context of the question. If >> you have a repo of framework code, its automated tests need the compiler >> to compile them. Meanwhile repo of compiler code has an automated test >>to >> prove that any change to the compiler can still compile the framework. > >Sounds like you just need to split the compiler tests into two sets and >run in this order: >1. compile the compiler >2. run the non framework compiler tests >3. use the compiler to compile the framework >4. run the framework compiler tests >5. run the framework tests 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? Actually, we’d need two more to produce nighty builds once step 5 is successful. Otherwise a bad compiler nightly could get consumed by someone. What do other’s think? No objection from me if someone has the time to do it. I think we have all the right ant targets so it is just a matter of setting up a different set of jobs. -Alex
