[
https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug...
]
Yeray Borges edited comment on WFCORE-4822 at 1/31/20 9:00 AM:
---------------------------------------------------------------
I haven't checked, but my very vague idea is when we cancel a Job, CI could kick it
off automatically again, and then if we are not faster enough pushing up the new commit,
the new Job picks up the old one.
was (Author: yersan):
I haven't checked, but my very vague idea is when we cancel a Job, CI could kick it
off automatically again, and then if we are not faster enough pushing up the new commit,
the new Job picks up the latest commit.
Upgrade Management API Version to 12.0
--------------------------------------
Key: WFCORE-4822
URL:
https://issues.redhat.com/browse/WFCORE-4822
Project: WildFly Core
Issue Type: Bug
Components: Management
Reporter: Jeff Mesnil
Assignee: Yeray Borges
Priority: Blocker
Fix For: 11.0.0.Beta8
We need to fix the version state before WildFly 19 is released.
* The KernelAPIVersion must be bumped to 12.0
* We also need to release wildly-config-12.0.xsd with the proper host-exclude for
* WildFlY18, Version.10
* EAP73, Version.10
(and add those to KnownRelease too)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)