Apache NiFi 1.8.0 RC1 Release Helper Guide

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Apache NiFi 1.8.0 RC1 Release Helper Guide

Jeff-2
Hello Apache NiFi community,

Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.

# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS

# Import keys file:
gpg --import KEYS

# [optional] Clear out local maven artifact repository

# Pull down nifi-1.8.0 source release artifacts for review:

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.asc
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.sha256
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.sha512

# Verify the signature
gpg --verify nifi-1.8.0-source-release.zip.asc

# Verify the hashes (sha256, sha512) match the source and what was provided
in the vote email thread
shasum -a 256 nifi-1.8.0-source-release.zip
shasum -a 512 nifi-1.8.0-source-release.zip

# Unzip nifi-1.8.0-source-release.zip

# Verify the build works including release audit tool (RAT) checks
cd nifi-1.8.0
mvn clean install -Pcontrib-check,include-grpc

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.

Thank you for your time and effort to validate the release!
Reply | Threaded
Open this post in threaded view
|

Re: Apache NiFi 1.8.0 RC1 Release Helper Guide

Otto Fowler
I don’t see a tag for nifi-1.8.0-RC1


On October 18, 2018 at 00:01:06, Jeff ([hidden email]) wrote:

Hello Apache NiFi community,

Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.

# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS

# Import keys file:
gpg --import KEYS

# [optional] Clear out local maven artifact repository

# Pull down nifi-1.8.0 source release artifacts for review:

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.asc
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.sha256
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.sha512

# Verify the signature
gpg --verify nifi-1.8.0-source-release.zip.asc

# Verify the hashes (sha256, sha512) match the source and what was provided
in the vote email thread
shasum -a 256 nifi-1.8.0-source-release.zip
shasum -a 512 nifi-1.8.0-source-release.zip

# Unzip nifi-1.8.0-source-release.zip

# Verify the build works including release audit tool (RAT) checks
cd nifi-1.8.0
mvn clean install -Pcontrib-check,include-grpc

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.

Thank you for your time and effort to validate the release!
Reply | Threaded
Open this post in threaded view
|

Re: Apache NiFi 1.8.0 RC1 Release Helper Guide

Jeff
Sorry Otto!  The tag [1] should be there now.

[1] *https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=tag;h=2fdc819e65481e609532312d18a41d30d58f16f3
<https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=tag;h=2fdc819e65481e609532312d18a41d30d58f16f3>*

On Thu, Oct 18, 2018 at 8:34 AM Otto Fowler <[hidden email]> wrote:

> I don’t see a tag for nifi-1.8.0-RC1
>
>
> On October 18, 2018 at 00:01:06, Jeff ([hidden email]) wrote:
>
> Hello Apache NiFi community,
>
> Please find the associated guidance to help those interested in
> validating/verifying the release so they can vote.
>
> # Download latest KEYS file:
> https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
> # Import keys file:
> gpg --import KEYS
>
> # [optional] Clear out local maven artifact repository
>
> # Pull down nifi-1.8.0 source release artifacts for review:
>
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.asc
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.sha256
> wget
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.8.0/nifi-1.8.0-source-release.zip.sha512
>
> # Verify the signature
> gpg --verify nifi-1.8.0-source-release.zip.asc
>
> # Verify the hashes (sha256, sha512) match the source and what was provided
> in the vote email thread
> shasum -a 256 nifi-1.8.0-source-release.zip
> shasum -a 512 nifi-1.8.0-source-release.zip
>
> # Unzip nifi-1.8.0-source-release.zip
>
> # Verify the build works including release audit tool (RAT) checks
> cd nifi-1.8.0
> mvn clean install -Pcontrib-check,include-grpc
>
> # Verify the contents contain a good README, NOTICE, and LICENSE.
>
> # Verify the git commit ID is correct
>
> # Verify the RC was branched off the correct git commit ID
>
> # Look at the resulting convenience binary as found in nifi-assembly/target
>
> # Make sure the README, NOTICE, and LICENSE are present and correct
>
> # Run the resulting convenience binary and make sure it works as expected
>
> # Send a response to the vote thread indicating a +1, 0, -1 based on your
> findings.
>
> Thank you for your time and effort to validate the release!
>