You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/12/19 17:56:00 UTC

[jira] [Commented] (METRON-1374) Script the RC checking process

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

ASF GitHub Bot commented on METRON-1374:
----------------------------------------

GitHub user ottobackwards opened a pull request:

    https://github.com/apache/metron/pull/876

    METRON-1374 Script Metron Release Validation

    This PR introduces a script that automats the documented process for validation of metron releases.
    
    It will:
    
    Download the files
    Install the keys
    Validate the signatures
    Build and test metron + rpms
    Start full dev
    
    
    to test ( with RC2 )
    
    ```bash
    %> cd build_utils/release-utils
    %> bash ./metron-rc-check 0.4.2 RC2 0.1.0
    
    where 0.4.2 is the release number, RC2 is the RC, 0.1.0 is the bro plugin version
    
    When asked, enter yes (y) for testing and full dev
    
    
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). 
    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    
    ### For code changes:
    - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
    - [x] Have you included steps or a guide to how the change may be verified and tested manually?
    - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ottobackwards/metron rc-check

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/876.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #876
    
----
commit 8decec26050d8580b38456a3c5ec03d2c1456ced
Author: Otto Fowler <ot...@gmail.com>
Date:   2017-12-19T17:47:07Z

    rc checking script

----


> 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)