You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2014/04/08 18:20:19 UTC
[jira] [Commented] (KAFKA-1360) Configure continuous integration
(CI) for Kafka branches under active development
[ https://issues.apache.org/jira/browse/KAFKA-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963132#comment-13963132 ]
Jun Rao commented on KAFKA-1360:
--------------------------------
Following up in https://issues.apache.org/jira/browse/INFRA-7546
> Configure continuous integration (CI) for Kafka branches under active development
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-1360
> URL: https://issues.apache.org/jira/browse/KAFKA-1360
> Project: Kafka
> Issue Type: Improvement
> Components: packaging
> Reporter: Clark Breyman
> Priority: Minor
> Labels: build, ci
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Having continuous integration configured for Kafka would help the project by
> - ensuring that developers are notified when the build or tests break
> - automates the publication of test coverage and performance information
> - simplifies the process of publishing nightlies to both maven central and the package download site (which also makes it easier to get feedback on pre-release builds)
> See http://ci.apache.org for Apache managed options. Jenkins seems the most appealing.
--
This message was sent by Atlassian JIRA
(v6.2#6252)