-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WFLY-4811] Add new batch-jberet subsystems #7806
Conversation
Windows Build 2176 is now running using a merge of 7eca336 |
Linux Build 7124 is now running using a merge of 7eca336 |
Linux with security manager Build 1997 is now running using a merge of 7eca336 |
Linux with security manager Build 1997 outcome was SUCCESS using a merge of 7eca336 |
Linux Build 7124 outcome was FAILURE using a merge of 7eca336 Build problems:Failed tests detected Failed tests
|
Windows Build 2176 outcome was FAILURE using a merge of 7eca336 Build problems:Failed tests detected Failed tests
|
retest this please |
Linux Build 7139 is now running using a merge of 7eca336 |
Windows Build 2192 is now running using a merge of 7eca336 |
Linux with security manager Build 2012 is now running using a merge of 7eca336 |
Linux with security manager Build 2012 outcome was SUCCESS using a merge of 7eca336 |
Windows Build 2192 outcome was FAILURE using a merge of 7eca336 Build problems:Failed tests detected Failed tests
|
Linux Build 7139 outcome was FAILURE using a merge of 7eca336 Build problems:Failed tests detected Failed tests
|
Linux Build 7144 is now running using a merge of e6c5e16 |
Windows Build 2197 is now running using a merge of e6c5e16 |
Linux with security manager Build 2017 is now running using a merge of e6c5e16 |
Linux with security manager Build 2017 outcome was SUCCESS using a merge of e6c5e16 |
Linux Build 7144 outcome was FAILURE using a merge of e6c5e16 Build problems:Failed tests detected Failed tests
|
Windows Build 2197 outcome was FAILURE using a merge of e6c5e16 Build problems:Failed tests detected Failed tests
|
Linux Build 7146 is now running using a merge of 44b096d |
Windows Build 2199 is now running using a merge of 44b096d |
Linux with security manager Build 2019 is now running using a merge of 44b096d |
Linux with security manager Build 2019 outcome was SUCCESS using a merge of 44b096d |
Linux Build 7146 outcome was FAILURE using a merge of 44b096d Build problems:Failed tests detected Failed tests
|
Windows Build 2199 outcome was FAILURE using a merge of 44b096d Build problems:Failed tests detected Failed tests
|
…the jboss-all.xml deployment descriptor." This reverts commit bd8c818. This will only be present in the new batch-jberet subsystem.
Linux with security manager Build 2033 is now running using a merge of 949329c |
Linux Build 7161 is now running using a merge of 949329c |
Windows Build 2217 is now running using a merge of 949329c |
Linux with security manager Build 2033 outcome was SUCCESS using a merge of 949329c |
Linux Build 7161 outcome was SUCCESS using a merge of 949329c |
Windows Build 2217 outcome was SUCCESS using a merge of 949329c |
[WFLY-4811] Add new batch-jberet subsystems
This PR adds a new
batch-jberet
subsystem.First Commit
This commit reverts a change to the original batch subsystem that will only be allowed in the new subsystem.
Second Commit
This commit brings JBeret to a level required for the new subsystem.
Third Commit
This commit just changes a few things to prepare for the new subsystem. It could be squashed with the next commit, but for the review process it may be easier having it separate.
Fourth Commit
This commit is the addition of the new subsystem. The new subsystem model looks like the following.
This new model allows for the use of capabilities & requirements as well as hopefully cleans up the user experience. The
default-job-repository
anddefault-thread-pool
attributes seem a bit awkward to me, but allow the deployments to work without a deployment descriptor.The JNDI name is no longer used for a
jdbc-job-repository
. The data source capability is used and the data source is no longer looked up via a JNDI lookup.Multiple thread pools and job repositories are allowed to be defined. The
jboss-all.xml
deployment descriptor can be used to define specific job repositories or thread pools to the deployment.Once this is acceptable I will submit a PR for the capabilities documentation.
Fifth Commit
This is just the tests and can be squashed with the third commit. I only left this separate as it may be easier to review the commits separated.