forked from protocolbuffers/protobuf
-
Notifications
You must be signed in to change notification settings - Fork 0
/
regenerate_stale_files.sh
executable file
·41 lines (32 loc) · 1.3 KB
/
regenerate_stale_files.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
#!/bin/bash
# This script runs the staleness tests and uses them to update any stale
# generated files.
set -ex
echo "::group::Regenerate stale files"
# Cd to the repo root.
cd $(dirname -- "$0")
readonly BazelBin="${BAZEL:-bazel} ${BAZEL_STARTUP_FLAGS}"
STALENESS_TESTS=(
"java/core:generated_java_defaults_staleness_test"
"upb/reflection:bootstrap_upb_defaults_staleness_test"
"src:cmake_lists_staleness_test"
"src/google/protobuf:well_known_types_staleness_test"
"objectivec:well_known_types_staleness_test"
"php:test_amalgamation_staleness"
"php:proto_staleness_test"
"ruby/ext/google/protobuf_c:test_amalgamation_staleness"
"upb/cmake:test_generated_files"
"upb/reflection:descriptor_upb_proto_staleness_test"
"upb_generator:plugin_upb_proto_staleness_test"
)
# Run and fix all staleness tests.
for test in ${STALENESS_TESTS[@]}; do
${BazelBin} test $test "$@" || ./bazel-bin/${test%%:*}/${test#*:} --fix
done
# Generate C# code.
# This doesn't currently have Bazel staleness tests, but there's an existing
# shell script that generates everything required. The output files are stable,
# so just regenerating in place should be harmless.
${BazelBin} build src/google/protobuf/compiler:protoc "$@"
(export PROTOC=$PWD/bazel-bin/protoc && cd csharp && ./generate_protos.sh)
echo "::endgroup::"