Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build only changed files with grunt-newer dosen't work #29

Open
tobiasharth opened this issue Oct 12, 2015 · 1 comment
Open

build only changed files with grunt-newer dosen't work #29

tobiasharth opened this issue Oct 12, 2015 · 1 comment

Comments

@tobiasharth
Copy link

Hey there,

i will use Assemble like the description on the installation-site with the grunt-newer task, but it build always the whole page with 1000+ pages.

My Assemble task in the Gruntfile:

 assemble: {
      options: {
        assets: "contents/assets",
        data: "config.json",
        layoutdir: "templates",
        layout: "default.hbs",
        partials: "templates/partials/**/*.hbs",
        helpers: ["lib/helpers/*.js" ]
      },
      project: {
        options: {},
        files: {
          "sites/_default/public": ["contents/**/*.md" ]
        }
      }
    },

The content tree is like:

|- contents
    |--- docs
    |     |--- current
    |     |     |--- lorem ipsum
    |     |           |--- lorem-ipsum.md
    |     |--- versions
    |           |--- v.1.0.1
    |           |--- v.1.0.2
    |           |--- v.1.0.3
    |                 |--- lorem ipsum
    |                       |--- lorem-ipsum.md
    |--- product
    |--- start

What is wronge? Do you support grunt-newer with single changed files? Is there a failure in grunt-newer or in my Gruntfile?

Cheers,
Tobi

@blmyr
Copy link

blmyr commented Oct 16, 2015

Hey there,

grunt-newer works and only runs the assemble task if a file has changed but I guess assemble is designed to always build all the pages. So it will only run if there have been changes but then it will build everything. It would be great though if this could be implemented since it would speed up a continuous build process by a great amount.

Cheers,
Daniel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants