[jbosstools-issues] [JBoss JIRA] (JBIDE-10671) [performance tuning] create separate jbosstools-nightly-staging-composite site for SOA Tooling

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-10671 at 1/19/12 10:14 AM:
--------------------------------------------------------------

Log of build of soa-site (without SwitchYard). Shows what's downloaded (metadata, plugins, features) and from where.

Can also read logs from Jenkins builds here: http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.aggregate/ (and here: http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.soa-tooling.updatesite/)
                
      was (Author: nickboldt):
    Log of build of soa-site (without SwitchYard). Shows what's downloaded (metadata, plugins, features) and from where.
                  
> [performance tuning] create separate jbosstools-nightly-staging-composite site for SOA Tooling 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10671
>                 URL: https://issues.jboss.org/browse/JBIDE-10671
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, updatesite
>    Affects Versions: 3.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Douglas Palmer
>             Fix For: 3.3.0.Beta1
>
>         Attachments: soa-site.build.txt
>
>
> To speed up SOA Tooling aggregate build, source from a new URL instead of http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no metadata for content that will ultimately not be included in the site will be downloaded -- only metadata for staged SOA nightlies will be read/used.
> 1. create new site http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar (need two sites for use with trunk and stable_branch)
> 2. Add new propert(ies) to parent pom.xml (to complement jbosstools-nightly-staging-composite)
> 3. Replace reference to jbosstools-nightly-staging-composite in build/aggregate/soa-site/pom.xml with new URL
> 4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly JBT Core site (for trunk or stable_branch), eg., http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve dependencies to common components in JBT Core or the SOA site won't be able to build/resolve/get installed.
> 5. respin to verify

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