[
https://issues.apache.org/jira/browse/CASSANDRA-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955708#comment-15955708
]
Jeff Jirsa commented on CASSANDRA-13388:
----------------------------------------
I've been using the {{circle.yml}} recently - for example CASSANDRA-13410
- A successful CI run looks like this:
https://circleci.com/gh/jeffjirsa/cassandra/77 (all green)
- A failed CI run looks like https://circleci.com/gh/jeffjirsa/cassandra/75:
{quote}
Your build ran 2980 tests with 1 failure
testDroppedMessages - org.apache.cassandra.net.MessagingServiceTest
{quote}
> Add hosted CI config files (such as Circle and TravisCI) for easier developer
> testing
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13388
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13388
> Project: Cassandra
> Issue Type: Improvement
> Components: Testing
> Reporter: Jeff Jirsa
> Assignee: Jeff Jirsa
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.x
>
> Attachments: circle.yml, travis.yml
>
>
> We currently require unit tests and dtests to accept a patch, but it's not
> easy for most contributors to actually execute these tests in a way that's
> visible for the reviewer / other JIRA users.
> We should push some standard config files into the various branches to
> facilitate easier testing.
> I propose we start with TravisCI and CircleCI, because:
> - Travis has limited free support for developers working on OSS projects, and
> is already an accepted vendor at the ASF (apparently the ASF pays for 30
> concurrent tests already), and
> - CircleCI is also free for developers working on OSS projects, and has
> slightly more flexibility than Travis in terms of the number of free workers
> and durations.
> Both are enabled by pushing a single YAML file into each branch to configure
> jobs, and require each individual developer who WANTS to run tests to link
> their github account to the vendor. Developers who don't want to use this
> functionality can simply ignore it - they're effectively no-ops for anyone
> who's not already using those services.
> Are there any others we should consider including?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
