-
Notifications
You must be signed in to change notification settings - Fork 1
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate from legacy to container-based infrastructure in Travis CI #2
Comments
hmm... well... some of the packages such as |
it is a good idea, cloning QT and building it in Travis CI would make it much slower again.. |
Also, check trusty CI environment later on |
Or we could shift to semaphoreci for continuous integration and continuous deployment. |
I suppose I will look in semaphoreci later on. And keeping travis builds for QT 4 only. |
This makes build for only QT 4 and not QT 5. Changes done after Travis CI moved to container based infrastructure. (refer issue #2)
Commit ce3a945 closes this issue. |
Reopening this issue as I found a good ppa of beineri. This will gives a facility to build and run tests on different versions of QT and not just for QT Qt 4.8.1 and Qt 5.0.2 |
Travis CI build 31 passed 馃槇 , now closing this issue. |
Migrate from legacy to container-based infrastructure in Travis CI, last build failed in
dev
branch. Also this is much faster 馃榿 !!The text was updated successfully, but these errors were encountered: