This PR try to fix Tx warning and improve autobuild process in Travis.
In the context of building on Travis, we faced some issues about Transifex:
Tx client relies on urllib3 whic complains about SNI config for python < 3
Python 3 is available on Travis Precise OS in v3.2, but python SSL isn't available for python < 3.3
We don't have a dedicated account on Tx to pull locales, and rely to developers personnal accounts is never a good idea
Build isn't necessary on development-build branch as it's just a receiver for the build
So, this PR:
[x] disable Travis build for the development-build branch
[x] install Python3.5 and Pip from deadsnakes PPA
[x] install last Tx client from Pip
[x] use the brand-new dedicated Cozy Tx account for Travis jobs
Note: we pass the Tx account password using Travis encrypted variables. Those variables are disabled from unsure PR, like ones comming from another remote (like in PR). So Tx locales pull will always fail in PR build. It's safe and OK, and won't break the CI in PR ; the development branch build after merge will so be OK too, as long as the pull will work fine in this case (same origin).
This PR try to fix Tx warning and improve autobuild process in Travis.
In the context of building on Travis, we faced some issues about Transifex:
So, this PR:
Note: we pass the Tx account password using Travis encrypted variables. Those variables are disabled from unsure PR, like ones comming from another remote (like in PR). So Tx locales pull will always fail in PR build. It's safe and OK, and won't break the CI in PR ; the development branch build after merge will so be OK too, as long as the pull will work fine in this case (same origin).