Anyway, don’t worry too much about why the test is failing. We’ll figure out it. The task is complete when you’ve added a link to the web page. And thanks again.
Julian > On Feb 9, 2016, at 11:12 AM, Josh Elser <josh.el...@gmail.com> wrote: > > I'm not sure, actually. The first run passed, I haven't looked closely enough > to guess why it fails. Will try to take a look tonight. > > For those who don't already have Jenkins accounts, I think Julian (as VP) > should have the karma to give you the necessary permission to update/tweak > the Jenkins job (or he will have the ability to request such a permission). > > Julian Hyde wrote: >> 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 >> http://calcite.apache.org/develop/<http://calcite.apache.org/develop/>. I’ve >> assigned https://issues.apache.org/jira/browse/CALCITE-623 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? >> >> Julian >> >> >>> On Feb 8, 2016, at 9:39 PM, Josh Elser<josh.el...@gmail.com> wrote: >>> >>> Better late than never? >>> >>> https://builds.apache.org/view/A-D/view/Calcite/ >>> >>> 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. >>>> >>>> https://blogs.apache.org/infra/entry/github_pull_request_builds_now >>>> 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] https://yetus.apache.org >>>> >>>> Vladimir Sitnikov wrote: >>>>> Any success with CI? >>>>> >>>>> I just came across https://travis-ci.org/apache/jackrabbit-oak, 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 >> >>
