We could use SNAPSHOT versions of the SDK ... yes ... these could be built with the nightly build Job.
When thinking about Maven you really have to stop thinking about "downloading nightly builds" and stuff like that. Maven has it's dependency resolution mechanism for that. But if we would be building everything on the ASF Jenkins, we could auto-publish the SNAPSHOT versions and use them in the other builds. The cool thing is that for the FDK dependencies I'm actually currently using my maven-converter to auto download and mavenize the FDKs so these tests are currently all passing. But running the tests against ASJS 0.5.0 sounds like it will be guaranteed to fail. Chris ________________________________________ Von: Alex Harui <[email protected]> Gesendet: Dienstag, 29. März 2016 17:27 An: [email protected] Betreff: Re: AW: AW: [DISCUSS] How about bringing Falcon and ASJS together? On 3/29/16, 8:09 AM, "Christofer Dutz" <[email protected]> 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
