svn commit: r1921599 - /maven/website/content/guides/development/guide-testing-releases.html

[sv...@apache.org]

Author: svn-site-role
Date: Sun Oct 27 16:35:35 2024
New Revision: 1921599

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/development/guide-testing-releases.html

Modified: maven/website/content/guides/development/guide-testing-releases.html
==============================================================================
--- maven/website/content/guides/development/guide-testing-releases.html (original)
+++ maven/website/content/guides/development/guide-testing-releases.html Sun Oct 27 16:35:35 2024
@@ -163,7 +163,12 @@
     </pluginRepository>
   </pluginRepositories>
   ...</pre></div>
-<p>The important thing is that the staged release does not pollute your eventual environment as it may change if the vote fails and the release is made again. This is why clearing the local repository is necessary, but if you are using a repository manager this is also important to clear. The following provides instructions for setting Archiva up in such a way that the artifacts are isolated already.</p><section>
+<p>The important thing is that the staged release does not pollute your eventual environment as it may change if the vote fails and the release is made again. This is why clearing the local repository is necessary, but if you are using a repository manager this is also important to clear. The following provides instructions for setting Archiva up in such a way that the artifacts are isolated already.</p></section><section>
+<h1>Checking Reproducible Builds</h1>
+<p>Checking binary output, ideally to control that the build is reproducible, can be done by running <code>verify</code> (NOT <code>install</code>) followed by <code>artifact:compare</code> against the staged content:</p>
+<div class="verbatim">
+<pre>mvn -Papache-release -Dgpg.skip clean verify \
+    artifact:compare -Dreference.repo=https://repository.apache.org/content/groups/staging/</pre></div><section>
 <h2>Setting up Archiva to Test Staged Releases</h2>
 <p>These steps will be similar for any repository manager - please refer to their individual documentation for instructions on how to configure remote proxies.</p>
 <p>For Archiva, the first step is to create a new managed repository for the staged releases. This will ensure they remain isolated from your environment. On the repositories tab, add a new managed repository with the settings:</p>