Another very common requirement for builds is generating checksums on your files. We've got you covered here now as well. Run
checksum help for even more options.
checksum file.txt checksum path=build.zip algorithm=SHA-256
command( 'checksum' ) .params( 'file.txt' ) .run(); command( 'checksum' ) .params( path = 'build.zip', algorithm = 'SHA-256' ) .run();
You can provide a file globbing pattern to receive a checksum for all files in a directory that match that pattern.
checksum command also supports some other popular formats for outputting checksums. The default format is
checksum path=**.cfc format=checksum checksum path=**.cfc format=sfv checksum path=**.cfc format=md5sum
checksum command will also write out a file that contains the hash which is a common requirement for builds that produce artifacts.
Write checksum(s) to a file named after the original file plus a new extension. This will create a file called
checksum myFile.zip md5 --write
Control the file extension like so. (
--write is optional when supplying an extension) This will create a file called
checksum path=myFile.zip extension=hash --write
You can check a file against an existing checksum to make sure the file hasn't changed.
checksum path=myFile.zip verify=2A95F32028087699CCBEB09AFDA0348C