First of all, thanks for taking the time to validate an Apache StreamPipes (incubating) release!

The following steps should help you in performing the necessary steps to validate a release. Any comments or improvements to this guide are highly appreciated!

Introduction

An Apache StreamPipes release currently consists of one source releases:

• incubator-streampipes is the core of Apache StreamPipes
  • This also contains all the extensions (> 20 adapters and > 100 pipeline elements) & the installer (containing files for docker, a CLI, and helm charts for Kubernetes)

Validation

Prerequisites

For fully testing a release candidate, you should have the following installed on your system:

• JDK (tested with JDK 8+)
• Maven (tested with 3.6)
• NodeJS + NPM (tested with v12+/ v6+)
• Docker + Docker-Compose

Step 1: Download release artifacts

Download all staged artifacts under the url specified in the release vote email into a directory we’ll now call download-dir.

The artifacts are available at https://dist.apache.org/repos/dist/dev/incubator/streampipes 

Typically, this includes one zip files along with checksum, signature, README, RELEASE_VALIDATION and RELEASE_NOTES.

You can either download the release artifacts one by one, or use the convenient single line command below:

# download all release artifacts (core, extensions, installer)
wget --recursive --no-host-directories -e robots=off --cut-dirs=5 --no-parent --reject "index.html*" https://dist.apache.org/repos/dist/dev/incubator/streampipes/

Step 2: Validate incubator-streampipes

First, open the folder ({version}/{rc}) (e.g., 0.69.0/rc1).

Check signatures and checksums

Verify the signature

If the output says "public key not found", follow the instructions in this guide: Validate a release for the first time

gpg --verify apache-streampipes-{current-full-version}-incubating-source-release.zip.asc apache-streampipes-{current-full-version}-incubating-source-release.zip

# example
gpg --verify apache-streampipes-0.69.0-incubating-source-release.zip.asc apache-streampipes-0.69.0-incubating-source-release.zip

Verify the checksum

sha512sum -c apache-streampipes-{current-full-version}-incubating-source-release.zip.sha512

# example:
sha512sum -c apache-streampipes-0.68.0-incubating-source-release.zip.sha512

# alternative (if you get an error such as no properly formatted SHA512 checksum lines found)
# print the checksum
cat apache-streampipes-0.68.0-incubating-source-release.zip.sha512
# print the checksum of the zip file
sha512sum apache-streampipes-0.68.0-incubating-source-release.zip
# compare both checksums

Make sure the output says OK.

Check source release

Unzip the source file

Unzip and switch to the parent directory (where the README and pom files are located) 

unzip apache-streampipes-{current-full-version}-incubating-source-release.zip
cd apache-streampipes-{current-full-version}-incubating/

# example:
unzip apache-streampipes-0.68.0-incubating-source-release.zip

cd apache-streampipes-0.68.0-incubating/

Verify legal information and required files

• Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES and RELEASE_VALIDATION files in the extracted source bundle.
• Check the LICENSE file
• Check the NOTICE file (e.g., make sure the year is correct)

Run RAT

mvn rat:rat

Search for SNAPSHOT dependencies

Search for any unexpected SNAPSHOT dependencies in the bundle, e.g.:

grep -rnw './' -e 'SNAPSHOT'

# Check the output

Search for unexpected binaries

Have a look at the source code to check there are no unexpected binaries, e.g., in the ui folder there shouldn't be any node_modules folder or dist folder.

Build backend & UI

From the parent folder of the core, do the following to build the Java-based core:

# in download directory
mvn clean package

This build should be successful.

The next step is to build the UI, switch to the ui directory and do the following:

# cd ui

npm install
# If this results in an error, do npm install --legacy-peer-deps

npm run build

Start test system 

If you want to test the system, there is a convenience docker-compose file that will help you starting the release candidate for testing.

Go back to the main directory of the core release artifact (where the docker-compose.yml file is located) and do the following:

# this might be optional - seems to only occur in rare cases on Windows systems

# Set the correct EOL encoding for the UI entrypoint file (docker-entrypoint.sh) file to LF:
awk 'BEGIN{RS="^$";ORS="";getline;gsub("\r","");print>ARGV[1]}' ui/docker-entrypoint.sh

# Alternative: Open the file ui/docker-entrypoint.sh, change the eol encoding to "LF" (e.g., in Notepad++ by clicking on "Windows CRLF" in the bottom status bar).

docker-compose up --build -d

# Use docker-compose up to run it in foreground
# Docker images will be locally built

Once you're done with that, proceed to the next step. 

Step 2: Test

If you have started the core and extensions in Docker as explained in the previous step, you can now switch to the user interface to do functional testing:

Open your browser and go to http://localhost (port 80) to get to the StreamPipes UI. You'll see the login screen:

• Default user email: admin@streampipes.apache.org
• Default password: admin

Once you are logged in, you can test the functionalities of the software.

Step 5: Clean Up

After finishing testing the StreamPipes, one can stop and remove all running containers and clean up your host using the following two commands.

docker stop $(docker ps -a -q)
docker system prune --volumes

Validation Template

See also the Incubator Release Checklist (which is not official policy, but may help)

Here is a template that can help you validating a release:

• Download all staged artifacts under the url specified in the release vote email
• Verify the signature is correct
• Check if the signature references an Apache email address
• Verify the SHA512 checksum
• Unzip the archive
• Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES, RELEASE_VALIDATION files in the extracted source bundle.
• Run RAT
• Search for SNAPSHOT dependencies
• Build Backend
• Build UI
• Build and Run Test system on Docker