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

Alex Newman commented on HBASE-11853:
-------------------------------------

> This is looking good. How I read it? I see we are running a shell command to 
> run each of the categories... in //?
That's correct

 > Takes 30mins? Where I look for tests that failed?
Internally on our jenkins we can get it to run that fast. Do you mean on 
jenkins/travis or circle. I'll assume you mean for travis or jenkins. The web 
interface will show if any of the categories failed. If you click on the 
category run it will show the failed test at the bottom.

>Looking at patch, are we pulling all dependencies each time?
> $HOME/.m2
Circle will cache the dependencies. Travis will as well, but only for paid 
accounts.

> The travis spec is still only hbase-server tests?
>Ditto for circle-ci set?

Nah they run all the others with the line "test -PskipServerTests" \" in circle 
and   - BUILD="test -PskipServerTests"
in travis

> Provide an alternative to the apache build for developers (like me) who 
> aren't committers
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-11853
>                 URL: https://issues.apache.org/jira/browse/HBASE-11853
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Alex Newman
>            Assignee: Alex Newman
>         Attachments: HBASE-11853-testing-v0.patch, 
> HBASE-11853-testing-v1.patch, HBASE-11853-v0.patch, HBASE-11853-v3.patch, 
> HBASE-11853-v4.patch, HBASE-11853-v5.patch, HBASE-11853-v6.patch, 
> HBASE-11853-v7.patch
>
>
> Travis CI and Circle-CI now provide free builds for open source projects. I 
> created the capability to run builds this way. Although they are closed 
> source (and thus not a replacement for jenkins IMHO), they are super 
> convenient. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to