2e7f5ccb7c
Build actions can be cached, so they can't be used for Maven interactions. Instead, generate a script that calls buck and then runs the upload process. This obviates tools/maven/api.py. The script tools/maven/api.sh runs all deployment steps combined (generate script, generate artifacts, upload to maven.) Tested: Ran "python tools/maven/api.py -n deploy" before and "buck build //tools/maven:gen_api_deploy" afterwards. The old command line and generated script differ as expected: * paths in the script are absolute, because Buck expands $(location) to absolute paths. * the ordering of arguments differs, because Python dict iteration was random beforehand. * "-o" missing afterward, as expected. The same check was performed for gen_api_install. Change-Id: Ia246000f8b59e881c53265751e2ebcfe8ec7d433
70 lines
1.5 KiB
Bash
Executable File
70 lines
1.5 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# Copyright (C) 2015 The Android Open Source Project
|
|
#
|
|
# Licensed 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.
|
|
|
|
if [[ "$#" == "0" ]] ; then
|
|
cat <<EOF
|
|
Usage: run "$0 COMMAND" from the top of your workspace, where
|
|
COMMAND is one of
|
|
|
|
install
|
|
deploy
|
|
war_install
|
|
war_deploy
|
|
|
|
Set VERBOSE in the environment to get more information.
|
|
|
|
EOF
|
|
|
|
exit 1
|
|
fi
|
|
|
|
set -o errexit
|
|
set -o nounset
|
|
|
|
|
|
case "$1" in
|
|
install)
|
|
command="api_install"
|
|
;;
|
|
deploy)
|
|
command="api_deploy"
|
|
;;
|
|
war_install)
|
|
command="war_install"
|
|
;;
|
|
war_deploy)
|
|
command="war_deploy"
|
|
;;
|
|
*)
|
|
echo "unknown command $1"
|
|
exit 1
|
|
;;
|
|
esac
|
|
|
|
if [[ "${VERBOSE:-x}" != "x" ]]; then
|
|
set -o xtrace
|
|
fi
|
|
|
|
buck build //tools/maven:gen_${command} || \
|
|
{ echo "buck failed to build gen_${command}. Use VERBOSE=1 for more info" ; exit 1 ; }
|
|
|
|
script="./buck-out/gen/tools/maven/gen_${command}/${command}.sh"
|
|
|
|
# The PEX wrapper does some funky exit handling, so even if the script
|
|
# does "exit(0)", the return status is '1'. So we can't tell if the
|
|
# following invocation was successful.
|
|
${script}
|