Michael Cooper [:mythmon] Assignee
	Description • 11 years ago

Jenkins is pretty unreliable lately, and we keep wasting time on it. IT has made be believe that our Jenkins is going away, but I haven't gotten any clues about what it will be replaced with.

So, in the mean time, we should try and set up an alternative like Travis! We should be able to use a custom Travis build script and get it to install whatever we like and get a full test set up running, and then run the tests. Hopefully. Ideally after this bug is done, there will be a parallel set of CI jobs running for pull requests and commits to master. If that runs nicely for a while, we can decide if we want to stay with Travis and ditch Jenkins, or do something else.

Marking this as 3 points to block off a bunch of time to try it all out.

	Will Kahn-Greene [:willkg] ET needinfo? me
	Comment 1 • 11 years ago

Switching this to be a research bug. Research bugs can result in tangible changes, so it's just a nomenclature tweak.

	Michael Cooper [:mythmon] Assignee
	Comment 2 • 11 years ago

This is me.

	Michael Cooper [:mythmon] Assignee
	Comment 3 • 11 years ago

Status: This is going well so far! I have Travis running on a particular branch just for this, and it is currently running tests and passing all the tests it doesn't skip. Right now it is skipping all ES, Redis, and Selenium tests (and maybe more). I have plans to make all of these work.

Work is slow because not only does this have to run the tests for me to verify things, it also has to run through an entire clone and install cycle for every test run, unlike Jenkins which would save state between builds. The first build that passed tests was 7 minutes total, without ES or Redis. That's pretty good, considering.

	Michael Cooper [:mythmon] Assignee
	Comment 4 • 11 years ago

Status: 32 builds later, I have all tests running and passing and a full SUMO environment being created for each Travis run. This takes between 5 and 15 minutes, depending on network bandwidth and other factors.

I filed a pull request here: https://github.com/mozilla/kitsune/pull/1579

The Travis build for that pull request can be seen here: https://travis-ci.org/mythmon/kitsune/builds/10468830

	Michael Cooper [:mythmon] Assignee
	Comment 5 • 11 years ago

This landed in
- https://github.com/mozilla/kitsune/commit/826450fcc1071d0809628387d98c30bef369e40b
- https://github.com/mozilla/kitsune/commit/69a9aca9311b33b0f330a8d2fd8216e223b24d96

This will take effect immediately. I'll leave this open until we decide that we like this. Also, Jenkins is still running for now.

	Michael Cooper [:mythmon] Assignee
	Comment 6 • 11 years ago

I like this. I'm happy with the results, and Travis seems to be stable. I'm going to mark this as fixed and not worry about Jenkins anymore.

	Will Kahn-Greene [:willkg] ET needinfo? me
	Comment 7 • 11 years ago

Nixing the [research] part since this ended up being an implementation bug.