We require someone with github admin rights to login to both services using 
github account and activate build for cordova-lib repo. The rest of the work 
will be done by the services.

Thx!
Sergey
-----Original Message-----
From: Mark Koudritsky [mailto:kam...@google.com] 
Sent: Thursday, July 17, 2014 5:42 PM
To: dev@cordova.apache.org
Subject: Re: Add build status to github

+1 for running both, Travis and AppVeyor.

What's needed in terms of setting up the hooks on GitHub side? Do we need in 
INFRA ticket for this?


On Thu, Jul 17, 2014 at 6:56 AM, Sergey Grebnov (Akvelon) < 
v-seg...@microsoft.com> wrote:

> I've sent separate PRs for Travis and AppVeyor build configurations:
>         https://github.com/apache/cordova-lib/pull/59
>         https://github.com/apache/cordova-lib/pull/60
>
> #1 Both Travis and AppVeyor use very similar .yml based configuration 
> files which are very easy to use/understand.
>
> #2 AppVeyor showed me Windows specific test failure related to paths 
> so I think we should tun tests on both Linux and Windows
>         https://ci.appveyor.com/project/sgrebnov/cordova-lib/build/1.0.2
>         1) lazy_load module custom method (loads custom cordova libs) 
> local paths for libraries should return the local path, no symlink
>         862   Message:
>         863     Expected '\some\random\lib' to equal '/some/random/lib'.
>
>     * PS. I have more failures on my local machine - will investigate 
> this
>
> #3 Travis build sample
>         https://travis-ci.org/sgrebnov/cordova-lib/builds/30154663
>
> #4 Sample home page with both build badges integrated:
> https://github.com/sgrebnov/cordova-lib/
>
> #5  Pull Requests. Tests are run on both services but github shows 
> information for the only one of them - message is changed as per 
> response from the build service, the last message is showed (not sure 
> how it works if we have failure + then success - to be investigated).
>         https://github.com/sgrebnov/cordova-lib/pull/4
>
> Thx!
> Sergey
> -----Original Message-----
> From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf 
> Of Brian LeRoux
> Sent: Tuesday, July 15, 2014 9:42 PM
> To: dev@cordova.apache.org
> Subject: Re: Add build status to github
>
> I see, it looks like our testing infra is going to be 
> redunant/distributed regardless. (travis + X) No sense in fighting it!
>
>
> On Tue, Jul 15, 2014 at 9:31 AM, Parashuram Narasimhan (MS OPEN TECH) 
> < panar...@microsoft.com> wrote:
>
> > Don't we still need Travis to drive the Saucelabs test?
> >
> > P.S: I have been investigating to see if I could use Appium to run 
> > Medic tests.  No Windows support yet though :(
> >
> > -----Original Message-----
> > From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On 
> > Behalf Of Brian LeRoux
> > Sent: Tuesday, July 15, 2014 9:18 AM
> > To: dev@cordova.apache.org
> > Subject: RE: Add build status to github
> >
> > https://docs.saucelabs.com/reference/status-images/
> > On Jul 15, 2014 9:17 AM, "Brian LeRoux" <b...@brian.io> wrote:
> >
> > > Or we could use SauceLabs (for all) On Jul 15, 2014 9:16 AM, 
> > > "Parashuram Narasimhan (MS OPEN TECH)" < panar...@microsoft.com> 
> > > wrote:
> > >
> > >> We would need both right? For covering Windows and Linux 
> > >> platforms for lib to build/run.
> > >>
> > >> -----Original Message-----
> > >> From: Mark Koudritsky [mailto:kam...@google.com]
> > >> Sent: Tuesday, July 15, 2014 7:55 AM
> > >> To: dev@cordova.apache.org
> > >> Subject: Re: Add build status to github
> > >>
> > >> Ok, let's ask here.
> > >>
> > >> Does anybody have any strong preferences for either AppVeyor or 
> > >> TravisCI or both for cordova-lib?
> > >> note, this is only about running "npm test" in cordova-lib.
> > >>
> > >
> >
>

Reply via email to