Skip to content

CI: fix failing ci and playwright workflows #1756

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
merged 1 commit into from
Apr 30, 2025

Conversation

jackw
Copy link
Collaborator

@jackw jackw commented Apr 30, 2025

What this PR does / why we need it:

Main is currently failing due to changes made in #1755

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@jackw jackw added no-changelog Don't include in changelog and version calculations ci labels Apr 30, 2025
@jackw jackw self-assigned this Apr 30, 2025
@jackw jackw requested review from a team as code owners April 30, 2025 13:20
@jackw jackw requested review from hugohaggmark, s4kh and xnyo April 30, 2025 13:20
@jackw jackw moved this from 📬 Triage to 🔬 In review in Plugins Platform / Grafana Community Apr 30, 2025
Copy link
Contributor

github-actions bot commented Apr 30, 2025

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs.

Copy link
Contributor

Playwright test results

Image Name Version Result Report
grafana-dev 12.1.0-241102
grafana-enterprise 11.6.1
grafana-enterprise 11.3.6
grafana-enterprise 10.2.9
grafana-enterprise 9.2.20
grafana-enterprise 8.5.27
Troubleshooting

404 when clicking on View report

By default, the deploy-report-pages Action deploys reports to the gh-pages branch. However, you need to take an extra step to ensure that GitHub Pages can build and serve the site from this branch. To do so:

  1. Go to the Settings tab of your repository.
  2. In the left-hand sidebar, click on Pages.
  3. Under Source, select Deploy from a branch, then choose the gh-pages branch.

This action needs to be completed manually in order for your GitHub Pages site to be built and accessible from the gh-pages branch. Once configured, GitHub will automatically build and serve the site whenever new reports are deployed.

@jackw jackw merged commit 43b96dc into main Apr 30, 2025
27 checks passed
@jackw jackw deleted the jackw/workflow-aftermath-part1 branch April 30, 2025 13:43
@github-project-automation github-project-automation bot moved this from 🔬 In review to 🚀 Shipped in Plugins Platform / Grafana Community Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci no-changelog Don't include in changelog and version calculations
Projects
Development

Successfully merging this pull request may close these issues.

3 participants