[
https://issues.apache.org/jira/browse/METRON-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297173#comment-16297173
]
ASF GitHub Bot commented on METRON-1374:
----------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/876
@ottobackwards I am using this to validate the current release candidate.
Works great.
Small nit pick... Any chance we could use proper flags for the args and a
--help? Maybe something like...
* -v / --version,
* -c / --candidate
* -pv / --plugin-version
* -h / --help
That's what I did with the `release-utils/validate-jira-for-release`.
Although, I would totally accept this as-is, as this is a really handy script
to have. Your choice.
Either way, +1 from me.
> Script the RC checking process
> ------------------------------
>
> Key: METRON-1374
> URL: https://issues.apache.org/jira/browse/METRON-1374
> Project: Metron
> Issue Type: Improvement
> Reporter: Otto Fowler
> Assignee: Otto Fowler
>
> There are several steps to validating a release for metron.
> These can be scripted, such that they are easier to run.
> This script should:
> * create a working directory
> * download the KEYS
> * download the release files ( metron and bro plugin ) as asc files
> * add the keys
> * validate the downloaded files
> * optionally build and test metron, including rpm builds
> * optionally start full_dev
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
