1079357 - switch to Travis-CI for continuous integration

Status: RESOLVED FIXED

(Input Graveyard :: Code Quality, defect)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Input currently uses jenkins (ci.mozilla.org) for continuous integration. There are a few problems with our setup:

1. we don't have it set up to test pull requests

2. we're stuck with using whatever services jenkins is currently using


We can fix the first one, but it's a bunch of extra work. SUMO had this set up for a while.

The second one means that our test environment can differ from our server environments and we don't have much control over that.

I think the better solution is to instead switch to Travis CI. This fixes both issues and gives us more flexibility to do things like test against multiple versions of Elasticsearch.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Pushing this off until next quarter.

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

Pretty sure Jenkins only has Python 2.6 on it. In order to switch to Django 1.7 which doesn't support Python 2.6, we need to switch to Travis.

Thus, I'm making this bug block bug #1118765.

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

@r1cky: This would be a good one to tackle next. It'll be a much better CI experience for us plus it lets us test with Python 2.7 (which we're using) and Elasticsearch 1.2.4 (which we're switching to).

Comment 4

[Ricky Rosario [:rrosario, :r1cky]]

Grabbing. I'll talk to :mythmon for inspiration.

Comment 5

[Ricky Rosario [:rrosario, :r1cky]]

Iterated in a pull request until I got it working:
https://github.com/mozilla/fjord/pull/450

I need to look into separate builds for vendor vs peep.

Comment 6

[Ricky Rosario [:rrosario, :r1cky]]

Landed on master:
https://github.com/mozilla/fjord/commit/8396274159a4373400682944655f6008139ced52

The commit message has the wrong bug # in it :/

Comment 7

[Ricky Rosario [:rrosario, :r1cky]]

Travis is building master! https://travis-ci.org/mozilla/fjord/builds/