Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(buildkite): add pipeline definition for release QA #5425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ShadowCurse merged 2 commits into firecracker-microvm:main from Manciukic:bk-release-qa
Sep 3, 2025

Conversation

Copy link
Contributor

@Manciukic Manciukic commented Sep 2, 2025
edited
Loading

Changes

Adds a definition for release QA pipeline to also define it as code in our repository.

This also adds a test mode when VERSION=dev where "make_release" is used to generate the artifacts instead of downloading them from S3.

Reason

The release QA pipeline broke and we fixed it manually. As it wasn't defined in code, it's hard to track and audit changes to it, so we should move it to our repo.

At the same time, we were wondering if we could test this pipeline weekly. This change addresses that by enabling a new mode when "VERSION=dev" that uses devtool make_release to build the release artifacts from main and use them instead of downloading a specific release.
By running the pipeline weekly on main with that option we can be notified when make_release or the QA pipeline fail.

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkbuild --all to verify that the PR passes
    build checks on all supported architectures.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

Copy link

codecov bot commented Sep 2, 2025
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.73%. Comparing base (5dde18c) to head (ca5a0f0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@
## main #5425 +/- ##
=======================================
 Coverage 82.73% 82.73% 
=======================================
 Files 263 263 
 Lines 27455 27455 
=======================================
 Hits 22715 22715 
 Misses 4740 4740 
Flag Coverage Δ
5.10-m5n.metal 82.84% <ø> (+<0.01%) ⬆️
5.10-m6a.metal 82.09% <ø> (+<0.01%) ⬆️
5.10-m6g.metal 79.52% <ø> (ø)
5.10-m6i.metal 82.83% <ø> (+<0.01%) ⬆️
5.10-m7a.metal-48xl 82.08% <ø> (+<0.01%) ⬆️
5.10-m7g.metal 79.52% <ø> (ø)
5.10-m7i.metal-24xl 82.81% <ø> (ø)
5.10-m7i.metal-48xl 82.81% <ø> (+<0.01%) ⬆️
5.10-m8g.metal-24xl 79.52% <ø> (ø)
5.10-m8g.metal-48xl 79.52% <ø> (ø)
6.1-m5n.metal 82.87% <ø> (ø)
6.1-m6a.metal 82.13% <ø> (?)
6.1-m6g.metal 79.52% <ø> (ø)
6.1-m6i.metal 82.87% <ø> (+<0.01%) ⬆️
6.1-m7a.metal-48xl 82.12% <ø> (ø)
6.1-m7g.metal 79.52% <ø> (ø)
6.1-m7i.metal-24xl 82.88% <ø> (+<0.01%) ⬆️
6.1-m7i.metal-48xl 82.88% <ø> (ø)
6.1-m8g.metal-24xl 79.52% <ø> (ø)
6.1-m8g.metal-48xl 79.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor Author

Manciukic commented Sep 2, 2025
edited
Loading

Release QA pipeline testing in my personal pipeline:

Adds a definition for release QA pipeline to also define it as code in
our repository.
This also adds a test mode when VERSION=dev where "make_release" is used
to generate the artifacts instead of downloading them from S3.
Signed-off-by: Riccardo Mancini <mancio@amazon.com>
@Manciukic Manciukic marked this pull request as ready for review September 2, 2025 11:11
@Manciukic Manciukic added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Sep 2, 2025
@zulinx86 zulinx86 self-requested a review September 3, 2025 08:51
@ShadowCurse ShadowCurse merged commit 286aa17 into firecracker-microvm:main Sep 3, 2025
7 checks passed
@Manciukic Manciukic deleted the bk-release-qa branch September 3, 2025 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JackThomson2 JackThomson2 JackThomson2 approved these changes

@ShadowCurse ShadowCurse ShadowCurse approved these changes

@zulinx86 zulinx86 zulinx86 approved these changes

Assignees
No one assigned
Labels
Status: Awaiting review Indicates that a pull request is ready to be reviewed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /