Set up Travis-CI testing for Kuma

RESOLVED FIXED

Status

RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: lorchard, Unassigned)

Tracking

Details

(Whiteboard: [specification][type:feature])

(Reporter)

Description

5 years ago
What problems would this solve?
===============================
Currently, we use Jenkins. Jenkins has issues, and we hear that IT would rather not maintain it.

SUMO recently switched Kitsune over to use Travis-CI, the hosted continual integration testing service.
We should try doing something similar.


Who would use this?
===================
MDN devs & contributors

What would users see?
=====================
Tests would run on Travis, rather than Jenkins

What would users do? What would happen as a result?
===================================================
Test performance might improve, transient errors will probably go away.

Is there anything else we should know?
======================================
Though our set up will be special in its own annoying ways, we can copy the SUMO team's notes in trying to set this up:

https://github.com/mozilla/kitsune/blob/master/.travis.yml
https://github.com/mozilla/kitsune/tree/master/scripts/travis

Comment 1

5 years ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/512526fff0fa509a97901276f87ba421726b05c7
Update requirements files (#1934) and first working .travis.yml (bug 914808)

https://github.com/mozilla/kuma/commit/d2434c8f7c8afe8f03795530e64813e1456be405
bug 914808: Stop updating product details at test time; tweak usage of constance in demos forms

https://github.com/mozilla/kuma/commit/cb1693eb4a87685e663cd6fbb40d80d069b604f6
bug 914808: Notify mdndev in IRC and mailing list on travis status
(Reporter)

Comment 2

5 years ago
This should be done and start working with IRC notifications soon.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.