Sorry for delay. See my comments inline.
thanks, Vladimir
On 8/17/06, Fedotov, Alexei A <[EMAIL PROTECTED]> wrote:
Vladimir,
I was trying a buildtest module from svn repository.
You wrote,
>When I tried to run it for the first time I saw problems with <get>
>and <svn> commands - they did not work in my environment due to:
> - no proxy settings for <get> and <exec svn> command.
> - some problems with my certificate for apache site.
Is there any progress with making <get> command work? I tried to make it
work.
1. I succeed to make <get> work through proxy by changing cc/config.xml
(= config/config-full.xml) in a following way:
<schedule interval="300">
<ant antWorkingDir="projects/classlib/trunk"
target="fetch-depends">
<jvmarg arg="-Dhttp.proxyHost=***.com "/>
<jvmarg arg="-Dhttp.proxyPort=***"/>
</ant>
</schedule>
2. Setting CC_OPTS (like ANT_OPTS) doesn't help me to rewrite the
configuration file in a following way.
<schedule interval="300">
<ant antWorkingDir="projects/classlib/trunk"
target="fetch-depends">
<jvmarg arg="- Dhttp.proxyHost=${http.proxyHost}"/>
<jvmarg arg="-Dhttp.proxyPort=${http.proxyPort}"/>
</ant>
</schedule>
So I've created config/cc.properties and used
<?xml version="1.0" encoding="UTF-8"?>
<cruisecontrol>
+ <property file="cc.properties"/>
Using this approach I managed to make classlib-deps and drlvm-deps. Do
you think this is a correct direction to develop proxy support?
The proxy should be added by condition (non-empty value in the property
file, for example) to work correctly in the non-proxy environment. Your can
copy this part of script from the build.xml.
BTW, why the config file is called config-full.xml? I prefer to call it
cc-config.xml.
I think, we should ask author (Geir :) ) about it. But it seems logically to
have different configuration for CC to minimize computers load (we can
separate CC for API and VM parts for example).
With best regards,
Alexei Fedotov,
Intel Middleware Products Division
>-----Original Message-----
>From: Vladimir Ivanov [mailto:[EMAIL PROTECTED]
>Sent: Thursday, July 27, 2006 3:56 PM
>To: harmony-dev@incubator.apache.org; [EMAIL PROTECTED]
>Subject: Re: [build-test-infra] Build Test Infrastructure
>
>On 7/26/06, Geir Magnusson Jr < [EMAIL PROTECTED]> wrote:
>>
>>
>>
>>
>> That's what the buildtest subproject is for. Have you looked at it?
>
>
>
>Yes. When I tried to run it for the first time I saw problems with
<get>
>and
><svn> commands - they did not work in my environment due to:
> - no proxy settings for <get> and <exec svn> command.
> - some problems with my certificate for apache site.
>
>I propose to do the following:
> - specify in README.txt that if you work via proxy, then, specify in
>property file values for proxy host/port and checks proxy settings into
>your
>SVN configuration files.
> - specify in README.txt that the certificate to work with apache site
>should be accepted.
>
>Does it make sense?
>Issue 995 was created to support proxy settings for the 'get' target.
>
>
>
>> > 4. Full testing - the whole set of Harmony tests are run on
>> regular
>> > builds, results are published.
>> > Goal: to see what happened with Harmony quality on the whole set of
>> > automated tests, see new bugs, see quality of Harmony runtimes.
>> > Users should be able to do this kind of testing on their specific
>> platforms
>> > and publish results on Harmony web site.
>> > ****This script (prototype) I implemented, see issue 984.
>>
>> I thought that the classlib tests are run as well w/ the CC script
right
>> now, but will check.
>
>
>Yes, but I hope in the future we will have more test suites
(functional,
>stress etc).
>Will we run all of them in code integrity testing? - I suppose no, once
we
>see that running all tests takes more then hour.
>
> Thanks, Vladimir
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
