On 3/29/16, 8:09 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Yes they do test against other stuff, but the released versions of them >... In all of your examples are run against released versions. If for >example we would test against the last released version, this would be >fine, but we are testing one unreleased version against another >unreleased version and that's where the Hen-Eg-Problem comes from. Why couldn't we test against a nightly instead of a release? Right now the scripts are testing against a sibling repo, but if we changed it to pull from a nightly would that help? I'd probably still have the Ant builds have the option to pull from a repo as well to save a step when I have a parallel changes going on, but actually our CI builds on apacheflexbuilds are also currently fragile in a similar way: if the main flex-sdk build fails, all the downstream builds fail because they assume they can grab stuff from the flex-sdk workspace. They should probably grab the last successful build as well. I've thought about changing that too, but it isn't high enough on my list. -Alex
