[
https://issues.jboss.org/browse/RFPL-3367?page=com.atlassian.jira.plugin....
]
Jiří Štefek edited comment on RFPL-3367 at 5/7/14 5:48 AM:
-----------------------------------------------------------
Do we need the suites at all? Couldn't we create one parametrized matrix job for all
components ( = one axis for component, second axis for container)? Or will it be
unmaintainable? Will it be a big overload for the slaves?
Something like this job:
[
richfaces-4.3-release-metamer-ftest--server-compatibility-tables-2|https:...].
was (Author: jstefek):
Do we need the suites at all? Couldn't we create one parametrized matrix job for all
components ( = one axis for component, second axis for container)? Or will it be
unmaintainable? Will it be a big overload for the slaves?
Split suites to decrease job run times and to acquire better
feedback
---------------------------------------------------------------------
Key: RFPL-3367
URL:
https://issues.jboss.org/browse/RFPL-3367
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: QE
Reporter: Jiří Štefek
The suite for tables is now too big and it cannot run on Jenkins under {color:red}900
mins{color}, we need to split it somehow. But, imho, it is not just problem of this suite,
we should divide all suites somehow to gain at least a better feedback.
Any ideas how to divide the suites?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)