[jbosstools-issues] [JBoss JIRA] (JBIDE-23734) dedupe vpe unit test jobs / migrate vpe builds to CCI
Nick Boldt (JIRA)
issues at jboss.org
Fri Jan 27 11:09:00 EST 2017
[ https://issues.jboss.org/browse/JBIDE-23734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13354452#comment-13354452 ]
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/Devstudio/view/devstudio_integration_tests_prcheck/
[2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_pull_requests/
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/Devstudio/view/devstudio_master/job/jbosstools-javaee-tests-matrix_master/
> dedupe vpe unit test jobs / migrate vpe builds to CCI
> -----------------------------------------------------
>
> Key: JBIDE-23734
> URL: https://issues.jboss.org/browse/JBIDE-23734
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.4.3.Final
>
>
> There are four VPE unit test jobs. We probably only need 2 of those.
> These both run on multiple OSes:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio_integration_tests/job/vpe.unittests/
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master_otherOS/job/jbosstools-vpe_master_otherOS/
> These probably run the same unit tests, but against master or 4.4.x branches, and are called from the VPE build jobs [1], [2] on Boston MW Jenkins (because the tests were failing to run in Boston):
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio_pull_requests/job/jbosstools-vpe-Run-Unit-Tests_master/
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio_pull_requests/job/jbosstools-vpe-Run-Unit-Tests_4.4.neon/
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master/
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_4.4.neon/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jbosstools-issues
mailing list