calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Hyde <>
Subject Re: Apache-hosted CI (was Re: Build error in master branch)
Date Tue, 09 Feb 2016 18:33:02 GMT
Fantastic! We’ve needed CI for a long time.

I think the only thing left is to link to that site from somewhere on our web site, maybe <>. I’ve assigned to you. Can you mark it fixed when you’ve
added that link. I’m happy to re-publish the web site.

Any idea why the JDK 1.7 build is failing? Maybe some interference between tests?


> On Feb 8, 2016, at 9:39 PM, Josh Elser <> wrote:
> Better late than never?
> Here are two jobs that will run hourly (if changes are present), compile, run tests,
and build javadocs. As an added perk, if the build was successful, it will deploy the snapshot
to the Apache snapshots repository (hooray). We can also have the job send a message to one
of our lists on pass/fail. Both jobs are presently configured just to message me for now.
> Let me know what you all think.
> Getting some precommit stuff wired up will be next.
> Josh Elser wrote:
>> Ugh, sorry, I've been otherwise swamped and haven't looked into this at
>> all.
>> covers the infra post on what they recently providing for
>> building/testing pull requests.
>> In general, we have access to a Jenkins instance which we can configure
>> to run builds on commits. We can investigate using Yetus[1] as an entry
>> point for automating builds (can also double as an alternative for
>> building PR's).
>> [1]
>> Vladimir Sitnikov wrote:
>>> Any success with CI?
>>> I just came across, and
>>> they somehow managed to enable Travis for an Apache project.
>>> I've no idea what opportunities Apache's CI provides, however having
>>> some sort (e.g. Travis) of "github PR testing" would be good.
>>> Vladimir

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message