You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -62,7 +62,7 @@ Build ClickHouse in `build` or `build_debug`, `build_asan`, `build_tsan`, `build
62
62
63
63
**Step 2b: Start the ninja build:**
64
64
```bash
65
-
cd build/${buildType}&& ninja [target] > [log file path] 2>&1
65
+
cd build && ninja [target] > [log file path] 2>&1
66
66
```
67
67
68
68
When using ninja you can pass `-k{num}` to continue building even if some targets fail. For example, `-k20` will keep going after 20 failures. Adjust this number based on your needs.
@@ -90,7 +90,7 @@ Build ClickHouse in `build` or `build_debug`, `build_asan`, `build_tsan`, `build
@@ -161,7 +161,7 @@ Build ClickHouse in `build` or `build_debug`, `build_asan`, `build_tsan`, `build
161
161
- Run: pkill -f \"clickhouse[- ]server\"
162
162
- Wait 1 second: sleep 1
163
163
- Verify stopped: pgrep -f \"clickhouse[- ]server\" should return nothing
164
-
- Report: \"Server stopped. To start the new version, run: ./build/${buildType}/programs/clickhouse server --config-file ./programs/server/config.xml\"
164
+
- Report: \"Server stopped. To start the new version, run: ./build/programs/clickhouse server --config-file ./programs/server/config.xml\"
165
165
- If user chooses \"No, keep it running\":
166
166
- Report: \"Server remains running with the old binary. You'll need to manually restart it to use the new build.\"
167
167
@@ -180,7 +180,7 @@ Build ClickHouse in `build` or `build_debug`, `build_asan`, `build_tsan`, `build
180
180
181
181
**For successful builds:**
182
182
- Confirm the build completed successfully
183
-
- Report the binary location: `build/${buildType}/programs/[target]`
183
+
- Report the binary location: `build/programs/[target]`
184
184
- Report the server status outcome from step 5
185
185
186
186
**For failed builds:**
@@ -207,11 +207,11 @@ Build ClickHouse in `build` or `build_debug`, `build_asan`, `build_tsan`, `build
207
207
208
208
- Always run from repository root
209
209
- **NEVER** create build directories or run `cmake` - the build directory must already be configured
- This skill only runs incremental builds with `ninja`
213
213
- To configure a new build directory, the user must manually run CMake first
214
-
- For a clean build, the user should remove `build/${buildType}` and reconfigure manually
214
+
- For a clean build, the user should remove `build` and reconfigure manually
215
215
- **MANDATORY:** After successful builds, this skill MUST check for running ClickHouse servers and ask the user if they want to stop them to use the new build
216
216
- **MANDATORY:** ALL build output (success or failure) MUST be analyzed by a Task agent with `subagent_type=general-purpose`
217
217
- **MANDATORY:** ALWAYS provide a final summary to the user at the end of the skill execution (step 6)
0 commit comments