|
|
@@ -141,6 +141,31 @@ ignore the fact that it is part of your build file which may be |
|
|
|
readable by third parties. If you need more security, consider using |
|
|
|
the <a href="input.html">input task</a> to query for a password.</p> |
|
|
|
|
|
|
|
<p>Using a macro like the following</p> |
|
|
|
|
|
|
|
<pre> |
|
|
|
<macrodef name="get-and-checksum"> |
|
|
|
<attribute name="url"/> |
|
|
|
<attribute name="dest"/> |
|
|
|
<sequential> |
|
|
|
<get src="@{url}" dest="@{dest}"/> |
|
|
|
<get src="@{url}.sha1" dest="@{dest}.sha"/> |
|
|
|
<local name="checksum.matches"/> |
|
|
|
<local name="checksum.matches.fail"/> |
|
|
|
<checksum file="@{dest}" algorithm="sha" fileext=".sha" |
|
|
|
verifyproperty="checksum.matches"/> |
|
|
|
<condition property="checksum.matches.fail"> |
|
|
|
<equals arg1="${checksum.matches}" arg2="false"/> |
|
|
|
</condition> |
|
|
|
<fail if="checksum.matches.fail">Checksum error</fail> |
|
|
|
</sequential> |
|
|
|
</macrodef> |
|
|
|
</pre> |
|
|
|
|
|
|
|
<p>it is possible to download an artifacts together with its SHA1 |
|
|
|
checksum (assuming a certain naming convention for the checksum |
|
|
|
file, of course) and validate the checksum on the fly.</p> |
|
|
|
|
|
|
|
</body> |
|
|
|
</html> |
|
|
|
|