Allow re-rendering after config has changed #7

Activity

1. rf commented on Jan 16, 2015

   

   rf

   on Jan 16, 2015

   Owner

   More actions

   Yeah the way I used to get around this was to just find images/ | xargs touch. touch will just set their last modified date to the current time, so that'll force rebuild. But yeah, that would be a cool feature.
2. jamchamb

   self-assigned this

   on Jan 18, 2015
3. jamchamb

   closed this as completedin #8on Jan 19, 2015
4. jamchamb commented on Jan 19, 2015

   

   jamchamb

   on Jan 19, 2015

   CollaboratorAuthor

   More actions

   I might've jumped the gun on this one. It works, but all output groups will be re-rendered after the config is updated, whereas we really only want to re-render the specific groups that were updated. To do that, we'd have to keep track of the properties used to generate each output file.

   It might be possible to use a flat-file to store hashes of each outputConfig by group and do a re-render if we come across an outputConfig that hasn't been seen before (and then prune the ones that no longer exist) in addition to re-rendering when the source images change.

   In the meantime, should I undo the changes to ModCheck? I could also just put a --rerender <group(s)> option in its place until something more automatic is implemented.
5. jamchamb

   reopened this on Jan 19, 2015
6. jamchamb

   added 3 commits that reference this issue on Jan 19, 2015

   Undo changes to ModCheck, see rf#7

   e0910ed

   Undo changes to ModCheck, see rf#7

   0412632

   Merge pull request #9 from jamchamb/undo-mod-check

   ...

   1420a4a
7. jamchamb

   added a commit that references this issue on Jan 30, 2015

   One approach to address rf#7

   ...

   a0e930b
8. jamchamb commented on Apr 2, 2015

   

   jamchamb

   on Apr 2, 2015

   CollaboratorAuthor

   More actions

   I've been using a simple modification that just puts a hash of the output description into the filename of the build files, and it works pretty well (I think the 9patch plugin has to be updated to work with it, though). The only issue is leftover obsolete build images, but it shouldn't be hard to add a command line option for pruning out configs that no longer exist in images.yaml.
9. jamchamb

   added a commit that references this issue on Feb 5, 2016

   Squashed commit of hashing branch:

   ...

   b6ef543