[jbosstools-issues] [JBoss JIRA] (JBIDE-19116) itests not being linked from build page

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036256#comment-13036256 ] 

Nick Boldt edited comment on JBIDE-19116 at 1/29/15 10:50 AM:
--------------------------------------------------------------

The above worked, but using "sources/*/\*tests/\*/target/surefire-reports/TEST-\*.xml" might be simpler. Running now:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/ >=664

Incidentally, I thought we wanted to NOT run all the itests in CI build jobs. Do they need to run every time? Maybe we want to have ONE job that runs weekly to run ALL the ITests across all the components? [~maxandersen] WDYT?


was (Author: nickboldt):
The above worked, but using "sources/*/*tests/*/target/surefire-reports/TEST-*.xml" might be simpler. Running now:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/ >=664

Incidentally, I thought we wanted to NOT run all the itests in CI build jobs. Do they need to run every time? Maybe we want to have ONE job that runs weekly to run ALL the ITests across all the components? [~maxandersen] WDYT?

> itests not being linked from build page
> ---------------------------------------
>
>                 Key: JBIDE-19116
>                 URL: https://issues.jboss.org/browse/JBIDE-19116
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>            Reporter: Rob Stryker
>            Assignee: Mickael Istria
>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/660/
> There is no link to the itests, and yet the build has failed. This makes it troublesome to browse the failing tests. 



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)