3 ms·
For testing there are quite a few good remote solutions. Here are a couple I'm familiar with. https://developer.github.com/v3/guides/building-a-ci-server/ http
by figgis 9y ago
For testing there are quite a few good remote solutions. Here are a couple I'm familiar with.
https://developer.github.com/v3/guides/building-a-ci-server/ https://developer.github.com/v3/guides/building-a-ci-server/
https://docs.gitlab.com/ee/ci/examples/README.html https://docs.gitlab.com/ee/ci/examples/README.html
My simplified workflow is: do work locally using whatever IDE I desire -> create a pull request -> server runs the tests and puts the results in the pull request. Much faster than running the same tests on my local machine as well.
With the tests being done remote you will also likely not need to commit such large amounts of data that it becomes a problem.
> Working with a local environment and 4g connection is fine, because 4g is more than enough to look up docs. But working with a distant environment and 4g connection is very slow and unreliable.
Normally even if you are working remote it's expected that you have a stable, decent, connection. But even without one there are plenty of great options.
For documentation I actually keep that local using https://devdocs.io/ https://devdocs.io/.
Without internet you don't have sites like stackoverflow and that's a downside that really can't be fixed without some serious work.
- conradk 9y ago> Much faster than running the same tests on my local machine as well. That sounds odd. Usually, while developing, running the whole test suite is unnecessary. So running tests is very fast, as long as you only run the tests that may fail after recent changes. At least that's my experience. > not need to commit such large amounts of data that it becomes a problem Not sure what you mean here. Mind clarifying ? > if you are working remote it's expected that you have a stable, decent, connection Definitely ! And 90% of the time I do have a stable connection. But that 10% where I don't (because the wifi breaks down, or I'm on a train to a nearby town), having a remote environment would not work. That's my use case for having a local environment. > For documentation I actually keep that local using https://devdocs.io/ https://devdocs.io/. Wow, that's cool ! I wasn't aware it worked offline ! Will definitely have a look at this. Thanks :)