[
https://issues.apache.org/jira/browse/HBASE-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Newman updated HBASE-11853:
--------------------------------
Attachment: HBASE-11853-v3.patch
Here's an example file. I only did the work for some of the tests, but I think
you catch the drift. One mvn comman builds everything that's not hbase-server.
Then we break up the hbase-server tests into smaller categories. Since we have
fixed categories to assign to tests (just like small, medium and large), it
should never go stale, as long as we remember to assign them to a category.
The one tricky part is figuring out what categories we want for the
hbase-server. We don't want too many as it will cause too many builds, but it
is important that any category can run fast enough to complete within
travis/ci's limits. As far as HBase-server categories go I am thinking
- misc
- client
- coprocessor
- mapred
- mapreduce
- master
- metrics-monitoring
- regionserver
- replication
- rest
- snapshot
- util
I've provided an example for client and also the non hbase-server tests. It's
currently running on travis
https://travis-ci.org/OhmData/hbase-public/
If we like this approach, i'll complete the patch for travis and circleci (both
free for open source)
> 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: Bug
> Reporter: Alex Newman
> Assignee: Alex Newman
> Attachments: HBASE-11853-testing-v0.patch,
> HBASE-11853-testing-v1.patch, HBASE-11853-v3.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.2#6252)
