| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Setting up Jenkins tests for PostgreSQL is not a priority for WMF, so
this change enables Travis CI tests run against a PostgreSQL database.
At the moment, those tests will fail because various fixes for
PostgreSQL issues are still pending review. However carefully testing
individual commits (cf. for example
https://travis-ci.org/scfc/mediawiki-core/builds/40319020) shows that
the test setup itself is working as expected.
Travis CI's hhvm does not support PostgreSQL, so for now this change
only tests PostgreSQL with PHP 5.3.
Also the range of branches that tests are run against is widened to
include travis-ci/*. This allows developers to enable Travis CI in
their GitHub fork of wikimedia/mediawiki and then push to such a
branch without having to mess up the master or wmf/* branches with
their defined meaning.
Bug: 37602
Change-Id: I9c2efa3fbc589d2d4198120ca80501124b1b16b9
|
| |
|
|
| |
Change-Id: If61d0ac868c0932a0bb0aae76db4354190874c35
|
| |
|
|
|
|
| |
This reverts commit 420f55ad976a4929fdc9b1eff9ed2b6044c633d6.
Change-Id: I4c8aa600c72041daf49ed6158b9375bdcc5c9015
|
| |
|
|
|
|
|
| |
Those with admin access to the GitHub repo get e-mails by default
for build failures.
Change-Id: I1edba0af7f53ed40066cd395fe70daf3c99413eb
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
On second thought, I'd really much rather only target hhvm-nightly for now. On
the one hand, this is monopolizing / hijacking .travis.yml to a specific
Wikimedia project (HHVM deployment), but on the other hand, it's a big enough
project, so I'd like to ask you (dear reviewer) to consider it, as a short-term
arrangement. There are things like IRC notifications, overall build status,
etc. that are scoped to all configured builds and having 5.3 in there adds
noise. It also sows confusion about where we run our tests. People should
really turn to Jenkins for 5.3 testing. I think we're in the final couple of
months of hardcore sprinting on HHVM. I wouldn't mind opening this up after.
Change-Id: I0131667135ef3ca75d01ac5645dbc89bda306d98
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Target 'hhvm-nightly', not 'hhvm'.
* Don't target Zend PHP versions other than 5.3.
There is value in targetting different versions of the PHP interpreter, but
in the short term there is more benefit to be had from targetting just HHVM
and PHP 5.3 (results are produced more quickly and are easier to interpret).
* Don't update submodules manually; Travis does that by default if there is a
.gitmodules file in the repository root.
<http://docs.travis-ci.com/user/build-configuration/#Git-Submodules>
* Update Composer before installing PHPUnit.
* Make the wiki name and dbname agree.
* Allow Composer to install whatever is specified in composer.json, rather than
hard-coding an install of PHPUnit 3.7 (3.7 is incompatible with HHVM).
* Ping freenode#mediawiki-core with the test results, but only when the build
status changes. We can turn it off if it gets annoying.
* Don't hack include_path or date.timezone ini settings; those were kludges
needed to get HHVM to run at all at, but they're no longer needed.
* Invoke hhvm via 'php'; Travis ensures that it points to the target
interpreter.
Verified on my personal fork:
<https://travis-ci.org/atdt/mediawiki-core/builds/27983653>
Change-Id: I442b40e0d3e31d3cbd963e1219578842f4564004
|
| |
|
|
| |
Change-Id: I7401f1d059437eadd3712c012a93a6a5b6ac4403
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Currently these are all set to be allowed to
fail as currently some tests do fail but having
this run will allow us to slowly fix them and
remove the versions from allow_failures
The jobs for 5.3 5.4 and 5.5 seem to take somewhere
between 6 and 9 mins compared to hhvm which takes
about 4 but this should be no problem
Change-Id: Ifee7f6476cfd41736aa595e92260a333b4c059ee
|
| |
|
|
|
|
|
|
| |
This will avoid composer transport exceptions
which happen when travis hits the github api
too much
Change-Id: I3c7b209d9e4181dd1393f4e9f93587d05828bb4e
|
|
|
Travis CI is a popular continuous integration service that provides free
automated testing to FOSS projects. Ten days ago, the HHVM team announced that
Travis CI's build environment provides HHVM by default. This patch contains a
Travis CI job configuration that runs MediaWiki's test suite using HHVM.
Because we replicate changes to GitHub, merging this change and enabling the
Travis CI hook in the repository configuration on GitHub will cause Travis CI
to run the tests on each commit.
Change-Id: Ia18cba5facb7f0b506e962df2f114338af571b8a
|
