+ [2013-06-15T19:10:01Z] travis-ci [travis-ci] Build details : http://travis-ci.org/jekyll/jekyll-import/builds/8120228
+ [2013-06-15T19:10:01Z] travis-ci [travis-ci] Change view : https://github.com/jekyll/jekyll-import/compare/fbf9752aacc1^...1aaeea98e410
+ [2013-06-15T19:14:08Z] travis-ci [travis-ci] Build details : http://travis-ci.org/jekyll/jekyll-import/builds/8120265
+ [2013-06-15T19:14:07Z] travis-ci [travis-ci] Change view : https://github.com/jekyll/jekyll-import/compare/970be655fc73...3c3851256d17
+ [2013-06-15T19:14:07Z] travis-ci [travis-ci] jekyll/jekyll-import#37 (master - 3c38512 : Parker Moore): The build failed.

message no. 3054

Posted by travis-ci in #jekyll at 2013-06-15T12:21:45Z

[travis-ci] Change view : https://github.com/mojombo/jekyll/compare/76e5b7fa13a6...872eba313c68
+ [2013-06-16T21:39:01Z] lehrblogger Hi, I've been using Jekyll's built-in dev server, which watches for changes and re-generates files automatically.
+ [2013-06-16T21:39:04Z] lehrblogger This is great, some template changes affect many output files, so it can be a bit slow.
+ [2013-06-16T21:39:16Z] lehrblogger Is there a way to run a Jekyll dev server that renders the templates as they are requested?
+ [2013-06-16T23:04:38Z] RobW_ lehrblogger: No, unfortunately, because a change in one file may affect others.
+ [2013-06-16T23:04:47Z] RobW_ So the whole site has to be rebuilt.