Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <2369801.1191323570559.JavaMail.jira@brutus>
Date: Tue, 2 Oct 2007 04:12:50 -0700 (PDT)
From: "Alexey Varlamov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Updated: (HARMONY-4883) [bti] BTI polls SVN repository too
 eagerly
In-Reply-To: <24146514.1191318530577.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HARMONY-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Varlamov updated HARMONY-4883:
-------------------------------------

    Attachment: hdk-build.diff

Finally, allow to customize SVN root url, defaults to "http://svn.apache.org/repos/asf"

> [bti] BTI polls SVN repository too eagerly
> ------------------------------------------
>
>                 Key: HARMONY-4883
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4883
>             Project: Harmony
>          Issue Type: Bug
>          Components: build - test - ci
>            Reporter: Alexey Varlamov
>            Priority: Critical
>         Attachments: bti-fix.diff, hdk-adaptor.diff, hdk-build.diff
>
>
> The Integrity Testing infra built on BTI 2.0 issues too much requests to SVN server. Most of requests are not really needed and may be optimized out w/o loosing any functionality. Also note that standard ASF policy [1] states: "Please do not use programs that poll the repository more frequently than hourly."
> Here is the initial analysis:
> 1) Default CC interval is 300 sec, which is actual when there is no SVN modifications (e.g. during weekends). Apparently it must be increased.
> 2) Using SVNbootstrapper feature of CC is not feasible, BTI should only update workspace after actual modification is detected;
> 3) Significant overhead is added by dependency-handling machinery autogenerated by BTI. In particular, each test adaptor checks parent's SVN repository twice (!): 1st time it uses Veto to possibly yield tests execution in favor of parent, and then obtains list of modifications to include them in test report. 4) Repository layout for HDK is rather complicated, consisting of 5 separate locations. Unfortunately standard CC plugins do not allow to poll them all at once, a sequence of requests to SVN is needed. Neverthless current HDK adaptor is suboptimal, it should be more fine-graned to leverage HDK build peculiarities.
> 5) We should consider using HTTP vs HTTPS by default, to save traffic and server load.
> [1] http://apache.org/dev/version-control.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.