-
Notifications
You must be signed in to change notification settings - Fork 53
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
Build: run plugin examples tests every hour #89
Comments
or maybe even better. Run it based on a push to master event in grafana/grafana |
I think the second option of a push to master of grafana/grafana whenever files change in packages/**/ would be more advantageous and is relatively easy to do in drone. 👍 |
@jackw how often do we run currently? I imagine we want to discuss this in relation to the new e2e tests running in grafana and as part of the broader topic on the purpose of these examples |
They run ones every 24h and when someone push something new to main. |
To catch issues introduced in Grafana that might affect plugins we should run the plugin examples tests every hour.
The text was updated successfully, but these errors were encountered: