(Re-) enable travis as CI about fosckeditorbundle HOT 6 CLOSED

What about moving to what is recommended in Symfony documentation ? https://symfony.com/doc/current/bundles/best_practices.html#continuous-integration

from fosckeditorbundle.

the config should indeed be cleaned:

• not requiring a Symfony version for each job (and using the locking package for jobs testing a specific versions rather than changing requirements)
• I suggest using separate commands in the travis.yml rather than an external script, as this allows seeing the different commands in the Travis logs
• drop the docker-based job (not worth running docker inside the Travis container IMO)

from fosckeditorbundle.

We should also enable the appveyor build as we have the config for it

from fosckeditorbundle.

completely 👍 i really like the config proposed in best practices. And i really like the script idea, as i can reuse those scripts locally to get a specific setup.

from fosckeditorbundle.

I'm suggesting not using them anymore (they are quite unlikely to be usable locally anyway)

from fosckeditorbundle.

We should'nt have that much of commands to execute, so i can go with it. We can discuss scripts or not on an other issue/meeting/conference :-).

from fosckeditorbundle.