This patch adds an --md5 flag to generate a hash value for the entire build tree. Useful for identifying if a build has changed in some way and for testing drush_make!

Comments

yhahn’s picture

Cross platform problems already. Investigating.

yhahn’s picture

StatusFileSize
new2.46 KB

Ok, that was obviously broken. New version. Requires cksum.

Put the following in a tmp.make file:

core = 6.x
projects[] = drupal
projects[] = token

And then run

drush make --md5 tmp.make tmp

The hash I get is:

Build hash: 619fbe19a9b0d5d7fc462e375ef4b220
yhahn’s picture

StatusFileSize
new2.51 KB

Quick adjustment, looks like find can list files in different order across platforms. Sort hashes to handle this difference.

New hash for makefile above:

Build hash: bad9852cf11f33ce9502a793b567c730
langworthy’s picture

I created the tmp.make file in #2 including a newline at the end of line #3. I received the same build hash as #3

Build hash: bad9852cf11f33ce9502a793b567c730
yhahn’s picture

Title: --md5 option to generate a build hash » Use md5 build hashes for basic drush make testing
Status: Active » Needs review
StatusFileSize
new8.91 KB

- Small revision to md5 build hash. Previous version did not properly reflect file/directory location information. New version does.
- Introduces drush make-test [test] command. Each test is a registered as a makefile, any additional option flags, and a build hash that represents a correct build of that makefile.
- Very rudimentary tests for CVS, patching and no-patch-txt option.

dmitrig01’s picture

Status: Needs review » Reviewed & tested by the community

tested

yhahn’s picture

Status: Reviewed & tested by the community » Fixed

Committed. Now to write more tests!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.