Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Travis-CI: Use new container-based infrastructure #297

Merged
merged 33 commits into from
Aug 18, 2017

Conversation

AlexanderS
Copy link
Member

Travis-ci started to promote the new container-base infrastructure in each build on the legacy systems. So we should try to migrate. I requested to add yum and libaugeas0 to the package whitelist, so it should be possible to install all required apt-packages.

Let's see how much speed-up we will get from this.

@AlexanderS AlexanderS changed the title Travis-CI: Use new container-base infrastructure Travis-CI: Use new container-based infrastructure Jul 24, 2015
@solj
Copy link
Member

solj commented Jul 24, 2015

👍

@stpierre
Copy link
Member

We should also see if we can get selinux libs installed (since we currently don't test that), and see if we can test in older Python somehow. That might be scope creep for this PR, though.

@AlexanderS
Copy link
Member Author

I think we can download, compile and install older python version. There is a guide for installing custom software: http://docs.travis-ci.com/user/migrating-from-legacy/#How-Do-I-Install-Custom-Software%3F

@AlexanderS AlexanderS force-pushed the feature/travis-container branch 26 times, most recently from ccb57f6 to ad7ac78 Compare July 25, 2015 03:30
@AlexanderS AlexanderS force-pushed the feature/travis-container branch from da430d8 to 829334d Compare August 17, 2017 14:48
@AlexanderS AlexanderS force-pushed the feature/travis-container branch 14 times, most recently from 17a8fae to 5fc1f7e Compare August 17, 2017 20:29
@AlexanderS
Copy link
Member Author

So we now have working tests again on the current travis infrastructure.

All failures in the Python3 tests are ignored. Most errors are because of the unicode semantic in python3 and some errors seem to be that the Mock module is handled differently.

Additionally we need a newer pylint version with Python3 support that introduces a lot of more warnings/errors. There already was some progress in #269 but it seems to be stalled.

Last but not least we may need to think about alternative packages for missing stuff like m2crypto.

I think we can merge this now and create a new bug/pr for Python3 support.

Since 2017-07-18 the default dist is changing to trusty[1]. Just using the
new default before the switch.

1: https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming
cheetah3 is a fork of cheetah for Python2.7 and Python3.
The "with_system_site_packages" virtualenv seems to be missing the
pymodules directory containing python modules installed with the
python-support debian helper. So we use the default environment and
manually add the references to the system-wide python packages.
@AlexanderS AlexanderS force-pushed the feature/travis-container branch from 5fc1f7e to 0fdabbc Compare August 17, 2017 21:04
@solj solj merged commit 0fdabbc into Bcfg2:master Aug 18, 2017
@solj
Copy link
Member

solj commented Aug 18, 2017

@AlexanderS Sounds good to me. Merged. Thanks!

@AlexanderS AlexanderS deleted the feature/travis-container branch August 21, 2017 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants