I invite you to share thoughts about possible CI workflows, which would run tests on community supplied unofficial plugins. Some communities depend heavily on plugins, without established maintenance: [image] Unofficial plugins management during updates But we are afraid that during Discourse …

This may be useful: [image] Setup Continuous Integration using GitHub Actions Developer Guides mag Overview To build a robust extension for Discourse, it can be wise to include Continuous Integration (CI) into your plugin or theme-component. This will help to …

Yes, and to add to what @angus has shared, you can find our daily compatibility dashboard here: https://coop.pavilion.tech/plugins?branch=tests-passed Which displays status of checks for compatibility of Pavilion Plugins (and sometimes others) against tests-passed and stable. This is updated ever…

[image] Robert: This is updated every day, automatically. Impressive. Could you point to the code, which implements this?

It’s an architecture as per @angus ’ diagram, with multiple repos involved, but this is the status server: https://github.com/paviliondev/discourse-plugin-manager It’s also an approach: Never implement a fix without checking for a test, and if a suitable test doesn’t exist, add one. Preferably de…

All official plugins have specs that you can use as examples. The discourse-plugin-Skelton plugin includes github Actions to run tests at every commit, and I think, daily.

Do I understand correctly? [image] Thomas Kalka: to build some machinery, which aides site maintainers to run tests in a staging environment a) This is available via GitHub actions: plugins with proper specs / tests using GitHub actions will have a badge on GitHub, if all tests pass and the…

[image] Thomas Kalka: b) Except discourse official plugins and pavilion plugins, there exist no automatic overview for administrators, if used plugins will work in the version intended for update? We originally set out to and provided an unbranded version of our Plugin dashboard where 3rd par…

How could a CI workflow for unofficial plugins be implemented?

Development

angus (Angus McLeod) July 16, 2023, 8:36am 3

In addition to CI with backend and frontend tests, which most Pavilion plugins have now, we have a plugin manager system of which CI is one part. This is how it works

Topic		Replies	Views
Setup Continuous Integration using GitHub Actions Developer Guides how-to , code	8	1740	March 3, 2025
Smoke-testing plugins during upgrade process Feature	22	2902	May 15, 2025
Give Plugin versions for minimum and maximum discourse version Feature	5	276	September 5, 2025
Unofficial plugins management during updates Self-hosting	5	1278	October 22, 2020
Suggestions for better plugin maintenance Development	15	3158	November 7, 2016

How could a CI workflow for unofficial plugins be implemented?

Related topics