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
Upgrade to latest Travis CI infrastructure #11986
Comments
contacted Github support about the error and they replied:
So maybe we try the solution in the git-lfs issue? |
I think this will be a "bigger" project. The new infrastructure has way more changes to be done. Actually I believe it might be most useful to build the new travis setup from scratch and maybe (if possible) with @mneudert would you maybe be keen to do that? |
Switching over to a partially sudoless infrastructure sounds like something I would really like to try. Partially only because I think the ramdisk used in some tests only works that way. But afaik it is possible to activate sudo on a per-job base without the global requirement. But that might still not solve the problem with the git credentials. Wouldn't it work using some travis secure token to at least get everything up and running until a complete switch can be made? |
Yes. Secure token should work as well. For now the builds are running on old |
Hi @mneudert Do you maybe have an update on the progress of migrating to the latest Travis architecture in Core and plugins? Thanks! |
I have to admit I sort of forgot this issue :D Working on it right now with some pull requests incoming soon! |
After the merge of #12405 this should be finally completed. After all there is no longer any build running on the old |
-> Goal of this issue is to use the latest Travis CI infrastructure documented here
Current status
Recently our builds were running on the latest Travis CI infrastructure and they were failing with the message below. For now we reverted to use the older infrastructure in 485f61e and 6846058
First error on new distribution
from here: https://travis-ci.org/piwik/piwik/jobs/269029296
Timeline
As travis explains it seems that we will need to upgrade in the next few weeks:
The text was updated successfully, but these errors were encountered: