Travis CI integration is broken

[pbauer]

Since plone.api is now part of the core does it make sense to have a travis-setup it in this package?

[hvelarde]

I think is easier to catch errors in Travis than having to wait for builds on Jenkins, but it's up to the testing team.

I can help fixing the builds, but on Thursday or Friday.

[hvelarde]

@loechel Travis is still broken and I don't understand the current setup; I need you help on this or I'll will have to completely remove the use of tox.

@gforcada can you help here?

[gforcada]

@hvelarde why has a testing related issue be a blocker? 🤔 one can still test pull requests with jenkins, so there is no blockage IMHO.

[gforcada]

as for the problem at hand, looking at the logs it feels like there is a missing pypi.org link missing in buildouts? 🤔

[hvelarde]

@gforcada because we can't merge fixes or new features without testing; are plone.api tests running in Jenkins? where is the status?

[idgserpro]

I run the buildout locally and had the same problem with Travis:

Couldn't find index page for 'zc.recipe.testrunner' (maybe misspelled?)
Getting distribution for 'zc.recipe.testrunner==1.2.1'.
Couldn't find index page for 'zc.recipe.testrunner' (maybe misspelled?)
While:
  Installing.
  Getting section test.
  Initializing section test.
  Installing recipe zc.recipe.testrunner.
  Getting distribution for 'zc.recipe.testrunner==1.2.1'.
Error: Couldn't find a distribution for 'zc.recipe.testrunner==1.2.1'.

So I removed the allow-hosts from the buildout and it run normally.

@hvelarde @gforcada @jaroel