tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-166) Automatic precommit test using Jenkins
Date Wed, 15 Jan 2014 10:13:21 GMT

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

Hudson commented on TAJO-166:
-----------------------------

SUCCESS: Integrated in Tajo-master-build #13 (See [https://builds.apache.org/job/Tajo-master-build/13/])
TAJO-166: Automatic precommit test using Jenkins. (hyunsik) (hyunsik: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git&a=commit&h=d2ff46ee113c88a75268c1cb4cd3b9d43668b226)
* dev-support/test-patch.sh
* CHANGES.txt


> Automatic precommit test using Jenkins
> --------------------------------------
>
>                 Key: TAJO-166
>                 URL: https://issues.apache.org/jira/browse/TAJO-166
>             Project: Tajo
>          Issue Type: Task
>          Components: build
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.8-incubating
>
>         Attachments: TAJO-166.patch
>
>
> We have manually verified all submitted patches by using 'mvn clean install' before committing
patches. It is getting burden for committers. We need to adopt automatic precommit test using
jenkins.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message