Skip to content

ci(dashboard): pull lime-packages test reports from another side - #82

Merged
ccasanueva7 merged 1 commit into
developfrom
feat/collect-lime-results
May 23, 2026
Merged

ci(dashboard): pull lime-packages test reports from another side#82
ccasanueva7 merged 1 commit into
developfrom
feat/collect-lime-results

Conversation

@ccasanueva7

Copy link
Copy Markdown
Collaborator

Summary

  • New scheduled workflow collect-lime-results.yml that downloads report.xml artifacts from recent fcefyn-testbed/lime-packages CI runs and commits them under docs/ci-results/results/.
  • Runs every 6 h plus manual workflow_dispatch.
  • Lets the dashboard render per-job test details and stops the "Report ↗" links from 404'ing.

Why

The original plan (lime-packages pushing results into this repo) requires merging a PR to lime-packages' master, which the LibreMesh community has not accepted. This is the inverse direction: this repo pulls from lime-packages instead. No changes are required in lime-packages.

Setup required after merge

  • Add a repo secret named LIME_PACKAGES_TOKEN to fcefyn_testbed_utils (fine-grained PAT scoped to fcefyn-testbed/lime-packages, Actions: Read).
  • Trigger the workflow manually once from the Actions tab to backfill recent runs; afterwards the cron keeps it warm.

Test plan

  • Add LIME_PACKAGES_TOKEN secret
  • Run "Collect lime-packages test results" manually from Actions
  • Verify a commit appears on develop adding files under docs/ci-results/results/
  • Open the dashboard and confirm "Report " links open the JUnit XML instead of 404

Adds a scheduled workflow that uses LIME_PACKAGES_TOKEN to download
JUnit report.xml artifacts from recent fcefyn-testbed/lime-packages CI
runs and commits them under docs/ci-results/results/. Fixes the 404 on
the dashboard "Report ↗" links without requiring any change in
lime-packages (the PR to publish from there will not be merged
upstream).
@ccasanueva7
ccasanueva7 merged commit 08dd153 into develop May 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant