Deploy tool: cache build artifacts in Vercel Blob by commit hash

[DimitrijeDragasevic]

Title

Deploy tool: cache build artifacts in Vercel Blob by commit hash

Summary

• Introduces a per-commit artifact cache on Vercel Blob to speed up deployments.
• Reuses prebuilt WASM files and version_map.json if they already exist for the current commit.
• Falls back to local verify + build, deploys, then uploads artifacts for future runs.

Motivation

• Avoid rebuilding the same commit across different chains/environments.
• Ensure a single, consistent build output is reused everywhere for a given commit.

What changed

• Added Vercel Blob helpers:
  • list by prefix <commit_hash>/
  • download all matching objects into local artifacts/
  • upload .wasm and version_map.json to <commit_hash>/<filename>
• Updated deploy flow:
  • Check for <commit_hash>/ “folder” (prefix) on Vercel.
  • If present: download to artifacts/ and deploy (no build).
  • If absent: verify + build → deploy → upload artifacts (post-success only).

How it works

• Compute current commit: git rev-parse HEAD (trimmed).
• Probe Vercel Blob with prefix <commit_hash>/.
• Cache hit:
  • Download all blobs to artifacts/ (filenames preserved).
  • Deploy via ADO DB.
• Cache miss:
  • validate::run() → build::run().
  • Deploy via ADO DB.
  • Upload all .wasm + version_map.json to <commit_hash>/....

Environment / Secrets

• Requires VERCEL_BLOB_READ_WRITE_TOKEN.
• Existing vars unchanged: DEPLOYMENT_CHAIN, DEPLOYMENT_KERNEL_ADDRESS, DEPLOY_OS, DEPLOY_CONTRACTS.

Testing

• Cache miss:
  • Make a new commit (no blobs on Vercel for this hash).
  • Run deploy.
  • Expect: verify + build → deploy → upload to <commit_hash>/....
• Cache hit:
  • Run deploy again on the same commit.
  • Expect: logs “Found prebuilt artifacts…”, download to artifacts/, deploy (no build).

Checklist

• Builds and lints pass
• Cache-hit path skips build
• Cache-miss path uploads after successful deploy
• version_map.json aligned

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dimi/new_deployment_process

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[joemonem]

Missing a version bump for andromeda-deploy

[joemonem]

Also linking the workflow runs related to the testing in this PR could be useful for future reference

[SlayerAnsh]

version.json file missing from uploaded artifacts. We will need that to map version with wasm files