[ https://issues.jboss.org/browse/JBIDE-23734?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23734: ------------------------------------ I agree: for all build and PR jobs, we should be running the {color:green}*QUICK RUNNING*{color} Unit and UI (type 1 and 2) tests. Then once a week we can run the {color:red}*SLOW RUNNING*{color} ITests (type 3 and 4). Thanks for moving the views! So... I guess the next step is to dedupe the .prcheck jobs [1] vs. the -Pull-Request jobs [2] ? [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... We should decide if it makes sense to have 1 job per project (server), 1 job per functional grouping (as, archives, jmx, ...), or one MATRIX job per project, broken into functional groupings (eg., like the javaee-tests job [3]). Personally, I like the matrix approach because you can re-run just the failing parts, or run the whole suite for the whole project. [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)