[jbosstools-issues] [JBoss JIRA] (JBIDE-10974) Use Xvfb for build jobs instead of Xvnc

[Denis Golovin (JIRA)]

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

Denis Golovin edited comment on JBIDE-10974 at 3/5/12 1:20 PM:
---------------------------------------------------------------

It is not really major problem to spend time for :)
Slowness of our builds is related to:
1. Metadata downloading and analyzing (for example common component needs only TP and tests, but it is anyway use nightly composit repository with metadata for all components, another example is using remote and local version of target platform at the same time and etc)
2. Building parent pom in every single project even if it is not required anymore (this is minor)
3. Checkout from SVN is extremely slow and it happens pretty often because of slaves cleanup
4. Using very generic ant pattern for searching files like \*\*/TEXT\*.xml, force hudson to go over all project tree which is huge and takes time, I prefer use something more determined like sources/tests/\*/target/surefire-reports/TEST*.xml
5. Two steps build per component (first build everything without tests, publish, then build tests and run them) Could be good to have one test plugin that aggregates all TestSuites from component test plugins to run them at once.
6. Extra component bits publishing. When component build triggered by component build it depends on (like common triggers jst) bits get published even there were no changes
7. All tests are UI tests even for *.core plugins. It happens because most of our *.core plugins actually references eclipse.ui packages where workbench instance is required
8. Mixing of shell, ant and maven instead of using maven only with ant calls form it where it is really needed (minor one, but really annoying when you need run it on windows and have to install cygwin)
9. Every change in build component triggers full rebuild for all components
10. Aggregation builds happen to often and it reduces number of slaves available for component builds.

That's what I remember from top of my head

                
      was (Author: dgolovin):
    It is not really major problem to spend time for :)
Slowness of our builds is related to:
1. Metadata downloading and analyzing (for example common component needs only TP and tests, but it is anyway use nightly composit repository with metadata for all components, another example is using remote and local version of target platform at the same time and etc)
2. Building parent pom in every single project even if it is not required anymore (this is minor)
3. Checkout from SVN is extremely slow and it happens pretty often because of slaves cleanup
4. Using very generic ant pattern for searching files like **/TEXT*.xml, force hudson to go over all project tree which is huge and takes time, I prefer use something more determined like sources/tests/*/target/surefire-reports/TEST*.xml
5. Two steps build per component (first build everything without tests, publish, then build tests and run them) Could be good to have one test plugin that aggregates all TestSuites from component test plugins to run them at once.
6. Extra component bits publishing. When component build triggered by component build it depends on (like common triggers jst) bits get published even there were no changes
7. All tests are UI tests even for *.core plugins. It happens because most of our *.core plugins actually references eclipse.ui packages where workbench instance is required
8. Mixing of shell, ant and maven instead of using maven only with ant calls form it where it is really needed (minor one, but really annoying when you need run it on windows and have to install cygwin)
9. Every change in build component triggers full rebuild for all components
10. Aggregation builds happen to often and it reduces number of slaves available for component builds.

That's what I remember from top of my head

                  
> Use Xvfb for build jobs instead of Xvnc
> ---------------------------------------
>
>                 Key: JBIDE-10974
>                 URL: https://issues.jboss.org/browse/JBIDE-10974
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: Build/Releng
>         Environment: any
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>
> Xvfb is a minimalist in-memory X server, without VNC. For our use-case, Xvfb may be faster and may avoid some of the issues we have with Xvnc.
> A Jenkins plugin exists to use Xvfb in Jenkins: https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin
> It requires Xvfb to be install in the slaves we use of IC, and the plugin installed on Jenkins.

--
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