Thanks for the update Dmitry! I have kept somewhat distant from the intricacies of our CI, so I have a few questions.
Do you think we can get Medic running different build variations, like with and without the --browserify flag? Can we have Medic run tests for every pull request and report results back to github so we can see if a pr breaks something? The now long ago original architecture of Medic was designed to support running tests on physical devices that would then report their results back to the url specified url in medic.json. Is this still available? And if so, can we configure test devices to report back to the federated test results server? We have nearly every device here at Adobe, but many are used rarely, we could potentially set them up for use in running tests. This would be especially useful in android land, where every device seems to 'feature' some sort of manufacturer quirk. @purplecabbage risingj.com On Fri, May 22, 2015 at 2:00 PM, Dmitry Blotsky <dblot...@microsoft.com> wrote: > Hi list, > > > > Here are some points of interest regarding the CI: > > - Builds now know what commits went into them > > - Waiting on Infra to configure GitHub repos to send changes our > way so that they will *trigger* the builds (right now they're still > periodic) > > - Windows build recently broke, and here is the JIRA: > https://issues.apache.org/jira/browse/CB-9066 > > - Other JIRAs outstanding, being fixed piece by piece by folks in > the community > > > > Here is this week's report on test failures: > > - 14 on Android OSX (flaky) > > - ~14 on Android Windows > > - ~21 on iOS > > - Windows breaking > > - 0 on WP8 (flaky) > > > > As always, the Medic URI is: http://ci.cordova.io > > > > Kindly, > > Dmitry > >
