2014-02-15 18:52:08 +00:00
|
|
|
# http://docs.travis-ci.com/user/languages/python/
|
Add a Travis configuration
Travis[1] runs continuous integration for Open Source projects. With
github, it will run the configured tests and tag pull requests as passing
or failing. This commit adds a Travis configuration.
Since Travis hosts run debian/ubuntu, and execute tests in virtualenv,
getting access to `rpm` and `python-rpm` is impossible, or nontrivial,
at least. For now, ignore the functional tests. To support running the
BuildTargetParser tests, pull that class out into its own module, and
away from release.py, which imports `rpm`.
To configure travis, go to the website, log in with your github account,
then sync your repos under the account tab below your name. Then just
switch the repo to 'on' and it should be all set up.
[1]: http://travis-ci.org
2012-11-10 10:19:02 -04:00
|
|
|
language: python
|
|
|
|
|
python:
|
|
|
|
|
- "2.6"
|
|
|
|
|
- "2.7"
|
2014-02-16 02:35:34 +00:00
|
|
|
- "3.3"
|
Add a Travis configuration
Travis[1] runs continuous integration for Open Source projects. With
github, it will run the configured tests and tag pull requests as passing
or failing. This commit adds a Travis configuration.
Since Travis hosts run debian/ubuntu, and execute tests in virtualenv,
getting access to `rpm` and `python-rpm` is impossible, or nontrivial,
at least. For now, ignore the functional tests. To support running the
BuildTargetParser tests, pull that class out into its own module, and
away from release.py, which imports `rpm`.
To configure travis, go to the website, log in with your github account,
then sync your repos under the account tab below your name. Then just
switch the repo to 'on' and it should be all set up.
[1]: http://travis-ci.org
2012-11-10 10:19:02 -04:00
|
|
|
|
2014-02-15 18:52:08 +00:00
|
|
|
install:
|
2014-02-16 02:35:34 +00:00
|
|
|
- ./.travis-install-kludge.sh
|
2014-02-15 18:52:08 +00:00
|
|
|
- pip install 'pep8' --use-mirrors
|
|
|
|
|
|
Add a Travis configuration
Travis[1] runs continuous integration for Open Source projects. With
github, it will run the configured tests and tag pull requests as passing
or failing. This commit adds a Travis configuration.
Since Travis hosts run debian/ubuntu, and execute tests in virtualenv,
getting access to `rpm` and `python-rpm` is impossible, or nontrivial,
at least. For now, ignore the functional tests. To support running the
BuildTargetParser tests, pull that class out into its own module, and
away from release.py, which imports `rpm`.
To configure travis, go to the website, log in with your github account,
then sync your repos under the account tab below your name. Then just
switch the repo to 'on' and it should be all set up.
[1]: http://travis-ci.org
2012-11-10 10:19:02 -04:00
|
|
|
script: nosetests test/unit
|
