Commit Graph

9 Commits

Author SHA1 Message Date
pezkuwichain 36b724ec4f fix: add git safe.directory for containerized CI with persistent cache
When using persistent cargo cache mounted from host directory, the container
user differs from the directory owner, causing git "dubious ownership" error.
This fix adds `git config --global --add safe.directory '*'` before cargo
commands in containerized jobs.
2026-01-28 04:37:43 +03:00
pezkuwichain 785eba8322 feat: add persistent cargo target cache for self-hosted runners
Mount /cache/cargo-target/pezkuwi-sdk on VPS runners to reuse
compiled artifacts between workflow runs. This significantly
speeds up subsequent builds by avoiding full recompilation.

Updated workflows:
- checks.yml (cargo-clippy, check-try-runtime)
- docs.yml (test-doc, build-rustdoc)
- tests-linux-stable.yml (all test jobs)

Also removed Swatinem/rust-cache where persistent cache is used
since it's now redundant.
2026-01-28 03:12:27 +03:00
pezkuwichain 268b640371 fix: CI failures - tests-linux-stable and build-publish-images
tests-linux-stable.yml:
- Add SKIP_WASM_BUILD=1 to test-linux-stable-int, test-linux-stable-runtime-benchmarks,
  test-linux-stable, and test-linux-stable-no-try-runtime jobs
- Remove wasm32v1-none target from test-linux-stable-runtime-benchmarks
  (not needed with SKIP_WASM_BUILD)
- Tracking: https://github.com/pezkuwichain/pezkuwi-sdk/issues/358

build-publish-images.yml:
- Add git safe.directory configuration to build-linux-stable and
  build-linux-bizinikiwi jobs
- Fixes "fatal: detected dubious ownership in repository" error that occurs
  when build-only-wasm.sh script runs git rev-parse
2026-01-27 22:13:40 +03:00
pezkuwichain b7a074aeaf perf: optimize CI workflows with caching and reduced parallelism
Changes:
- Add Rust caching (Swatinem/rust-cache) to all heavy build jobs
- Reduce cargo-check-each-crate from 7 to 4 parallel jobs
- Reduce tests-linux-stable matrix from 6 to 3 jobs
- Set CARGO_INCREMENTAL=0 for consistent caching
- Reduce timeouts from 60 to 45 minutes (cache makes builds faster)
- Remove redundant disk cleanup steps (cache handles this)

Expected improvements:
- 50-80% faster builds after cache is populated
- Lower VPS load (fewer parallel jobs)
- More consistent build times

Affected workflows:
- checks.yml (cargo-clippy, check-try-runtime)
- tests.yml (quick-benchmarks, cargo-check-all-benches)
- tests-misc.yml (test-pezframe-ui, cargo-check-each-crate)
- tests-linux-stable.yml (test-linux-stable)
- docs.yml (test-doc, build-rustdoc)
2026-01-26 23:44:30 +03:00
pezkuwichain 849e51cc57 fix: add wasm32v1-none target to CI workflows
Add rustup target add wasm32v1-none step to:
- tests-misc.yml: test-pezframe-examples-compile-to-wasm, cargo-check-benches, check-metadata-hash, cargo-check-each-crate
- tests-linux-stable.yml: test-linux-stable-int, test-linux-stable-runtime-benchmarks, test-linux-stable, test-linux-stable-no-try-runtime
- build-misc.yml: build-runtimes-polkavm

This fixes WASM build failures in container jobs where the wasm32v1-none target is not available by default.
2026-01-26 15:42:21 +03:00
pezkuwichain cf23fed9c5 fix(ci): remove wasm32v1-none target to fix serde_core compilation (#346)
* docs: update workflow plan with completed CI fixes

* fix(ci): remove wasm32v1-none target installation to fix serde_core compilation

This removes the explicit `rustup target add wasm32v1-none` step from CI
workflows. When wasm32v1-none is installed, the wasm-builder uses it instead
of wasm32-unknown-unknown, which causes serde_core 1.0.228 to fail compilation
with "relaxing a default bound only does something for ?Sized" errors.

By not installing wasm32v1-none, the wasm-builder automatically falls back to
wasm32-unknown-unknown which compiles successfully.

This aligns with Polkadot SDK's CI configuration which also does not explicitly
install wasm32v1-none.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-27 09:41:10 +03:00
pezkuwichain c593011caa ci: add wasm32v1-none target for Rust 1.84+ WASM builds
Fixes getrandom/duplicate lang item errors in WASM builds by ensuring
the wasm32v1-none target is installed before running cargo builds that
involve WASM compilation. This is required for Rust 1.84+ where the
bizinikiwi-wasm-builder uses wasm32v1-none instead of wasm32-unknown-unknown.

Affected workflows:
- tests.yml (quick-benchmarks)
- tests-linux-stable.yml (test-linux-stable-int, test-linux-stable-runtime-benchmarks)
- tests-misc.yml (test-deterministic-wasm)
- build-publish-images.yml (build-linux-stable, build-linux-bizinikiwi)
- check-pezframe-omni-bencher.yml (quick-benchmarks-omni, run-pezframe-omni-bencher)
2025-12-26 14:12:02 +03:00
pezkuwichain 826ee7cdd8 fix: correct pezstaging-node-cli package name in CI workflows
The package was renamed from pez-staging-node-cli to pezstaging-node-cli
during the rebrand but the workflow files still referenced the old name.

Files updated:
- build-publish-images.yml
- release-20_build-rc.yml
- release-reusable-rc-build.yml
- tests-linux-stable.yml
- tests.yml

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-24 07:23:48 +03:00
pezkuwichain 2093647fea feat: Add rebrand CI/CD workflows to main branch
- Add 72 rebrand workflow files (polkadot→pezkuwi, substrate→bizinikiwi, cumulus→pezcumulus)
- Add GitHub actions, issue templates, and configs
- Removed unnecessary workflows (fork-sync, gitspiegel, upstream-tracker, sync-templates, backport)
- Renamed zombienet test files to match new naming convention
2025-12-19 22:51:57 +03:00