[
https://issues.apache.org/jira/browse/HADOOP-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923984#comment-15923984
]
Steve Loughran commented on HADOOP-14162:
-----------------------------------------
I'm clearly biased towards ant rather than bash. I recognise that it's been a
while since the project moved off it, but it contains the core actions you need
for a release: packaging, signing, emailing. And we can extend it if we need
something private. I would far rather we put together an ant build script for
the steps of invoking maven and generating template emails than going into a
mess of bash scripts. Which are never, ever going to be maintained except badly
by java developers who don't "get" bash.
Why not lift the slider release.xml and play with it before running away.
w.r.t repeatability, +1. it'd be great it if could be a yetus option too
(excluding some signing).
Oh, one more thing to consider: you know there are actually python libs to work
with JIRA and github. Something to consider if those are needed. But again, not
a justification for using bash.
> 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]
