e6c7e629c6
Provide BazelBuild to stub out the Bazel build.
Tested:
Production use case:
1.) bazel build polygerrit && \
$(bazel info output_base)/external/local_jdk/bin/java \
-jar bazel-bin/polygerrit.war daemon -d ../test_site \
--console-log --show-stack-trace
Development mode use cases:
2.) bazel build polygerrit \
//polygerrit-ui:polygerrit_components.bower_components.zip &&
$(bazel info output_base)/external/local_jdk/bin/java \
-jar bazel-bin/polygerrit.war daemon \
--polygerrit-dev -d ../gerrit_testsite --console-log --show-stack-trace
checked that updates under polygerrit-ui/app/index.html are served
live.
3.) Run tools/eclipse/project.py, started gwt_daemon launcher,
verified that it worked.
4.) Run tools/eclipse/project.py, started gerit_gwt_debug launcher,
verified that GWT SDM worked.
Change-Id: I9d105e00e953b63c78306e9e37d5152673627727
23 lines
611 B
Bash
Executable File
23 lines
611 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# This script will be run by bazel when the build process starts to
|
|
# generate key-value information that represents the status of the
|
|
# workspace. The output should be like
|
|
#
|
|
# KEY1 VALUE1
|
|
# KEY2 VALUE2
|
|
#
|
|
# If the script exits with non-zero code, it's considered as a failure
|
|
# and the output will be discarded.
|
|
|
|
function rev() {
|
|
cd $1; git describe --always --match "v[0-9].*" --dirty
|
|
}
|
|
|
|
echo STABLE_BUILD_GERRIT_LABEL $(rev .)
|
|
for p in plugins/* ; do
|
|
test -d "$p" || continue
|
|
echo STABLE_BUILD_$(echo $(basename $p)_LABEL|tr [a-z] [A-Z]) $(rev $p)
|
|
done
|
|
echo "STABLE_WORKSPACE_ROOT ${PWD}"
|