You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com> on 2014/06/27 11:49:32 UTC
Add build status to github
Hi,
I propose to add integration w/ travis-ci to automatically run CLI and LIB tests for new commits and pull requests. In this case we will be more confident that the code is healthy and well formatted. Adding more spec tests will make this even more helpful.
We can do the same for the platforms. Adding unit and e2e tests could be very helpful. As an example, here is simple configuration which can test changes in cordova-windows repo for build using the latest available CLI (platform add, prepare, build)
* Example usage: https://github.com/vladimir-kotikov/cordova-windows/pull/2
* Detailed log: https://ci.appveyor.com/project/vladimir-kotikov/cordova-windows/build/1.0.4
Thx!
Sergey
RE: Add build status to github
Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
My reasoning is to catch error that we may introduce due to concatenating paths, CRLF endings etc.
-----Original Message-----
From: Parashuram Narasimhan (MS OPEN TECH)
Sent: Tuesday, July 15, 2014 9:09 AM
To: dev@cordova.apache.org
Subject: RE: Add build status to github
We would need both right? For covering Windows and Linux platforms for lib to build/run.
-----Original Message-----
From: Mark Koudritsky [mailto:kamrik@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.
Re: Add build status to github
Posted by Jesse <pu...@gmail.com>.
Very nice, updated my fork, and I now see tests passing!
Great work Sergey, Mark, and Daniel!
@purplecabbage
risingj.com
On Mon, Jul 21, 2014 at 2:01 PM, Mark Koudritsky <ka...@google.com> wrote:
> It works now! Added AppVeyor badge to README. Thanks to Daniel Gruno from
> the Apache INFRA team.
>
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
It works now! Added AppVeyor badge to README. Thanks to Daniel Gruno from
the Apache INFRA team.
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
Travis builds are up and running here
https://travis-ci.org/apache/cordova-lib/builds
For AppVeyor there is some problem (might be permissions, details in
INFRA-8066 <https://issues.apache.org/jira/browse/INFRA-8066>).
Sergey, did you have to check some special check boxes on AppVeyor to make
the app public?
I can see full info about your app builds at
https://ci.appveyor.com/project/sgrebnov/cordova-lib/history
​
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
Created an INFRA ticket for this
https://issues.apache.org/jira/browse/INFRA-8066
On Sat, Jul 19, 2014 at 4:42 AM, Sergey Grebnov (Akvelon) <
v-segreb@microsoft.com> wrote:
> Tests are now green on both Linux (Travis) and Windows (AppVeyor).
> Thx Mark!
>
> -Sergey
> -----Original Message-----
> From: Mark Koudritsky [mailto:kamrik@google.com]
> Sent: Friday, July 18, 2014 11:13 PM
> To: dev@cordova.apache.org
> Subject: Re: Add build status to github
>
> I didn't.
> I guess we also need to provide the INFRA people with some short
> instructions on how to enable this on the AppVeyor site.
>
>
> On Fri, Jul 18, 2014 at 2:48 PM, Jesse <pu...@gmail.com> wrote:
>
> > awesome!
> > Has anyone created an INFRA ticket for adding the github service hooks?
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Fri, Jul 18, 2014 at 11:36 AM, Mark Koudritsky <ka...@google.com>
> > wrote:
> >
> > > The test failure on Travis is in plugman/install spec. It seems to
> > > only happen with a fresh checkout, once you run the test second
> > > time, it works ok. I was bitten by this before. Maybe something with
> > > bad management of temp dirs. I'll investigate.
> > >
> > > For now just removing that spec file "fixes" the build on Travis:
> > > https://travis-ci.org/kamrik/cordova-lib/builds/30291305
> > >
> > > The build is with .travis.yml with
> > > before_install: cd cordova-lib; rm spec-plugman/install.spec.js
> > >
> >
>
RE: Add build status to github
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
Tests are now green on both Linux (Travis) and Windows (AppVeyor).
Thx Mark!
-Sergey
-----Original Message-----
From: Mark Koudritsky [mailto:kamrik@google.com]
Sent: Friday, July 18, 2014 11:13 PM
To: dev@cordova.apache.org
Subject: Re: Add build status to github
I didn't.
I guess we also need to provide the INFRA people with some short instructions on how to enable this on the AppVeyor site.
On Fri, Jul 18, 2014 at 2:48 PM, Jesse <pu...@gmail.com> wrote:
> awesome!
> Has anyone created an INFRA ticket for adding the github service hooks?
>
> @purplecabbage
> risingj.com
>
>
> On Fri, Jul 18, 2014 at 11:36 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > The test failure on Travis is in plugman/install spec. It seems to
> > only happen with a fresh checkout, once you run the test second
> > time, it works ok. I was bitten by this before. Maybe something with
> > bad management of temp dirs. I'll investigate.
> >
> > For now just removing that spec file "fixes" the build on Travis:
> > https://travis-ci.org/kamrik/cordova-lib/builds/30291305
> >
> > The build is with .travis.yml with
> > before_install: cd cordova-lib; rm spec-plugman/install.spec.js
> >
>
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
I didn't.
I guess we also need to provide the INFRA people with some short
instructions on how to enable this on the AppVeyor site.
On Fri, Jul 18, 2014 at 2:48 PM, Jesse <pu...@gmail.com> wrote:
> awesome!
> Has anyone created an INFRA ticket for adding the github service hooks?
>
> @purplecabbage
> risingj.com
>
>
> On Fri, Jul 18, 2014 at 11:36 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > The test failure on Travis is in plugman/install spec. It seems to only
> > happen with a fresh checkout, once you run the test second time, it works
> > ok. I was bitten by this before. Maybe something with bad management of
> > temp dirs. I'll investigate.
> >
> > For now just removing that spec file "fixes" the build on Travis:
> > https://travis-ci.org/kamrik/cordova-lib/builds/30291305
> >
> > The build is with .travis.yml with
> > before_install: cd cordova-lib; rm spec-plugman/install.spec.js
> >
>
Re: Add build status to github
Posted by Jesse <pu...@gmail.com>.
awesome!
Has anyone created an INFRA ticket for adding the github service hooks?
@purplecabbage
risingj.com
On Fri, Jul 18, 2014 at 11:36 AM, Mark Koudritsky <ka...@google.com> wrote:
> The test failure on Travis is in plugman/install spec. It seems to only
> happen with a fresh checkout, once you run the test second time, it works
> ok. I was bitten by this before. Maybe something with bad management of
> temp dirs. I'll investigate.
>
> For now just removing that spec file "fixes" the build on Travis:
> https://travis-ci.org/kamrik/cordova-lib/builds/30291305
>
> The build is with .travis.yml with
> before_install: cd cordova-lib; rm spec-plugman/install.spec.js
>
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
The test failure on Travis is in plugman/install spec. It seems to only
happen with a fresh checkout, once you run the test second time, it works
ok. I was bitten by this before. Maybe something with bad management of
temp dirs. I'll investigate.
For now just removing that spec file "fixes" the build on Travis:
https://travis-ci.org/kamrik/cordova-lib/builds/30291305
The build is with .travis.yml with
before_install: cd cordova-lib; rm spec-plugman/install.spec.js
Re: Add build status to github
Posted by Shazron <sh...@gmail.com>.
Yes, only INFRA ppl have the privileges on Github to add anything to the repos.
On Thu, Jul 17, 2014 at 4:20 PM, Parashuram Narasimhan (MS OPEN TECH)
<pa...@microsoft.com> wrote:
> We would need to raise an INFRA ticket for this, right ?
>
> -----Original Message-----
> From: Sergey Grebnov (Akvelon) [mailto:v-segreb@microsoft.com]
> Sent: Thursday, July 17, 2014 6:53 AM
> To: dev@cordova.apache.org
> Subject: RE: Add build status to github
>
> 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:kamrik@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-segreb@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.leroux@gmail.com [mailto:brian.leroux@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)
>> < panarasi@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.leroux@gmail.com [mailto:brian.leroux@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)" < panarasi@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:kamrik@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.
>> > >>
>> > >
>> >
>>
RE: Add build status to github
Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
We would need to raise an INFRA ticket for this, right ?
-----Original Message-----
From: Sergey Grebnov (Akvelon) [mailto:v-segreb@microsoft.com]
Sent: Thursday, July 17, 2014 6:53 AM
To: dev@cordova.apache.org
Subject: RE: Add build status to github
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:kamrik@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-segreb@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.leroux@gmail.com [mailto:brian.leroux@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)
> < panarasi@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.leroux@gmail.com [mailto:brian.leroux@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)" < panarasi@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:kamrik@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.
> > >>
> > >
> >
>
RE: Add build status to github
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
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:kamrik@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-segreb@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.leroux@gmail.com [mailto:brian.leroux@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)
> < panarasi@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.leroux@gmail.com [mailto:brian.leroux@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)" < panarasi@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:kamrik@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.
> > >>
> > >
> >
>
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
+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-segreb@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.leroux@gmail.com [mailto:brian.leroux@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) <
> panarasi@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.leroux@gmail.com [mailto:brian.leroux@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)" <
> > > panarasi@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:kamrik@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.
> > >>
> > >
> >
>
RE: Add build status to github
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
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.leroux@gmail.com [mailto:brian.leroux@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) < panarasi@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.leroux@gmail.com [mailto:brian.leroux@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)" <
> > panarasi@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:kamrik@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.
> >>
> >
>
Re: Add build status to github
Posted by Brian LeRoux <b...@brian.io>.
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) <
panarasi@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.leroux@gmail.com [mailto:brian.leroux@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)" <
> > panarasi@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:kamrik@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.
> >>
> >
>
RE: Add build status to github
Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
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.leroux@gmail.com [mailto:brian.leroux@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)" <
> panarasi@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:kamrik@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.
>>
>
RE: Add build status to github
Posted by Brian LeRoux <b...@brian.io>.
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)" <
> panarasi@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:kamrik@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.
>>
>
RE: Add build status to github
Posted by Brian LeRoux <b...@brian.io>.
Or we could use SauceLabs (for all)
On Jul 15, 2014 9:16 AM, "Parashuram Narasimhan (MS OPEN TECH)" <
panarasi@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:kamrik@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.
>
RE: Add build status to github
Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
We would need both right? For covering Windows and Linux platforms for lib to build/run.
-----Original Message-----
From: Mark Koudritsky [mailto:kamrik@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.
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
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.
RE: Add build status to github
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
I will definitely happy to help here if we all agree to proceed with AppVeyor for cordova-lib. I personally think that for LIB and CLI it is enough to run tests on Travic only. Using two different build configurations (Travis for osx + AppVeyor for windows) could be an overkill.
But I still think that using AppVeyor for a WP8 + Windows8 quick test for incoming pull requests is a good idea. Same with Travis for iOS and Android. The great benefit here in comparison to Medic is that we can quickly run some tests for pull requests.
Thx!
Sergey
-----Original Message-----
From: Mark Koudritsky [mailto:kamrik@google.com]
Sent: Monday, July 14, 2014 11:55 PM
To: dev@cordova.apache.org
Subject: Re: Add build status to github
Sergey, can we set up AppVeyor to run the "npm test" of cordova-lib?
If yes, it would be an excellent option - we will have cordova-lib jasmine tests running on windows, which otherwise happens rarely for all of us who develop on Mac or Linux.
On Mon, Jul 14, 2014 at 2:54 PM, Jesse <pu...@gmail.com> wrote:
> We should just use Travis for quick sanity check tests.
>
> re: integration testing
> Getting into all the other build+test options is too close to Medic.
> Unless we plan to abandon Medic, we should focus on getting
> Medic+BuildBot working perfectly across all platforms, then possibly
> even reporting back to github on every commit.
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Jul 14, 2014 at 7:16 AM, Sergey Grebnov (Akvelon) <
> v-segreb@microsoft.com> wrote:
>
> > Tests on Windows:
> > I've compared Wercker and Appveyor and as for me it looks like
> > Appveyor
> is
> > a better option to proceed for Windows since 1. Wercker's existing
> > windows boxes doesn't support building of Windows
> > 8.1 and WP 8.1 apps due to absence of Windows 8.1 and WP 8.1 SDKs on
> > the boxes.
> > 2. Appveyor supports above
> > Please note, Wercker supports custom VM boxes so potentially we can
> > add custom VMs but I'm not sure it is good idea to maintain them.
> >
> > Tests on OSX:
> > I propose to use Travis since in comparison to Wercker it provides
> > OSX test boxes with XCode installed (
> > http://docs.travis-ci.com/user/osx-ci-environment) and also supports
> > Android builds (http://docs.travis-ci.com/user/languages/android)
> >
> > Thx!
> > Sergey
> > -----Original Message-----
> > From: Sergey Grebnov (Akvelon)
> > Sent: Monday, July 7, 2014 6:00 PM
> > To: dev@cordova.apache.org
> > Subject: RE: Add build status to github
> >
> > Hey Mark, it is really great to see you are working in this
> > direction, thx! Here are my additional notes
> >
> > I think we should have discussion in two directions here:
> > 1. Decide what we want to run as test for each repo 2. Particular
> > service/implementation details
> >
> > As for 1:
> > a) LIB, CLI: I propose to run unit tests via 'npm test' for
> > cordova-lib, cordova-cli, cordova-plugman (btw, I don't see plugman
> > tests so not sure
> we
> > have them) It seems, that Mark is on the same page.
> >
> > b) PLATFORMS: for the platforms I propose to start from implementing
> > simple e2e test with the following steps (written in nodejs):
> > - install cordova-cli (apache/master?)
> > - create test app
> > - add platform
> > - build
> >
> > * as a long term goal we may want to move this to npm tests (but
> > include to special group which can be run with additional flag since
> > I don't think we should run this along with general unit tests )
> >
> > As for 2:
> > If we want unified build platform across all repos it seems that
> > Wercker and Appveyor are the only good options due to windows support required.
> > Both looks good to me, but I need to double check Wercker supports
> > VS2013
> > (msbuild12) since it requires to build cordova-windows (will
> > investigate and respond). I also think is that Travic-CI is the most
> > safe option for other platforms/repos since they already proved to
> > be a good solution for many open source companies.
> >
> > Thx!
> > Sergey
> > -----Original Message-----
> > From: Mark Koudritsky [mailto:kamrik@google.com]
> > Sent: Friday, July 4, 2014 6:57 AM
> > To: dev@cordova.apache.org
> > Subject: Re: Add build status to github
> >
> > Oops, sorry, didn't look at the links before sending another link to
> > AppVeyor. Why not to use AppVeyor for lib and cli too? We could
> definitely
> > use some testing on windows.
> >
> > I also experimented with Wercker <http://wercker.com/> which is yet
> > another free CI service.
> > Added it to a branch in my fork of cordova-lib. You can see a badge
> > with build results here in README:
> > https://github.com/kamrik/cordova-lib/tree/wercker
> >
> > I never used Travis CI, but from description looks like Wercker is a
> > bit more flexible with environment setup and they even offer a
> > predefined environment for building Android apps <
> > http://devcenter.wercker.com/articles/languages/android.html> so
> > maybe
> we
> > can use it to run a test that goes all the way to building an apk.
> > They
> say
> > <http://devcenter.wercker.com/articles/bestpractices/pullrequests.ht
> > ml> they support checking pull requests too.
> >
> > What do you think?
> >
> > That said, I'm not particularly attached to any specific CI service,
> > any of them would be very helpful.
> >
> >
> > On Fri, Jun 27, 2014 at 10:40 AM, Andrew Grieve
> > <ag...@chromium.org>
> > wrote:
> >
> > > Make it happen :)
> > >
> > >
> > > On Fri, Jun 27, 2014 at 10:02 AM, Mark Koudritsky
> > > <ka...@google.com>
> > > wrote:
> > >
> > > > Would be nice to have this. Specifically Travis will only run on
> > > > Linux
> > > (and
> > > > maybe OSX). Here is a random similar service I found that can
> > > > also run on windows.
> > > > http://www.appveyor.com/
> > > >
> > >
> >
>
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
Sergey, can we set up AppVeyor to run the "npm test" of cordova-lib?
If yes, it would be an excellent option - we will have cordova-lib jasmine
tests running on windows, which otherwise happens rarely for all of us who
develop on Mac or Linux.
On Mon, Jul 14, 2014 at 2:54 PM, Jesse <pu...@gmail.com> wrote:
> We should just use Travis for quick sanity check tests.
>
> re: integration testing
> Getting into all the other build+test options is too close to Medic. Unless
> we plan to abandon Medic, we should focus on getting Medic+BuildBot working
> perfectly across all platforms, then possibly even reporting back to github
> on every commit.
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Jul 14, 2014 at 7:16 AM, Sergey Grebnov (Akvelon) <
> v-segreb@microsoft.com> wrote:
>
> > Tests on Windows:
> > I've compared Wercker and Appveyor and as for me it looks like Appveyor
> is
> > a better option to proceed for Windows since
> > 1. Wercker's existing windows boxes doesn't support building of Windows
> > 8.1 and WP 8.1 apps due to absence of Windows 8.1 and WP 8.1 SDKs on the
> > boxes.
> > 2. Appveyor supports above
> > Please note, Wercker supports custom VM boxes so potentially we can add
> > custom VMs but I'm not sure it is good idea to maintain them.
> >
> > Tests on OSX:
> > I propose to use Travis since in comparison to Wercker it provides OSX
> > test boxes with XCode installed (
> > http://docs.travis-ci.com/user/osx-ci-environment) and also supports
> > Android builds (http://docs.travis-ci.com/user/languages/android)
> >
> > Thx!
> > Sergey
> > -----Original Message-----
> > From: Sergey Grebnov (Akvelon)
> > Sent: Monday, July 7, 2014 6:00 PM
> > To: dev@cordova.apache.org
> > Subject: RE: Add build status to github
> >
> > Hey Mark, it is really great to see you are working in this direction,
> > thx! Here are my additional notes
> >
> > I think we should have discussion in two directions here:
> > 1. Decide what we want to run as test for each repo 2. Particular
> > service/implementation details
> >
> > As for 1:
> > a) LIB, CLI: I propose to run unit tests via 'npm test' for cordova-lib,
> > cordova-cli, cordova-plugman (btw, I don't see plugman tests so not sure
> we
> > have them) It seems, that Mark is on the same page.
> >
> > b) PLATFORMS: for the platforms I propose to start from implementing
> > simple e2e test with the following steps (written in nodejs):
> > - install cordova-cli (apache/master?)
> > - create test app
> > - add platform
> > - build
> >
> > * as a long term goal we may want to move this to npm tests (but
> > include to special group which can be run with additional flag since I
> > don't think we should run this along with general unit tests )
> >
> > As for 2:
> > If we want unified build platform across all repos it seems that Wercker
> > and Appveyor are the only good options due to windows support required.
> > Both looks good to me, but I need to double check Wercker supports VS2013
> > (msbuild12) since it requires to build cordova-windows (will investigate
> > and respond). I also think is that Travic-CI is the most safe option for
> > other platforms/repos since they already proved to be a good solution for
> > many open source companies.
> >
> > Thx!
> > Sergey
> > -----Original Message-----
> > From: Mark Koudritsky [mailto:kamrik@google.com]
> > Sent: Friday, July 4, 2014 6:57 AM
> > To: dev@cordova.apache.org
> > Subject: Re: Add build status to github
> >
> > Oops, sorry, didn't look at the links before sending another link to
> > AppVeyor. Why not to use AppVeyor for lib and cli too? We could
> definitely
> > use some testing on windows.
> >
> > I also experimented with Wercker <http://wercker.com/> which is yet
> > another free CI service.
> > Added it to a branch in my fork of cordova-lib. You can see a badge with
> > build results here in README:
> > https://github.com/kamrik/cordova-lib/tree/wercker
> >
> > I never used Travis CI, but from description looks like Wercker is a bit
> > more flexible with environment setup and they even offer a predefined
> > environment for building Android apps <
> > http://devcenter.wercker.com/articles/languages/android.html> so maybe
> we
> > can use it to run a test that goes all the way to building an apk. They
> say
> > <http://devcenter.wercker.com/articles/bestpractices/pullrequests.html>
> > they support checking pull requests too.
> >
> > What do you think?
> >
> > That said, I'm not particularly attached to any specific CI service, any
> > of them would be very helpful.
> >
> >
> > On Fri, Jun 27, 2014 at 10:40 AM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > Make it happen :)
> > >
> > >
> > > On Fri, Jun 27, 2014 at 10:02 AM, Mark Koudritsky <ka...@google.com>
> > > wrote:
> > >
> > > > Would be nice to have this. Specifically Travis will only run on
> > > > Linux
> > > (and
> > > > maybe OSX). Here is a random similar service I found that can also
> > > > run on windows.
> > > > http://www.appveyor.com/
> > > >
> > >
> >
>
Re: Add build status to github
Posted by Jesse <pu...@gmail.com>.
We should just use Travis for quick sanity check tests.
re: integration testing
Getting into all the other build+test options is too close to Medic. Unless
we plan to abandon Medic, we should focus on getting Medic+BuildBot working
perfectly across all platforms, then possibly even reporting back to github
on every commit.
@purplecabbage
risingj.com
On Mon, Jul 14, 2014 at 7:16 AM, Sergey Grebnov (Akvelon) <
v-segreb@microsoft.com> wrote:
> Tests on Windows:
> I've compared Wercker and Appveyor and as for me it looks like Appveyor is
> a better option to proceed for Windows since
> 1. Wercker's existing windows boxes doesn't support building of Windows
> 8.1 and WP 8.1 apps due to absence of Windows 8.1 and WP 8.1 SDKs on the
> boxes.
> 2. Appveyor supports above
> Please note, Wercker supports custom VM boxes so potentially we can add
> custom VMs but I'm not sure it is good idea to maintain them.
>
> Tests on OSX:
> I propose to use Travis since in comparison to Wercker it provides OSX
> test boxes with XCode installed (
> http://docs.travis-ci.com/user/osx-ci-environment) and also supports
> Android builds (http://docs.travis-ci.com/user/languages/android)
>
> Thx!
> Sergey
> -----Original Message-----
> From: Sergey Grebnov (Akvelon)
> Sent: Monday, July 7, 2014 6:00 PM
> To: dev@cordova.apache.org
> Subject: RE: Add build status to github
>
> Hey Mark, it is really great to see you are working in this direction,
> thx! Here are my additional notes
>
> I think we should have discussion in two directions here:
> 1. Decide what we want to run as test for each repo 2. Particular
> service/implementation details
>
> As for 1:
> a) LIB, CLI: I propose to run unit tests via 'npm test' for cordova-lib,
> cordova-cli, cordova-plugman (btw, I don't see plugman tests so not sure we
> have them) It seems, that Mark is on the same page.
>
> b) PLATFORMS: for the platforms I propose to start from implementing
> simple e2e test with the following steps (written in nodejs):
> - install cordova-cli (apache/master?)
> - create test app
> - add platform
> - build
>
> * as a long term goal we may want to move this to npm tests (but
> include to special group which can be run with additional flag since I
> don't think we should run this along with general unit tests )
>
> As for 2:
> If we want unified build platform across all repos it seems that Wercker
> and Appveyor are the only good options due to windows support required.
> Both looks good to me, but I need to double check Wercker supports VS2013
> (msbuild12) since it requires to build cordova-windows (will investigate
> and respond). I also think is that Travic-CI is the most safe option for
> other platforms/repos since they already proved to be a good solution for
> many open source companies.
>
> Thx!
> Sergey
> -----Original Message-----
> From: Mark Koudritsky [mailto:kamrik@google.com]
> Sent: Friday, July 4, 2014 6:57 AM
> To: dev@cordova.apache.org
> Subject: Re: Add build status to github
>
> Oops, sorry, didn't look at the links before sending another link to
> AppVeyor. Why not to use AppVeyor for lib and cli too? We could definitely
> use some testing on windows.
>
> I also experimented with Wercker <http://wercker.com/> which is yet
> another free CI service.
> Added it to a branch in my fork of cordova-lib. You can see a badge with
> build results here in README:
> https://github.com/kamrik/cordova-lib/tree/wercker
>
> I never used Travis CI, but from description looks like Wercker is a bit
> more flexible with environment setup and they even offer a predefined
> environment for building Android apps <
> http://devcenter.wercker.com/articles/languages/android.html> so maybe we
> can use it to run a test that goes all the way to building an apk. They say
> <http://devcenter.wercker.com/articles/bestpractices/pullrequests.html>
> they support checking pull requests too.
>
> What do you think?
>
> That said, I'm not particularly attached to any specific CI service, any
> of them would be very helpful.
>
>
> On Fri, Jun 27, 2014 at 10:40 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > Make it happen :)
> >
> >
> > On Fri, Jun 27, 2014 at 10:02 AM, Mark Koudritsky <ka...@google.com>
> > wrote:
> >
> > > Would be nice to have this. Specifically Travis will only run on
> > > Linux
> > (and
> > > maybe OSX). Here is a random similar service I found that can also
> > > run on windows.
> > > http://www.appveyor.com/
> > >
> >
>
RE: Add build status to github
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
Tests on Windows:
I've compared Wercker and Appveyor and as for me it looks like Appveyor is a better option to proceed for Windows since
1. Wercker's existing windows boxes doesn't support building of Windows 8.1 and WP 8.1 apps due to absence of Windows 8.1 and WP 8.1 SDKs on the boxes.
2. Appveyor supports above
Please note, Wercker supports custom VM boxes so potentially we can add custom VMs but I'm not sure it is good idea to maintain them.
Tests on OSX:
I propose to use Travis since in comparison to Wercker it provides OSX test boxes with XCode installed (http://docs.travis-ci.com/user/osx-ci-environment) and also supports Android builds (http://docs.travis-ci.com/user/languages/android)
Thx!
Sergey
-----Original Message-----
From: Sergey Grebnov (Akvelon)
Sent: Monday, July 7, 2014 6:00 PM
To: dev@cordova.apache.org
Subject: RE: Add build status to github
Hey Mark, it is really great to see you are working in this direction, thx! Here are my additional notes
I think we should have discussion in two directions here:
1. Decide what we want to run as test for each repo 2. Particular service/implementation details
As for 1:
a) LIB, CLI: I propose to run unit tests via 'npm test' for cordova-lib, cordova-cli, cordova-plugman (btw, I don't see plugman tests so not sure we have them) It seems, that Mark is on the same page.
b) PLATFORMS: for the platforms I propose to start from implementing simple e2e test with the following steps (written in nodejs):
- install cordova-cli (apache/master?)
- create test app
- add platform
- build
* as a long term goal we may want to move this to npm tests (but include to special group which can be run with additional flag since I don't think we should run this along with general unit tests )
As for 2:
If we want unified build platform across all repos it seems that Wercker and Appveyor are the only good options due to windows support required. Both looks good to me, but I need to double check Wercker supports VS2013 (msbuild12) since it requires to build cordova-windows (will investigate and respond). I also think is that Travic-CI is the most safe option for other platforms/repos since they already proved to be a good solution for many open source companies.
Thx!
Sergey
-----Original Message-----
From: Mark Koudritsky [mailto:kamrik@google.com]
Sent: Friday, July 4, 2014 6:57 AM
To: dev@cordova.apache.org
Subject: Re: Add build status to github
Oops, sorry, didn't look at the links before sending another link to AppVeyor. Why not to use AppVeyor for lib and cli too? We could definitely use some testing on windows.
I also experimented with Wercker <http://wercker.com/> which is yet another free CI service.
Added it to a branch in my fork of cordova-lib. You can see a badge with build results here in README:
https://github.com/kamrik/cordova-lib/tree/wercker
I never used Travis CI, but from description looks like Wercker is a bit more flexible with environment setup and they even offer a predefined environment for building Android apps <http://devcenter.wercker.com/articles/languages/android.html> so maybe we can use it to run a test that goes all the way to building an apk. They say <http://devcenter.wercker.com/articles/bestpractices/pullrequests.html>
they support checking pull requests too.
What do you think?
That said, I'm not particularly attached to any specific CI service, any of them would be very helpful.
On Fri, Jun 27, 2014 at 10:40 AM, Andrew Grieve <ag...@chromium.org>
wrote:
> Make it happen :)
>
>
> On Fri, Jun 27, 2014 at 10:02 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > Would be nice to have this. Specifically Travis will only run on
> > Linux
> (and
> > maybe OSX). Here is a random similar service I found that can also
> > run on windows.
> > http://www.appveyor.com/
> >
>
Re: Add build status to github
Posted by Josh Soref <js...@blackberry.com>.
fwiw, I have a draft change [1] to how we run cordova-lib tests, we'd like
to do this, but someone needs to spend the time creating a proper npm
module (and repo?) for it.
With the changes, it's possible to skip tests that can't run, e.g. If your
computer doesn't have vs2013, we could skip (and report skipping!) the
windows tests, but still get coverage of everything else (and be aware
that they were skipped…)
[1] https://github.com/apache/cordova-lib/pull/51
RE: Add build status to github
Posted by "Sergey Grebnov (Akvelon)" <v-...@microsoft.com>.
Hey Mark, it is really great to see you are working in this direction, thx! Here are my additional notes
I think we should have discussion in two directions here:
1. Decide what we want to run as test for each repo
2. Particular service/implementation details
As for 1:
a) LIB, CLI: I propose to run unit tests via 'npm test' for cordova-lib, cordova-cli, cordova-plugman (btw, I don't see plugman tests so not sure we have them)
It seems, that Mark is on the same page.
b) PLATFORMS: for the platforms I propose to start from implementing simple e2e test with the following steps (written in nodejs):
- install cordova-cli (apache/master?)
- create test app
- add platform
- build
* as a long term goal we may want to move this to npm tests (but include to special group which can be run with additional flag since I don't think we should run this along with general unit tests )
As for 2:
If we want unified build platform across all repos it seems that Wercker and Appveyor are the only good options due to windows support required. Both looks good to me, but I need to double check Wercker supports VS2013 (msbuild12) since it requires to build cordova-windows (will investigate and respond). I also think is that Travic-CI is the most safe option for other platforms/repos since they already proved to be a good solution for many open source companies.
Thx!
Sergey
-----Original Message-----
From: Mark Koudritsky [mailto:kamrik@google.com]
Sent: Friday, July 4, 2014 6:57 AM
To: dev@cordova.apache.org
Subject: Re: Add build status to github
Oops, sorry, didn't look at the links before sending another link to AppVeyor. Why not to use AppVeyor for lib and cli too? We could definitely use some testing on windows.
I also experimented with Wercker <http://wercker.com/> which is yet another free CI service.
Added it to a branch in my fork of cordova-lib. You can see a badge with build results here in README:
https://github.com/kamrik/cordova-lib/tree/wercker
I never used Travis CI, but from description looks like Wercker is a bit more flexible with environment setup and they even offer a predefined environment for building Android apps <http://devcenter.wercker.com/articles/languages/android.html> so maybe we can use it to run a test that goes all the way to building an apk. They say <http://devcenter.wercker.com/articles/bestpractices/pullrequests.html>
they support checking pull requests too.
What do you think?
That said, I'm not particularly attached to any specific CI service, any of them would be very helpful.
On Fri, Jun 27, 2014 at 10:40 AM, Andrew Grieve <ag...@chromium.org>
wrote:
> Make it happen :)
>
>
> On Fri, Jun 27, 2014 at 10:02 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > Would be nice to have this. Specifically Travis will only run on
> > Linux
> (and
> > maybe OSX). Here is a random similar service I found that can also
> > run on windows.
> > http://www.appveyor.com/
> >
>
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
Oops, sorry, didn't look at the links before sending another link to
AppVeyor. Why not to use AppVeyor for lib and cli too? We could definitely
use some testing on windows.
I also experimented with Wercker <http://wercker.com/> which is yet another
free CI service.
Added it to a branch in my fork of cordova-lib. You can see a badge with
build results here in README:
https://github.com/kamrik/cordova-lib/tree/wercker
I never used Travis CI, but from description looks like Wercker is a bit
more flexible with environment setup and they even offer a predefined
environment for building Android apps
<http://devcenter.wercker.com/articles/languages/android.html> so maybe we
can use it to run a test that goes all the way to building an apk. They say
<http://devcenter.wercker.com/articles/bestpractices/pullrequests.html>
they support checking pull requests too.
What do you think?
That said, I'm not particularly attached to any specific CI service, any of
them would be very helpful.
On Fri, Jun 27, 2014 at 10:40 AM, Andrew Grieve <ag...@chromium.org>
wrote:
> Make it happen :)
>
>
> On Fri, Jun 27, 2014 at 10:02 AM, Mark Koudritsky <ka...@google.com>
> wrote:
>
> > Would be nice to have this. Specifically Travis will only run on Linux
> (and
> > maybe OSX). Here is a random similar service I found that can also run on
> > windows.
> > http://www.appveyor.com/
> >
>
Re: Add build status to github
Posted by Andrew Grieve <ag...@chromium.org>.
Make it happen :)
On Fri, Jun 27, 2014 at 10:02 AM, Mark Koudritsky <ka...@google.com> wrote:
> Would be nice to have this. Specifically Travis will only run on Linux (and
> maybe OSX). Here is a random similar service I found that can also run on
> windows.
> http://www.appveyor.com/
>
Re: Add build status to github
Posted by Mark Koudritsky <ka...@google.com>.
Would be nice to have this. Specifically Travis will only run on Linux (and
maybe OSX). Here is a random similar service I found that can also run on
windows.
http://www.appveyor.com/