Built-in rules: add a tree rule

... so that for every construct supported in rules there is
an analogous one as a built-in rule to allow ad-hoc constructions
without having to write a rule (even though writing a rule is
recommended for everything occuring more than once):
- the "generic" rule allows an ad-hoc ACTION,
- the "file_gen" rule allows an ad-hoc BLOB,
- the "tree" rule allows an an ad-hoc TREE, and
- the "configure" rule allows an ad-hoc configuration transition.

1 files changed, 42 insertions, 0 deletions

diff --git a/test/end-to-end/built-in-rules/tree.sh b/test/end-to-end/built-in-rules/tree.sh
new file mode 100755
index 00000000..68699eec
--- /dev/null
+++ b/test/end-to-end/built-in-rules/tree.sh
@@ -0,0 +1,42 @@
+#!/bin/bash
+# Copyright 2022 Huawei Cloud Computing Technology Co., Ltd.
+#
+# 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.
+
+
+set -e
+
+touch ROOT
+touch a.txt
+
+cat <<'EOF' > TARGETS
+{ "": {"type": "tree", "name": "where/to/stage", "deps": ["content"]}
+, "content":
+  {"type": "install", "files": {"a": "a.txt", "b": "a.txt", "c/d": "a.txt"}}
+}
+EOF
+
+bin/tool-under-test analyse \
+    --dump-trees trees.json --dump-artifacts-to-build artifacts.json 2>&1
+echo
+echo Artifacts
+cat artifacts.json
+[ $(jq 'keys == ["where/to/stage"]' artifacts.json) = "true" ]
+tree_id=$(jq '."where/to/stage"."data"."id"' artifacts.json)
+
+echo
+cat trees.json
+[ $(jq 'keys == ['$tree_id']' trees.json) = "true" ]
+[ $(jq '.'$tree_id' | keys == ["a", "b", "c/d"]' trees.json) = "true" ]
+
+echo OK