Using drush's cache for release_info_fetch drastically speeds up testing. However, when running this on d.o., this patch would still allow specifying --no-cache so the most up-to-date release info is available when verifying make files.

CommentFileSizeAuthor
#1 1443410-1.drupalorg_drush-use-cache.patch741 bytesdww
drupalorg_drush-use-cache.patch736 bytesjhedstrom

Comments

dww’s picture

dww
we/he/they
commented
StatusFileSize
new 1443410-1.drupalorg_drush-use-cache.patch741 bytes

Rerolled after recent changes. However, I've got some concerns. This seems to be a global thing, not something we're setting just around the release_info_fetch() code and resetting. Therefore:

A) Does this setting impact anything else drush make is doing while it runs? I don't know, but I wanted to ask. Don't have time today to do a more thorough audit, but I wanted to raise it.

B) If it's just a global thing, why not do this once inside drupalorg_drush_drush_init() instead of doing it over and over inside drupalorg_drush_find_release_node() (which could be called dozens of times on a moderately complex .make file).

Thoughts?

Thanks,
-Derek