This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new ff10c955 add Reproducible Builds check instructions
ff10c955 is described below
commit ff10c955ad6c04bb96a666cebab3f234fefa3915
Author: Hervé Boutemy <hbout...@apache.org>
AuthorDate: Sun Oct 27 17:32:58 2024 +0100
add Reproducible Builds check instructions
---
content/apt/guides/development/guide-testing-releases.apt | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/content/apt/guides/development/guide-testing-releases.apt
b/content/apt/guides/development/guide-testing-releases.apt
index 7b5cc24f..c1a980c0 100644
--- a/content/apt/guides/development/guide-testing-releases.apt
+++ b/content/apt/guides/development/guide-testing-releases.apt
@@ -62,6 +62,15 @@ Guide to Testing Staged Releases
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.
+Checking Reproducible Builds
+
+ Checking binary output, ideally to control that the build is reproducible,
can be done by running <<<verify>>> (NOT <<<install>>>) followed by
<<<artifact:compare>>> against the staged content:
+
+-----
+mvn -Papache-release -Dgpg.skip clean verify \
+ artifact:compare
-Dreference.repo=https://repository.apache.org/content/groups/staging/
+-----
+
* Setting up Archiva to Test Staged Releases
These steps will be similar for any repository manager - please refer to
their individual documentation for instructions on how to
