[
https://issues.apache.org/jira/browse/HADOOP-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905450#comment-15905450
]
Steve Loughran commented on HADOOP-14162:
-----------------------------------------
At this point I will note that
* I don't think there's a rush to have a bash script we all fear
* there's got to be lots of other projects work to reuse
* I'd like to see more use of GPG signing in the process, for git tags as well
as artifacts.
* It's good to automate validation checks of the published artifacts too, such
as a downstream build from the maven repo, untar & build of the source.
I will draw attention to the Slider release.xml file for Ant, which includes
downloads of the staged artifacts with checksum validation, GPG signing and
some other things:
https://github.com/apache/incubator-slider/blob/develop/bin/release.xml , Even
so, there's steps in there related to JIRA and maven which you end up doing by
hand.
Spark has some good tooling, including some [python
modules|https://github.com/apache/spark/blob/master/dev/create-release/releaseutils.py]
which use some github and JIRA modules to work better with the tooling. I
think that might be a good starting point.
The other thing is to consider if/how this could relate to Yetus: we should be
able to automate the entire release process right up to that point where secret
credentials are required.
> 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 confirmation
> * Before dangerous steps (eg. bulk jira update) we can ask for confirmation
> and explain the
> * 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
