zeppelin/dev/create_release.sh

113 lines
4.7 KiB
Bash
Raw Normal View History

#!/bin/bash
#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# The script helps making a release.
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
# You need to specify release version and branch|tag name.
#
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
# Here are some helpful documents for the release.
# http://www.apache.org/dev/release.html
# http://www.apache.org/dev/release-publishing
# http://www.apache.org/dev/release-signing.html
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
BASEDIR="$(dirname "$0")"
. "${BASEDIR}/common_release.sh"
echo "${BASEDIR}/common_release.sh"
if [[ $# -ne 2 ]]; then
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
usage
fi
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
if [[ -z "${GPG_PASSPHRASE}" ]]; then
echo "You need GPG_PASSPHRASE variable set"
exit 1
fi
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
RELEASE_VERSION="$1"
GIT_TAG="$2"
function make_source_package() {
# create source package
cd ${WORKING_DIR}
cp -r "zeppelin" "zeppelin-${RELEASE_VERSION}"
${TAR} cvzf "zeppelin-${RELEASE_VERSION}.tgz" "zeppelin-${RELEASE_VERSION}"
echo "Signing the source package"
cd "${WORKING_DIR}"
echo "${GPG_PASSPHRASE}" | gpg --passphrase-fd 0 --armor \
--output "zeppelin-${RELEASE_VERSION}.tgz.asc" \
--detach-sig "${WORKING_DIR}/zeppelin-${RELEASE_VERSION}.tgz"
echo "${GPG_PASSPHRASE}" | gpg --passphrase-fd 0 \
--print-md MD5 "zeppelin-${RELEASE_VERSION}.tgz" > \
"${WORKING_DIR}/zeppelin-${RELEASE_VERSION}.tgz.md5"
echo "${GPG_PASSPHRASE}" | gpg --passphrase-fd 0 \
--print-md SHA512 "zeppelin-${RELEASE_VERSION}.tgz" > \
"${WORKING_DIR}/zeppelin-${RELEASE_VERSION}.tgz.sha512"
}
function make_binary_release() {
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
BIN_RELEASE_NAME="$1"
BUILD_FLAGS="$2"
cp -r "${WORKING_DIR}/zeppelin" "${WORKING_DIR}/zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}"
cd "${WORKING_DIR}/zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}"
[ZEPPELIN-1256][BUILD] Build distribution package with Spark 2.0 and Scala 2.11 ### What is this PR for? - build distribution package with Spark 2.0 and Scala 2.11 - change travis profile to use spark 2.0 instead of 2.0.0-preview by removing `-Dspark.version=2.0.0-preview` property - Change profile activation rule * current way of profile activation is not proper for supporting more than three scala version * -Pscala-2.11 activates both scala-2.10 and scala-2.11 profile without this patch ### What type of PR is it? Build ### What is the Jira issue? [ZEPPELIN-1256](https://issues.apache.org/jira/browse/ZEPPELIN-1256) ### How should this be tested? **Before** Run `mvn help:active-profiles -Pscala-2.11`: ``` Active Profiles for Project 'org.apache.zeppelin:zeppelin:pom:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-interpreter:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-zengine:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-display_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-display_2.11:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark-dependencies_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - spark-2.0 (source: org.apache.zeppelin:zeppelin-spark-dependencies_2.11:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - exclude-sparkr (source: org.apache.zeppelin:zeppelin-spark_2.11:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-markdown:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-angular:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-shell:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-livy:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-hbase:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-postgresql:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-jdbc:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-file:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-flink_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-ignite_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-kylin:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-python:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-lens:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-cassandra_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-elasticsearch:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-alluxio:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-web:war:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-server:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-server:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-distribution:pom:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-distribution:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) ``` **After** Run `mvn help:active-profiles -Dscala-2.11`: ``` Active Profiles for Project 'org.apache.zeppelin:zeppelin:pom:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-interpreter:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-zengine:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-display_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-display_2.11:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark-dependencies_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - spark-2.0 (source: org.apache.zeppelin:zeppelin-spark-dependencies_2.11:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - exclude-sparkr (source: org.apache.zeppelin:zeppelin-spark_2.11:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-markdown:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-angular:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-shell:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-livy:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-hbase:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-postgresql:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-jdbc:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-file:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-flink_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-ignite_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-kylin:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-python:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-lens:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-cassandra_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-elasticsearch:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-alluxio:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-web:war:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-server:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-server:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-distribution:pom:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-distribution:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) ``` ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? yes (for scala 2.11 build) Author: Mina Lee <minalee@apache.org> Closes #1251 from minahlee/ZEPPELIN-1256 and squashes the following commits: ff034c6 [Mina Lee] change scala-2.10 and scala-2.11 profile activation rule 99d91bf [Mina Lee] Update interpreter installation for the user who use Spark version <= 1.6.2 4ca3e7f [Mina Lee] Build distribution package with Spark 2.0 and Scala 2.11
2016-08-05 02:07:24 +00:00
./dev/change_scala_version.sh 2.11
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
echo "mvn clean package -Pbuild-distr -DskipTests ${BUILD_FLAGS}"
mvn clean package -Pbuild-distr -DskipTests ${BUILD_FLAGS}
if [[ $? -ne 0 ]]; then
echo "Build failed. ${BUILD_FLAGS}"
exit 1
fi
# re-create package with proper dir name with binary license
cd zeppelin-distribution/target/zeppelin-*
mv zeppelin-* "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}"
cat ../../src/bin_license/LICENSE >> "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}/LICENSE"
cat ../../src/bin_license/NOTICE >> "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}/NOTICE"
cp ../../src/bin_license/licenses/* "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}/licenses/"
${TAR} cvzf "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz" "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}"
# sign bin package
echo "${GPG_PASSPHRASE}" | gpg --passphrase-fd 0 --armor \
--output "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz.asc" \
--detach-sig "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz"
echo "${GPG_PASSPHRASE}" | gpg --passphrase-fd 0 --print-md MD5 \
"zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz" > \
"zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz.md5"
${SHASUM} -a 512 "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz" > \
"zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz.sha512"
mv "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz" "${WORKING_DIR}/"
mv "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz.asc" "${WORKING_DIR}/"
mv "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz.md5" "${WORKING_DIR}/"
mv "zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}.tgz.sha512" "${WORKING_DIR}/"
# clean up build dir
rm -rf "${WORKING_DIR}/zeppelin-${RELEASE_VERSION}-bin-${BIN_RELEASE_NAME}"
}
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
git_clone
make_source_package
[ZEPPELIN-1256][BUILD] Build distribution package with Spark 2.0 and Scala 2.11 ### What is this PR for? - build distribution package with Spark 2.0 and Scala 2.11 - change travis profile to use spark 2.0 instead of 2.0.0-preview by removing `-Dspark.version=2.0.0-preview` property - Change profile activation rule * current way of profile activation is not proper for supporting more than three scala version * -Pscala-2.11 activates both scala-2.10 and scala-2.11 profile without this patch ### What type of PR is it? Build ### What is the Jira issue? [ZEPPELIN-1256](https://issues.apache.org/jira/browse/ZEPPELIN-1256) ### How should this be tested? **Before** Run `mvn help:active-profiles -Pscala-2.11`: ``` Active Profiles for Project 'org.apache.zeppelin:zeppelin:pom:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-interpreter:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-zengine:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-display_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-display_2.11:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark-dependencies_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - spark-2.0 (source: org.apache.zeppelin:zeppelin-spark-dependencies_2.11:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - exclude-sparkr (source: org.apache.zeppelin:zeppelin-spark_2.11:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-markdown:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-angular:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-shell:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-livy:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-hbase:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-postgresql:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-jdbc:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-file:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-flink_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-ignite_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-kylin:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-python:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-lens:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-cassandra_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-elasticsearch:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-alluxio:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-web:war:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-server:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-server:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-distribution:pom:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-distribution:0.7.0-SNAPSHOT) - scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) ``` **After** Run `mvn help:active-profiles -Dscala-2.11`: ``` Active Profiles for Project 'org.apache.zeppelin:zeppelin:pom:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-interpreter:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-zengine:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-display_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-display_2.11:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark-dependencies_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - spark-2.0 (source: org.apache.zeppelin:zeppelin-spark-dependencies_2.11:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - exclude-sparkr (source: org.apache.zeppelin:zeppelin-spark_2.11:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-markdown:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-angular:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-shell:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-livy:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-hbase:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-postgresql:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-jdbc:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-file:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-flink_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-ignite_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-kylin:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-python:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-lens:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-cassandra_2.11:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-elasticsearch:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-alluxio:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-web:war:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-server:jar:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-server:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) Active Profiles for Project 'org.apache.zeppelin:zeppelin-distribution:pom:0.7.0-SNAPSHOT': The following profiles are active: - scala-2.11 (source: org.apache.zeppelin:zeppelin-distribution:0.7.0-SNAPSHOT) - scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT) ``` ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? yes (for scala 2.11 build) Author: Mina Lee <minalee@apache.org> Closes #1251 from minahlee/ZEPPELIN-1256 and squashes the following commits: ff034c6 [Mina Lee] change scala-2.10 and scala-2.11 profile activation rule 99d91bf [Mina Lee] Update interpreter installation for the user who use Spark version <= 1.6.2 4ca3e7f [Mina Lee] Build distribution package with Spark 2.0 and Scala 2.11
2016-08-05 02:07:24 +00:00
make_binary_release all "-Pspark-2.0 -Phadoop-2.4 -Pyarn -Ppyspark -Psparkr -Pr -Pscala-2.11"
make_binary_release netinst "-Pspark-2.0 -Phadoop-2.4 -Pyarn -Ppyspark -Psparkr -Pr -Pscala-2.11 -pl !alluxio,!angular,!cassandra,!elasticsearch,!file,!flink,!hbase,!ignite,!jdbc,!kylin,!lens,!livy,!markdown,!postgresql,!python,!shell,!bigquery"
# remove non release files and dirs
[ZEPPELIN-986] Create publish release script ### What is this PR for? This PR is to automate release publish to maven repository. We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository. Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908). Originally below modules were skipped for maven release - all interpreters(except spark) - zeppelin-display - zeppelin-server - zeppelin-distribution on the other hand this pr will skip only: - zeppelin-distribution ### What type of PR is it? Infra ### Todos - [x] Include SparkR/R interpreter in release - [x] Create common_release.sh to remove build configuration duplication - [x] Check curl networking failure ### What is the Jira issue? [ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged. Author: Mina Lee <minalee@apache.org> Closes #994 from minahlee/ZEPPELIN-986 and squashes the following commits: b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build" cd4cbcd [Mina Lee] curl failure check c0ea07c [Mina Lee] Fix wrong indentation a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build 2cced61 [Mina Lee] Add r to binary package and maven build 903bc12 [Mina Lee] Move duplicate code to common_release.sh a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact 48d338f [Mina Lee] Rollback mistakenly removed plugin aafaf42 [Mina Lee] Follow google shell style guide 30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy cd1f08c [Mina Lee] Refactor create release script e764f5f [Mina Lee] Add maven publish release script
2016-06-20 17:26:20 +00:00
rm -rf "${WORKING_DIR}/zeppelin"
rm -rf "${WORKING_DIR}/zeppelin-${RELEASE_VERSION}"
echo "Release files are created under ${WORKING_DIR}"