hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14162) Improve release scripts to automate missing steps
Date Mon, 13 Mar 2017 08:02:04 GMT

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

Elek, Marton commented on HADOOP-14162:

Thanks for the ideas. I will check the implementation of slider/spark release scripts.

>From a quick view: I like the approach, where the instructions for a non-automatizable
steps are printed out at the right time during the release process. eg https://github.com/apache/incubator-slider/blob/develop/bin/release.xml#L612

The advantages of an Ant based script is that it supports the dependency handling and exclude/include
steps out of the box. But I also like the simplicity of the current create-release script
in bash.

I have an idea to move out the implementation of the exact steps to separated files. Such
like here:


First, I would like to add additional steps, and It would help to keep the script itself simple,
and it is a quite simple change. (I also added an additional arguments to run only one step
in the process without the whole workflow). ((With this approach (long term) we can even implement
separated steps in different languages (for example in python).))  

[~aw] Could you please review/comment the commit above. If this is a good step forward I will
finalize it and create real patch from it.

> Improve release scripts to automate missing steps
> -------------------------------------------------
>                 Key: HADOOP-14162
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14162
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
> According to the conversation on the dev mailing list one pain point of the release making
is that even with the latest create-release script a lot of steps are not automated.
> This Jira is about creating a script which guides the release manager throw the proces:
> Goals:
>   * It would work even without the apache infrastructure: with custom configuration (forked
repositories/alternative nexus), it would be possible to test the scripts even by a non-commiter.
>   * every step which could be automated should be scripted (create git branches, build,...).
if something could be not automated there an explanation could be printed out, and wait for
>   * Before dangerous steps (eg. bulk jira update) we can ask for confirmation and explain
>   * The run should be idempontent (and there should be an option to continue the release
from any steps).  

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message