chore: integrate into zuul

[kp2pml30]

Depends-on: https://github.com/genlayerlabs/zuul-jobs/pull/15

Summary by CodeRabbit

• New Features
  • Build process now accepts a command-line option to set compression level (0–9). A sensible default of 9 remains when unspecified. Inputs are validated with a clear error for invalid values, and the chosen level is applied to the final compression step so you can balance artifact size versus build speed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e4499f8 and 12baaa3.

📒 Files selected for processing (1)

• support/ci/pipelines/build.sh

✅ Files skipped from review due to trivial changes (1)

• support/ci/pipelines/build.sh

---

📝 Walkthrough

Walkthrough

The build script adds a COMPRESSION_LEVEL variable (default 9), new CLI options --compression-level <value> and --compression-level=<value>, validates a single digit [0-9], and uses the value for xz compression as -$COMPRESSION_LEVEL instead of the hardcoded -9.

Changes

Cohort / File(s)	Summary
Build Script Compression Configuration support/ci/pipelines/build.sh	Added COMPRESSION_LEVEL variable (default 9); implemented parsing for --compression-level <value> and --compression-level=<value>; validated input as a single digit [0-9]; replaced hardcoded xz -9 with -$COMPRESSION_LEVEL.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I’m a rabbit in the build tree, quick and spry,
I nibble flags and crunch bytes as they fly,
Now compression’s chosen, zero through nine,
Speed or smallness, pick the design,
Hoppity-hop—your artifacts shine! 🐇✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title 'chore: integrate into zuul' is vague and generic. While it references 'zuul', the actual changeset adds a compression level feature to a build script, which is unrelated to zuul integration.	Update the title to accurately reflect the primary change, e.g., 'feat: add configurable compression level to build script' or similar.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/zuul

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

support/ci/pipelines/build.sh (1)

44-48: ⚠️ Potential issue | 🟡 Minor

Help text is missing the new --compression-level option.

Users won't discover the new option when running --help.

📝 Proposed fix

 		-h|--help)
 			echo "Usage: $0 [--target TARGET] [--executor-version VERSION]"
 			echo "  --target TARGET              Specify the target platform (default: universal)"
 			echo "  --executor-version VERSION   Specify the executor version"
+			echo "  --compression-level LEVEL    Specify xz compression level 0-9 (default: 9)"
 			exit 0
 			;;

🧹 Nitpick comments (1)

support/ci/pipelines/build.sh (1)

68-73: Inconsistent indentation and awkward control flow.

The validation block mixes spaces (lines 69-70) with tabs (lines 71-72), and the if true; else error pattern can be simplified by negating the condition.

♻️ Proposed simplification

-if [[ "$COMPRESSION_LEVEL" == [0-9] ]]; then
-    true
-else
-    echo "Error: --compression-level must be an integer between 0 and 9" >&2
+if [[ ! "$COMPRESSION_LEVEL" == [0-9] ]]; then
+	echo "Error: --compression-level must be an integer between 0 and 9" >&2
 	exit 1
 fi

[kp2pml30]

recheck