THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<properties> <sp.version>0.66.0-SNAPSHOT</sp.version> </properties> |
incubator-streampipes-
...
The next step is to prepare the extensions project for a release. The required steps are almost identical to the previous steps:
If needed, change the current SNAPSHOT version to the version that is planned for the upcoming release:
| Code Block | ||||
|---|---|---|---|---|
| ||||
# in incubator-streampipes-extensions
# Make sure to only use a SNAPSHOT version here
mvn versions:set -DnewVersion=0.66.0-SNAPSHOT
# Check the output and briefly check if all changed version numbers in the POM files are ok
mvn versions:commit
# Open the incubator-streampipes-extensions parent pom and change the parent version and the streampipes.version property to the SNAPSHOT version.
# Commit and push the changes to dev |
Afterwards, create a new branch for the upcoming release candidate:
| Code Block | ||||
|---|---|---|---|---|
| ||||
# Create a release branch by replacing VERSION with the intended release version
mvn release:branch -DbranchName=rel/VERSION -DautoVersionSubmodules=true
# In dev, update the streampipes.version property and the parent version to the next development version, e.g.:
<parent>
<groupId>org.apache.streampipes</groupId>
<artifactId>streampipes-parent</artifactId>
<version>0.67.0-SNAPSHOT</version>
</parent>
<streampipes.version>0.67.0-SNAPSHOT</streampipes.version>
# Commit and push all changes to dev |
incubator-streampipes-installer
Create a release branch from dev:
...
The following build tools need to be installed to properly test a release candidate:
- JDK (tested with JDK 8+starting from v0.70, JDK 11 is the new minimum java version)
- Maven (tested with 3.6)
- NodeJS + NPM (tested with v12+/ v6+)
- Docker + Docker-Compose
...
First, create a new folder and checkout the release branches of both projects incubator-streampipes and incubator-streampipes-extensions:
| Code Block | ||||
|---|---|---|---|---|
| ||||
# Clone & checkout a clean copy from the release branch mkdir test-streampipes-rc && cd test-streampipes-rc git clone git@github.com:apache/incubator-streampipes.git git clone git@github.com:apache/incubator-streampipes-extensions.git # ALTERNATIVE: git clone https://github.com/apache/incubator-streampipes.git # ALTERNATIVE: git clone https://github.com/apache/incubator-streampipes-extensions.git cd incubator-streampipes # Change VERSION to the current release branch git checkout rel/VERSION cd ../incubator-streampipes-extensions # Change VERSION to the current release branch git checkout rel/VERSION |
Setup test environment
| Anchor | ||||
|---|---|---|---|---|
|
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
# Go back to the main directory of incubator-streampipes docker-compose up # ALTERNATIVE: docker-compose up -d. # Start container in background. # This will build the Docker images for the streampipes-backend and the streampipes-connect-master modules. In addition, it will start several 3rd party Docker containers that are # mandatory for StreamPipes, e.g., CouchDB and Consul. Again, be aware that this docker-compose configuration does not include volume persistency and should therefore only be used for # short-term testing. # Force rebuild of images before starting (e.g. after bug fix): docker-compose build |
incubator-streampipes-extensions
Now we'll build and start the extensions project:
...