Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Done
Priority: Major
Fix Version/s: 23.0.0.Beta3, 23.0.0.Final
Affects Version/s: None
Component/s: Build System, Test Suite
Labels:
None

Git Pull Request:
https://github.com/wildfly/wildfly-core/pull/5777

Step two of the WFCORE-6611 'epic'.

Having a channel available as part of the build provides basic infrastructure for channel testing.

The channel artifact is not to be deployed to any external repository. The goal of this JIRA is to facilitate testing. However, when doing this thought should be given to what a deployed artifact would look like, e.g. its GAV and any other controllable content. Basically at some point we are probably going to want to deploy this artifact, so this should be a step toward that.

is cloned by

WFLY-18791 Create channel and manifest artifacts for the three feature packs

Closed

is depended on by

WFCORE-6616 Add per PR or nightly test jobs to test channel based provisioning

Open

WFCORE-6560 Log installation provisioning information at boot

Resolved

WFCORE-6615 Dynamic configuration of channels to use when testing

Resolved

is incorporated by

WFCORE-6611 Introduce channel based provisioning into the testsuite

Open

Assignee:: Brian Stansberry

Reporter:: Brian Stansberry

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2023/11/16 5:37 PM

Updated:: 2024/01/25 4:52 PM

Resolved:: 2023/12/01 10:34 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates