[jbosstools-issues] [JBoss JIRA] (JBIDE-11639) Remove patterns starts from "**/" from hudson configuration for JBoss Tools build projects

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-11639:
----------------------------------------

Denis,

I has a look at the configuration of jobs and found that only a few ones (from SOATooling mainly do specify such regexp) for tests. Do you have any other example in mind?
As per coverage.xml, The latest config contains direct path. The only component still to improve greedy regexp is --common. Did you already made the update?
I also replaced the regexp for publisher to remove **.
 
                
> Remove patterns starts from "**/" from hudson configuration for JBoss Tools build projects
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-11639
>                 URL: https://issues.jboss.org/browse/JBIDE-11639
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Denis Golovin
>            Assignee: Mickael Istria
>            Priority: Critical
>             Fix For: 3.3.0.Beta3
>
>
> Once I removed all patterns like 
> {code}"**/TESTS-*.xml"{code}
> from all JBT related builds from trunk but they keeps coming back.
> Such patterns for searching files in emma code coverage publishing, JUnit reports gathering or anywhere else in hudson project configuartion are evil because it slows down builds. After each build hudson should iterate overs everything in workspace (sources, build results, local maven repo) to find (in example above) JUnit test results. It should be something like
> {code}sources/tests/*/target/surefire-reports/TEST*.xml{code}
> which is much faster comparing to one uses "**" pattern.
> The same for code coverage xml. Instead of putting something like
> {code}**/coverage.xml{code}
> to find just one file in whole workspace use just direct path to this file
> it saves from couple to tens minutes for component build and if we look at build numbers HXXXX it becomes huge waste of time

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira