giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-316) Add for precommit test using Jenkins
Date Wed, 29 Aug 2012 23:15:07 GMT


Eli Reisman commented on GIRAPH-316:

So after this is committed you will fix the jira path? I have not used Jenkins too much and
am not sure if I should attempt to test this for real somehow or just commit and let you work
with it? Its a great idea!

> Add for precommit test using Jenkins
> --------------------------------------------------
>                 Key: GIRAPH-316
>                 URL:
>             Project: Giraph
>          Issue Type: Sub-task
>          Components: test
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>         Attachments: GIRAPH-316_2.patch, GIRAPH-316.patch
> For automatic pre-commit tests by jenkins, we need a script for downloading the recent
patch, compiling the patched source, and checking warnings. This patch includes the script.
I borrowed from Hadoop, and I modified the following things:
> * Hadoop's test-patch does not allow any javadoc warnings, but this patch allows them
and does not allow the increase of javadoc warnings. This is because the current implementation
of Giraph already has 47 javadoc warnings.
> * Add the checkstyle check which is not implemented in Hadoop's one.
> * Add an options to take jira user as an argument.
> * Add some codes related to the project directory structure and some messages.
> * Changed some codes to reflect the target directory hierarchy caused by munged.
> You can check the integrated test from
To execute the test, please click 'Build now' and type the number of Giraph jira issue. Now,
I gave the wrong path of the jira cli to jenkins because I don't want to disturb the jira.
So, you see "no such file/directory" error in "Adding comment to jira" section)
> After this patch is committed, I'll ask the automatic jenkins hook to builds@a.o as described

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message