On Wed, May 20, 2015 at 7:27 AM, Nick Wellnhofer <[email protected]> wrote:
> On 18/05/2015 21:31, Nick Wellnhofer wrote:
>>
>> OK, I started with a .travis.yml for Clownfish.
>
> I also added a build script and config file for Appveyor, a Travis clone for
> Windows. After applying a couple of fixes, the Windows build passes again:
>
>     https://ci.appveyor.com/project/nwellnhof/lucy-clownfish/build/1.0.13

When I do Windows development these days, I fire up a full EC2 instance.  Now
I won't have to do that for simple fixes!  Thank you!

> Unfortunately, I couldn't make the Perl bindings build on Appveyor with the
> preinstalled Perl. Like with Travis, it's possible to manually install
> whatever prerequisites, but I didn't want to go through the hassle.

Building with MSVC, though, that's great!

Once appveyor.yml has landed on master, we should open a ticket with Infra to
get both Travis and Appveyor turned on for lucy-clownfish.git.

  https://issues.apache.org/jira/browse/INFRA-9017

I guess we set up notifications after that?  I think it would be good to have
both Travis and Appveyor email issues@lucy on change between success/failure
for pushes to master.  I don't want to see email for pull requests or other
pushes to other branches though.

Marvin Humphrey

Reply via email to