[
https://issues.apache.org/jira/browse/CALCITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567533#comment-15567533
]
Josh Elser commented on CALCITE-1084:
-------------------------------------
Hey [~francischuang]. Apache Yetus is a project which can automatically run
contributions (pull requests, patches, etc) from users against the codebase and
give a report on a bunch of criteria about whether or not the patch is allowed
to be merged. The results of the test are automatically displayed via a comment
on the JIRA issue with some pretty JIRA formatting. We can get numerous checks
out of the box as well as the ability to write our own (e.g. verify that commit
messages start with "\[CALCITE-XXXX\]")
Here's an example:
https://issues.apache.org/jira/browse/ACCUMULO-4489?focusedCommentId=15557373&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15557373
Yetus does overlap with some of the verifications that exist on Github; I would
call Yetus a super-set of what Travis/Jenkins will do out of the box. Yetus
does not replace Jenkins/etc as a tool to run builds on commit/intervals.
Does that help?
> Set up Yetus-based PreCommit build
> ----------------------------------
>
> Key: CALCITE-1084
> URL: https://issues.apache.org/jira/browse/CALCITE-1084
> Project: Calcite
> Issue Type: Task
> Reporter: Josh Elser
> Assignee: Julian Hyde
>
> We got Jenkins-based CI in CALCITE-623. Let's get some ASF-hosted pre-commit
> builds that can be used before we commit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
