[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-23733: ------------------------------------------ Before creating a PR with any change to ITests I will at first try to run them on CCI. So lets say I have made a new test for cdi. My branch is cdi_newTest on rawagner fork of jbosstools-integration-tests repository. Before creating a PR I want to see if the new test is running fine on Mac/Linux/Windows. So I will run this job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... with TESTS_FORK set to "rawagner" and TEST_BRANCH to "cdi_newTest". If we would group cdi,jsf,seam, batch to one javaee job how would I be able to run just cdi part to see if the change works fine on all platforms ? I guess this could be somehow configured but we QE dont divide the components based on which repo they are in - so currently javaee components are owned by 2 or 3 different people. So with the workflow described above we could be blocked by each other or we would have to allow parallel execution which seems a bit messy to me. We could divide the QE jobs based on owner instead of repo - so my job would consist of browsersim,vpe,hibernate,livereload. But I think that job's name should express what components it is running and I have no idea what the name would look like :) -- This message was sent by Atlassian JIRA (v7.2.3#72005)