beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (BEAM-2727) Make Beam released artifacts reproducible
Date Fri, 04 Aug 2017 12:36:00 GMT

    [ https://issues.apache.org/jira/browse/BEAM-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114308#comment-16114308
] 

Jean-Baptiste Onofré commented on BEAM-2727:
--------------------------------------------

It sounds interesting. Thanks !

> Make Beam released artifacts reproducible
> -----------------------------------------
>
>                 Key: BEAM-2727
>                 URL: https://issues.apache.org/jira/browse/BEAM-2727
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system
>    Affects Versions: Not applicable
>            Reporter: Ismaël Mejía
>            Assignee: Ismaël Mejía
>            Priority: Minor
>
> There is a recent movement to create a verifiable path from source code to binary releases
in different open source projects. See http://reproducible-builds.org/
> For the case of Java binaries (classes and jars) if we want to have a reproducible build
we need to have a consistent build environment so we can reproduce those.
> For Beam we need to create an environment with a fixed version of the Java compiler,
maven and its plugins. This is addressed by BEAM-1534. But also by including the (JDK/Maven
versions) used to generate the jar artifacts in the information to validate at the vote. Additionally
we need to fix the Jar files because by default the maven-jar-plugin include the timestamp
of the build in the files which breaks the reproducibility of the process, fortunately there
is a Maven plugin that fixes this and that we can include in the release build.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message