-
Notifications
You must be signed in to change notification settings - Fork 131
Closed
Labels
InfrastructureIssues for the overall performance plugin infrastructureIssues for the overall performance plugin infrastructure[Plugin] Performance LabIssue relates to work in the Performance Lab Plugin onlyIssue relates to work in the Performance Lab Plugin only[Type] EnhancementA suggestion for improvement of an existing featureA suggestion for improvement of an existing feature
Milestone
Description
This issue is part 2/2 for setting up the new infrastructure for developing standalone plugins.
Requirements
This work should be implemented against a new feature/modules-to-plugins
feature branch.
After #934 has been completed:
- The
php-test-standalone-plugins.yml
anddeploy-standalone-plugins.yml
workflows should be enhanced to also cover plugins found in theplugins
directory (additionally to plugins in themodules
directory, which need to be built first). - Some key differences to look out for:
- Plugins in the
plugins
folder can be assumed to truly be plugins (not modules). So they don't require a build process (at least not for now). - Modules still need to be built, the same way they are now.
- In other words, the ready-to-deploy versions of modules continue to live in a folder within
build
, while plugins can be deployed directly from their folder withinplugins
.
- Plugins in the
- Both workflows should only act for plugins that are part of
plugins.json
. - The
npm run test-plugins
command will likely need to be expanded to also cover plugins in theplugins
folder (but only those that are inplugins.json
).
Metadata
Metadata
Assignees
Labels
InfrastructureIssues for the overall performance plugin infrastructureIssues for the overall performance plugin infrastructure[Plugin] Performance LabIssue relates to work in the Performance Lab Plugin onlyIssue relates to work in the Performance Lab Plugin only[Type] EnhancementA suggestion for improvement of an existing featureA suggestion for improvement of an existing feature