It should be possible to run the test suite manually, upstream, via a GitHub workflow that requires input parameters, specifically:
The bootable JAR Maven plugin version (Optional): the version of the WildFly JAR Maven plugin to be used. If not provided the default valued provided by the test suite properties in the POM file will be used.
The WildFly fork/branch to be used (Optional): both the Git repository and branch references to identifya WildFly codebase that should be built and used to test with. If not provided, then the test suite will download the distribution version which is set by the the project properties in the POM file.
This issue is to track the work for implementing a GitHub workflow that can be executed manually to verify changes against a given, or default, WildFly distribution.
It should be possible to run the test suite manually, upstream, via a GitHub workflow that requires input parameters, specifically:
This issue is to track the work for implementing a GitHub workflow that can be executed manually to verify changes against a given, or default, WildFly distribution.