View more context

 

wmk

@digitall_it https://stackoverflow.com/questions/21053657/how-to-run-travis-ci-locally well, could be worth a try

Show 1 attachment(s)
Stack Overflow  
How to run travis-ci locally

I've just joined a project, and I'm new to travis-ci. I'd rather not have to push every little change to .travis.yml and every little change I make to the source in order to run the build. With j...

Hide attachment content
andante

ok but TravisCI because you want to run your tests?

sander_ha

Is anyone here using HTTP2? (optimising for it)

wmk

ping @dorsetdigital @lerni ^^ afaik Tim made a module for HTTP2 prefetching

sander_ha

It seems to be quite well supported in most browsers these days

lerni

Using http/2 for a while - it really makes a difference. Have to check that module 🙂

sander_ha

@lerni What has stood out the most when using http/2? Performance? 🙂

lerni

well its about transport and there you gain ~30% - if you use server-push for critical requirements it makes first load quiet a bit faster. but it boils down to have less page-speed-insight complains 😉


Show less replies
andante

assuming you have all the dependencies installed locally, you could trigger a background job to run all your tests on commit to master or whatever

digitall_it

I use a vagrant box, that hook would have to run on the box but not on the host

andante

i mean obviously a UI and executing async is nice, but it depends where you want to optimise for

wmk

@digitall_it gitlab would also be a possible solution. It comes with a CI solution, but I didn't set it up yet