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: [Bild] Unofficial plugins management during updates But we are afraid that during Discourse u…

This may be useful: [Bild] 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 d…

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 [image]

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…

[Bild] 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? [Bild] 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 …

[Bild] 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 part…

Wie könnte ein CI-Workflow für inoffizielle Plugins implementiert werden?

Entwickler

angus (Angus McLeod) 16. Juli 2023 um 08:36 3

Zusätzlich zu CI mit Backend- und Frontend-Tests, was die meisten Pavilion-Plugins jetzt haben, verfügen wir über ein Plugin-Manager-System, dessen Teil CI ist. So funktioniert es

Thema		Antworten	Aufrufe
Setup Continuous Integration using GitHub Actions Developer Guides how-to , code	8	1739	3. März 2025
Smoke-testing plugins during upgrade process Feature	22	2901	15. Mai 2025
Give Plugin versions for minimum and maximum discourse version Feature	5	276	5. September 2025
Unofficial plugins management during updates Self-hosting	5	1278	22. Oktober 2020
Suggestions for better plugin maintenance Development	15	3158	7. November 2016

Wie könnte ein CI-Workflow für inoffizielle Plugins implementiert werden?

Verwandte Themen