Skip to content

Conversation

@xiangjinwu
Copy link
Contributor

@xiangjinwu xiangjinwu commented Oct 10, 2025

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Prior context: #18124

Checklist

  • I have written necessary rustdoc comments.
  • I have added necessary unit tests and integration tests.
  • I have added test labels as necessary.
  • I have added fuzzing tests or opened an issue to track them.
  • My PR contains breaking changes.
  • My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
  • I have checked the Release Timeline and Currently Supported Versions to determine which release branches I need to cherry-pick this PR into.

Documentation

  • My PR needs documentation updates.
Release note

@github-actions github-actions bot added the A-ci Area: CI workflow and scripts, etc. label Oct 10, 2025
steps:
- label: "docker-build-push: aarch64"
if: build.env("SKIP_TARGET_AARCH64") != "true"
command: "CARGO_PROFILE=patch-production ci/scripts/docker.sh"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CARGO_PROFILE=patch-production is not retained in this PR. Shall we:

  • expose it as one more additional checkbox / choice
  • assume it when skip_target_amd64 is checked
  • drop it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

assume it when skip_target_amd64 is checked

This. It should speed up the production build, since it skips lto.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed the option from skip_target_amd64 to fast_build, and preserved the CARGO_PROFILE.

@hzxa21 hzxa21 requested a review from kwannoel October 21, 2025 09:52
@xiangjinwu xiangjinwu marked this pull request as ready for review October 24, 2025 03:11
@xiangjinwu xiangjinwu added this pull request to the merge queue Oct 24, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 24, 2025
@xiangjinwu xiangjinwu added this pull request to the merge queue Oct 24, 2025
Merged via the queue into main with commit 940c883 Oct 24, 2025
34 of 35 checks passed
@xiangjinwu xiangjinwu deleted the ci-docker-arm-dry branch October 24, 2025 06:18
commit: HEAD
message: ':github: Triggering Docker build with image tag: ${{ env.IMAGE_TAG }}'
build_env_vars: '{ "IMAGE_TAG": "${{ env.IMAGE_TAG }}", "PUSH_DOCKERHUB": "${{ env.PUSH_DOCKERHUB }}" }'
build_env_vars: '{ "IMAGE_TAG": "${{ env.IMAGE_TAG }}", "PUSH_DOCKERHUB": "${{ env.PUSH_DOCKERHUB }}" }'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updating this line to pass SKIP_TARGET_AMD64 and CARGO_PROFILE to buildkite in a followup PR. I was only testing the shell script above by disabling the actual buildkite part 🤦

After that I will cherry-pick this together with it to release branches.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions
Copy link
Contributor

✅ Cherry-pick PRs (or issues if encountered conflicts) have been created successfully to all target branches.

github-merge-queue bot pushed a commit that referenced this pull request Oct 24, 2025
xiangjinwu added a commit that referenced this pull request Oct 24, 2025
lmatz pushed a commit that referenced this pull request Oct 29, 2025
github-merge-queue bot pushed a commit that referenced this pull request Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-ci Area: CI workflow and scripts, etc. need-cherry-pick-since-release-2.5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants