[
https://issues.apache.org/jira/browse/DRILL-8158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693675#comment-17693675
]
ASF GitHub Bot commented on DRILL-8158:
---------------------------------------
hboutemy commented on PR #2766:
URL: https://github.com/apache/drill/pull/2766#issuecomment-1445406594
I'd love that it could be feasible, but I don't think CI is able to check
reproducibility
another aspect is that we currently have no regression, but just fixes that
are done step by step: once we have fixed one issue that creates a lot of
noise, next release shows issues that are less noisy, then were not much
visible before
IMHO, we just need to accept that for such big project, having a build that
is fully reproducible requires multiple iterations: that's not unexpected
I'm confident that once this PR is merged, the remaining issues will impact
much less content
> Remove non-reproducible build outputs
> -------------------------------------
>
> Key: DRILL-8158
> URL: https://issues.apache.org/jira/browse/DRILL-8158
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.20.0
> Reporter: Herve Boutemy
> Assignee: James Turton
> Priority: Major
> Fix For: 1.20.2
>
>
> For context see [1] and [2]. The git-commit-id plugin includes information
> like build host, email and time which is not compatible with a reproducible
> build. Drill's built in sys.version table will return the build email and
> time if they are present in the build's git.properties file so these columns
> must be deprecated. Other useful Git-related information is retained.
> In accompanying commits, some Kerberos unit test fixes are applied, and the
> tests reenabled, and some updates to Release.md are included.
> [1] [https://maven.apache.org/guides/mini/guide-reproducible-builds.html]
> [2]
> [https://github.com/jvm-repo-rebuild/reproducible-central#org.apache.drill:drill-root]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
