-
Epic
-
Resolution: Duplicate
-
Critical
-
None
-
None
-
None
-
Automate the process of building and pushing plugins to the registry.
-
False
-
-
False
-
To Do
-
RHIDP-2534 - Plugin Marketplace
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
-
EPIC Goal
Automate the process of building and pushing plugins to the registry.
Background/Feature Origin
- Manual building and pushing can be error-prone.
- Automation ensures consistency and reliability.
Why is this important?
- Increases efficiency and reduces human error.
- Ensures that the latest plugin versions are always available in the registry.
User Scenarios
- As a developer, I want a GitHub action to build and push plugins automatically on merge.
- As a developer, I want to use Tekton tasks/pipelines for building and pushing plugins.
Dependencies (internal and external)
- Dependencies on CI/CD tools like GitHub Actions and Tekton.
Acceptance Criteria
- GH action is available for building and pushing plugins on merge.
- Tekton task/pipeline is available for building and pushing plugins.
Release Enablement/Demo - Provide necessary release enablement details and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>
- depends on
-
-
- Closed
-
- duplicates
-
RHIDP-3964 Dynamic Plugins release and test automation
-
- Backlog
-
- is depended on by
-
-
- New
-
