You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2014/03/25 18:44:20 UTC

[jira] [Commented] (SAMZA-29) Setup Hudson CI for Samza

    [ https://issues.apache.org/jira/browse/SAMZA-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946841#comment-13946841 ] 

Jakob Homan commented on SAMZA-29:
----------------------------------

If anyone is interested in taking this on, it would be very helpful.  I had investigated a few months ago (https://builds.apache.org/view/S-Z/view/Samza/job/Samza%20-%20testpach/)  and the non-reserved-for-Hadoop Jenkins boxes were completely slammed and it was taking hours and hours for a Jenkins job to get through.  Last week it looked like it was in better shape, but at this moment there are 55 jobs in the queue.  Not sure what the actual current state is.  [~gkesavan], is there any chance of get the Samza jobs into the shiny and empty Hadoop queues, seeing as we're BFFs to YARN?

This would be a good task to get more familiar with ASF infrastructure.  The instructions for getting an account and setting up Hadoop-style test-patch pre-commit builds are here: http://wiki.apache.org/general/Jenkins.  I'll make sure whoever takes this on gets the Jenkins account.

> Setup Hudson CI for Samza
> -------------------------
>
>                 Key: SAMZA-29
>                 URL: https://issues.apache.org/jira/browse/SAMZA-29
>             Project: Samza
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.6.0
>            Reporter: Chris Riccomini
>
> We should setup Apache's Hudson grid (https://builds.apache.org/) to automatically build Samza and run unit tests. The Hudson job should poll git periodically, and kick off the test if there were changes made since last run. We should set the test up to notify the dev mailing list of failures.



--
This message was sent by Atlassian JIRA
(v6.2#6252)