You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2014/01/30 20:32:10 UTC

[jira] [Commented] (HADOOP-10313) Script and jenkins job to produce Hadoop release artifacts

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

Alejandro Abdelnur commented on HADOOP-10313:
---------------------------------------------

a {{create-release.sh}} script would produce the release artifacts. This script would be committed in the dev-support/ directory of the branch.

A parameterized jenkins jobs would take the branch name and the RC label and it would produce the release artifacts.

The SRC and BIN tarballs would be MD5 but not signed. The release manager should pick up the artifacts and sign them before pushing them to a public staging area.

> Script and jenkins job to produce Hadoop release artifacts
> ----------------------------------------------------------
>
>                 Key: HADOOP-10313
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10313
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.3.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> As discussed in the dev mailing lists, we should have a jenkins job to build the release artifacts.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)