hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8914) Automate release builds
Date Fri, 12 Oct 2012 19:47:04 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475287#comment-13475287

Robert Joseph Evans commented on HADOOP-8914:

+1 for that.  I have the beginnings of a script that I would be happy to donate to the effort.
 However that is the script that caused the signing issues.  The big problem I see is how
do we sign the builds?  I am not really sure I trust putting my PGP private key on the jenkins
build hosts, and giving jenkins my password to decrypt it.
> Automate release builds
> -----------------------
>                 Key: HADOOP-8914
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8914
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: Eli Collins
> Hadoop releases are currently created manually by the RM (following http://wiki.apache.org/hadoop/HowToRelease),
which means various aspects of the build are ad hoc, eg what tool chain was used to compile
the java and native code varies from release to release. Other steps can be inconsistent since
they're done manually eg recently the checksums for an RC were incorrect. Let's use the jenkins
toolchain and create a job that automates creating release builds so that the only manual
thing about releasing is publishing to mvn central.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message