Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
MIME-Version: 1.0
Date: Thu, 3 Mar 2016 15:59:45 -0800
Message-ID: 
 <CAKP6k2sU4c_YyCuiLZZmKL_BOAXtXrpV6Q9AvoFa44rFfH93Fg@mail.gmail.com>
Subject: DISCUSS cordova-paramedic
From: Jesse <purplecabbage@gmail.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=001a11c29c9efb9c8e052d2dca68

--001a11c29c9efb9c8e052d2dca68
Content-Type: text/plain; charset=UTF-8

Nikhil and team have expressed interest in using cordova-paramedic for more
of our cordova CI work. This is approach that I explored last year but
ultimately dropped because I couldn't keep up with changes needed to keep
it running as a CI. The main issue I had was that TravisCI could only build
for iOS OR Android, and could not do both.  Similarily, AppVeyor could do
Windows OR Android, but not both.  This lead to tests that looked as if
they had passed, even though changes had been committed to untested
platforms. Given that there is more interest, we can probably find a way to
push through these issues, and have true github integration so we can see
if a pull request is failing tests. I was also not able to get the WP8
emulator running in a CI environment, although this is now not a much of a
concern as it is deprecated. Some stuff is also harder to test in a CI
emulator/simulator, like camera, where some user interaction is needed.

Currently cordova-paramedic is managed through my own repo, although Apache
licenced. This was so that I could iterate quickly, and publish to npm
without going through voting procedures. Given that others will be
committing, I have asked infra to create a new repo [1] for it to live in.
This way we can all commit without legal hurdles.


[1] https://issues.apache.org/jira/browse/INFRA-11371

@purplecabbage
risingj.com

--001a11c29c9efb9c8e052d2dca68--