Add S3 upload for test results and boot logs in daily CI #197
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: aparcar <16000931+aparcar@users.noreply.github.com>
Co-authored-by: aparcar <16000931+aparcar@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Extend daily CI to upload test results and boot logs to S3
Add S3 upload for test results and boot logs in daily CI
Oct 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Daily CI now uploads JUnit XML test reports and labgrid console logs to S3 for long-term archival beyond GitHub Actions retention limits.
Changes
.github/workflows/daily.yml: Added S3 upload steps totest-realandtest-qemujobsreport.xmlandconsole_*.logfiles after each test runsecrets.S3_BUCKET != ''- workflow continues normally if S3 not configuredalways()to capture logs even on test failuress3://{bucket}/daily/{YYYY-MM-DD}/{run_id}/{device}-{version}/docs/S3_CONFIGURATION.md: Configuration guide covering required secrets, bucket structure, IAM permissions, and troubleshootingREADME.md: Added CI section linking to S3 documentationRequired Secrets (Optional)
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_REGIONS3_BUCKETCompatible with any S3-compatible service (AWS S3, MinIO, DigitalOcean Spaces, etc.).
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.