Hi Alex, well I was simply assuming that something is generally not setup correctly and that one of them could simply check the reason for this and I was assuming that if we sort out the problem the tests could work fine.
Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Freitag, 28. November 2014 17:55 An: dev@flex.apache.org Betreff: Re: Jenkins builds and general structure of FlexJS/Falcon related project On 11/28/14, 8:29 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >I changed the test runner in falcon to start the flashplayer with a >timeout (currently set to 20 seconds as I asked someone of Infra to >check what the flashplayer is complaining about This is exactly why using builds.a.o for GUI tests is inefficient. You have to ask someone in Infra to tell you want is on the screen! There is a -Dis.jenkins=true option that I think will skip the GUI tests. That was my point in the other thread. If there is a way for the builds.a.o to trust what the built is good without running GUI tests you’ll probably save a lot of time and hassle. >The problem is the build structure of the project in general. > >It contains Falcon as well as FlexJS, unfortunately FlexJS' tests need >ASJS, which in turn needs Falcon. > >So we have sort of a "A --> B --> A" situation here. >If all were split up, we could create a build pipeline like this: > >- build flex-sdk > >- build falcon > >- build asjs > >- build falconjx > >?Each would be a separate project for which jenkins is configured to >execute in exactly this order. I’d like to solve the circularity as well, but ASJS will fail without FalconJX because it uses FalconJX for its tests. Basically, each one currently wants to test against the other. I’ll ponder this a bit more. -Alex
