Commit 955800d
committed
ci(shorebird): add shell steps for engine_stamp.json + aot-tools.dill
Both files are listed as shard artifacts in the new sharded build but
neither is actually produced — they were built outside the gn+ninja
graph in the legacy shell scripts (mac_build.sh / linux_build.sh) and
the sharded pipeline only knew about gn_ninja and rust step types.
shorebirdtech/_build_engine#209 adds a `shell` step type to
shard_runner. This PR uses it:
- mac-x64: new shell step runs `flutter/bin/et stamp` (writes
out/engine_stamp.json) and copies the result into
out/mac_release/engine_stamp.json so it ends up in the shard's
tarball. The matching artifact src updates from "engine_stamp.json"
to "mac_release/engine_stamp.json".
- linux/host: new shell step runs the host-built dart against
flutter/third_party/dart/pkg/aot_tools to produce
out/host_release/aot_tools/aot-tools.dill, matching what
linux_build.sh:78-90 does. The existing artifact src
("host_release/aot_tools/aot-tools.dill") is already correct.
After this lands and an engine bump produces a SHA carrying it,
finalize will upload these two missing files and the sharded build's
prod artifact set should match the legacy build's exactly (modulo
iOS XCFramework signing).1 parent 3fa79e8 commit 955800d
2 files changed
Lines changed: 9 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
91 | 91 | | |
92 | 92 | | |
93 | 93 | | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
94 | 98 | | |
95 | 99 | | |
96 | 100 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
157 | 157 | | |
158 | 158 | | |
159 | 159 | | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
160 | 164 | | |
161 | 165 | | |
162 | 166 | | |
163 | 167 | | |
164 | 168 | | |
165 | | - | |
| 169 | + | |
166 | 170 | | |
167 | 171 | | |
168 | 172 | | |
0 commit comments