Re: Nightly builds docu?

[Geir Magnusson Jr.]

On Jan 18, 2007, at 8:57 AM, Henri Yandell wrote:


On 1/17/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:

So how about biting the bullet and installing one of the well
established and obviously easier tools:


* Cruise Control (http://cruisecontrol.sourceforge.net/)


Just downloaded this the other day to sit and play with. When last I
looked at it I disregarded it because it insisted on a source only
distribution and its source wouldn't build on OS X.

They had a new release recently and a binary, so I'm aiming to give  
that a shot.


FWIW, I like it a lot.  When I was deciding on a CI system for  
harmony, I looked at a few and eventually settled on CC, because it  
had no inherent bias to what you were running, and while a bit rought  
around the edges, seemed to have lots of nice little features.


geir


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Henri Yandell]

On 1/17/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:

So how about biting the bullet and installing one of the well
established and obviously easier tools:


* Cruise Control (http://cruisecontrol.sourceforge.net/)


Just downloaded this the other day to sit and play with. When last I
looked at it I disregarded it because it insisted on a source only
distribution and its source wouldn't build on OS X.

They had a new release recently and a binary, so I'm aiming to give that a shot.


* anthill (https://www.anthillpro.com/html/products/anthillos/)


I've always leaned away from free versions that had commercial
superset versions (crippleware). They just changed to a more JIRA like
model.


* Luntbuild (http://luntbuild.javaforge.com/)


Not looked at this in a while (since it was much more recent), but
it's another crippleware. My gut instinct on such things is that while
that'd be fine for half a dozen subprojects within a project, we're
going to find ourselves wanting many of the 'enterprise' features if
we were to scope.


While I appreciate that we do have a ASL licensed CI product, the
arguments "it is too complicated to set up" and "it is better to have
none than having not-Continuum" don't work well with me.


Neither were my arguments. Actually my biggest +ve for Continuum is
that it is very easy to setup.

Reasons against Continuum are:

* Maven were going to run a Continuum on vmbuild and decided not to
due to the machine - so I'm not going to dive in trying to do the
same. There's discusion ongoing to get a machine with more cpu spare.

* I think it's easy to write a specific CI script and hard to write a
generic CI tool. Plus I'm not very bought off on the "gui so you can
do a build 'now!'" bits.

Phil's quick script, and Craig's before that, have been fine in
Commons - but we're going to start needing a visual representation one
of these days and that starts to send you into the CI product world.
We still build everything each day - which would be a hog if we kept
on adding things. However a condition of conditional on-svn-update
builds is that you have to start representing your state - it's more
than just "Last night".

Hen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Henning Schmiedehausen]

So how about biting the bullet and installing one of the well 
established and obviously easier tools:



* Cruise Control (http://cruisecontrol.sourceforge.net/)
* anthill (https://www.anthillpro.com/html/products/anthillos/)
* Luntbuild (http://luntbuild.javaforge.com/)

While I appreciate that we do have a ASL licensed CI product, the 
arguments "it is too complicated to set up" and "it is better to have 
none than having not-Continuum" don't work well with me.


(I've only glanced at Luntbuild but its feature list seems impressive.)

Best regards
Henning

Henri Yandell schrieb:

Gump's up and running. It was sounding like it was a bit dead, but
seems to have got active again with maven-2 support here or nearly
here. The biggest problem with Gump is that it's not a CI system -
it's a social experiment and it's aim is to tell people when trunks
are breaking for them and not to create nightly artifacts. That might
have changed though. They just started working with Harmony (that's
one of my wishlist bits for whatever build we use - build 1.4, 1.5,
1.6 and Harmony for each project - plus it should be testing the ant,
maven1 and maven2 builds).

vmbuild was intended to be a zone/machine for Continuum - but it
didn't have the cycles. The nightly spamassassin is on the same
machine and (allegedly) eats them all up. There's some talk of setting
a distributed Continuum up, but it involves a fair amount of people
working together so I wouldn't expect that any time soon.

Hen

On 1/17/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:

As we have at least one "CI" tool inside the ASF: How about setting up
one of these for the nightlies?

Best regards
Henning



Martin van den Bemt schrieb:
> Gump doesn't build against the versions of the dependencies 
specified in the pom / project.xml, but
> builds against the latest of everything, which could mean other 
trouble if you are using those jars.

>
> Mvgr,
> Martin
>
> Andrew C. Oliver wrote:
>> Ummwhy not out of Gump?
>>
>> Phil Steitz wrote:
>>> Henri Yandell wrote:
>>>
>>>> On 1/16/07, Ortwin Glück <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Does anyone (Henry?) know what happened to
>>>>>   http://www.apache.org/dev/nightly-builds.html ?
>>>>>
>>>>> It's referenced from
>>>>>   http://www.apache.org/dev/
>>>>> at the very bottom of the page. I'm looking for information how 
to get

>>>>> nightly builds done for HttpComponents.
>>>>>
>>>> It probably never existed. When that page was created the links were
>>>> made for pages that didn't exist to encourage people to write them -
>>>> didn't work :)
>>>>
>>>> Nightly build wise... it's still an unorganized situation. In 
Commons
>>>> we have some hand written scripts that are used on a zone 
(vmbuild) to

>>>> build the code each night. Taglibs used to be built each night on
>>>> Glenn's machine (I suspect that's not true anymore).
>>>>
>>>> We could expand the script for Commons to work from the Jakarta
>>>> perspective and not the Commons one.
>>> +1 and would not be hard to do.  Makes sense to do this for all 
Jakarta

>>> components that want nightlies and as long as the builds are
>>> "reasonable" in execution time, this should not be a problem.  The
>>> current script supports Ant, Maven 1 and Maven 2.   The script 
code is

>>> in svn at jakarta/commons/proper/commons-nightly/.  The main script,
>>> commons_nigthly.sh gets svn upped on vmbuild by a crontab wrapper 
before
>>> executing each night, so if you just make changes to include a new 
build
>>> or build type into this script and config and check in the 
changes, the

>>> new component will be added.
>>> Phil
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux
91054 Buckenhof, Germany   -- +49 9131 506540  | Apache person
Open Source Consulting, Development, Design| Velocity - Turbine

  "Save the cheerleader. Save the world."

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux
91054 Buckenhof, Germany   -- +49 9131 506540  | Apache person
Open Source Consulting, Development, Design| Velocity - Turbine

  "Save the cheerleader. Save the world."

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Henri Yandell]

Gump's up and running. It was sounding like it was a bit dead, but
seems to have got active again with maven-2 support here or nearly
here. The biggest problem with Gump is that it's not a CI system -
it's a social experiment and it's aim is to tell people when trunks
are breaking for them and not to create nightly artifacts. That might
have changed though. They just started working with Harmony (that's
one of my wishlist bits for whatever build we use - build 1.4, 1.5,
1.6 and Harmony for each project - plus it should be testing the ant,
maven1 and maven2 builds).

vmbuild was intended to be a zone/machine for Continuum - but it
didn't have the cycles. The nightly spamassassin is on the same
machine and (allegedly) eats them all up. There's some talk of setting
a distributed Continuum up, but it involves a fair amount of people
working together so I wouldn't expect that any time soon.

Hen

On 1/17/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:

As we have at least one "CI" tool inside the ASF: How about setting up
one of these for the nightlies?

Best regards
Henning



Martin van den Bemt schrieb:
> Gump doesn't build against the versions of the dependencies specified in the 
pom / project.xml, but
> builds against the latest of everything, which could mean other trouble if 
you are using those jars.
>
> Mvgr,
> Martin
>
> Andrew C. Oliver wrote:
>> Ummwhy not out of Gump?
>>
>> Phil Steitz wrote:
>>> Henri Yandell wrote:
>>>
>>>> On 1/16/07, Ortwin Glück <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Does anyone (Henry?) know what happened to
>>>>>   http://www.apache.org/dev/nightly-builds.html ?
>>>>>
>>>>> It's referenced from
>>>>>   http://www.apache.org/dev/
>>>>> at the very bottom of the page. I'm looking for information how to get
>>>>> nightly builds done for HttpComponents.
>>>>>
>>>> It probably never existed. When that page was created the links were
>>>> made for pages that didn't exist to encourage people to write them -
>>>> didn't work :)
>>>>
>>>> Nightly build wise... it's still an unorganized situation. In Commons
>>>> we have some hand written scripts that are used on a zone (vmbuild) to
>>>> build the code each night. Taglibs used to be built each night on
>>>> Glenn's machine (I suspect that's not true anymore).
>>>>
>>>> We could expand the script for Commons to work from the Jakarta
>>>> perspective and not the Commons one.
>>> +1 and would not be hard to do.  Makes sense to do this for all Jakarta
>>> components that want nightlies and as long as the builds are
>>> "reasonable" in execution time, this should not be a problem.  The
>>> current script supports Ant, Maven 1 and Maven 2.   The script code is
>>> in svn at jakarta/commons/proper/commons-nightly/.  The main script,
>>> commons_nigthly.sh gets svn upped on vmbuild by a crontab wrapper before
>>> executing each night, so if you just make changes to include a new build
>>> or build type into this script and config and check in the changes, the
>>> new component will be added.
>>> Phil
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux
91054 Buckenhof, Germany   -- +49 9131 506540  | Apache person
Open Source Consulting, Development, Design| Velocity - Turbine

  "Save the cheerleader. Save the world."

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Henning Schmiedehausen]

As we have at least one "CI" tool inside the ASF: How about setting up 
one of these for the nightlies?


Best regards
Henning



Martin van den Bemt schrieb:

Gump doesn't build against the versions of the dependencies specified in the 
pom / project.xml, but
builds against the latest of everything, which could mean other trouble if you 
are using those jars.

Mvgr,
Martin

Andrew C. Oliver wrote:

Ummwhy not out of Gump?

Phil Steitz wrote:

Henri Yandell wrote:
 

On 1/16/07, Ortwin Glück <[EMAIL PROTECTED]> wrote:
   

Hi,

Does anyone (Henry?) know what happened to
  http://www.apache.org/dev/nightly-builds.html ?

It's referenced from
  http://www.apache.org/dev/
at the very bottom of the page. I'm looking for information how to get
nightly builds done for HttpComponents.
  

It probably never existed. When that page was created the links were
made for pages that didn't exist to encourage people to write them -
didn't work :)

Nightly build wise... it's still an unorganized situation. In Commons
we have some hand written scripts that are used on a zone (vmbuild) to
build the code each night. Taglibs used to be built each night on
Glenn's machine (I suspect that's not true anymore).

We could expand the script for Commons to work from the Jakarta
perspective and not the Commons one. 

+1 and would not be hard to do.  Makes sense to do this for all Jakarta
components that want nightlies and as long as the builds are
"reasonable" in execution time, this should not be a problem.  The
current script supports Ant, Maven 1 and Maven 2.   The script code is
in svn at jakarta/commons/proper/commons-nightly/.  The main script,
commons_nigthly.sh gets svn upped on vmbuild by a crontab wrapper before
executing each night, so if you just make changes to include a new build
or build type into this script and config and check in the changes, the
new component will be added. 
Phil



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux
91054 Buckenhof, Germany   -- +49 9131 506540  | Apache person
Open Source Consulting, Development, Design| Velocity - Turbine

  "Save the cheerleader. Save the world."

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Martin van den Bemt]

Gump doesn't build against the versions of the dependencies specified in the 
pom / project.xml, but
builds against the latest of everything, which could mean other trouble if you 
are using those jars.

Mvgr,
Martin

Andrew C. Oliver wrote:
> Ummwhy not out of Gump?
> 
> Phil Steitz wrote:
>> Henri Yandell wrote:
>>  
>>> On 1/16/07, Ortwin Glück <[EMAIL PROTECTED]> wrote:
>>>
>>>> Hi,
>>>>
>>>> Does anyone (Henry?) know what happened to
>>>>   http://www.apache.org/dev/nightly-builds.html ?
>>>>
>>>> It's referenced from
>>>>   http://www.apache.org/dev/
>>>> at the very bottom of the page. I'm looking for information how to get
>>>> nightly builds done for HttpComponents.
>>>>   
>>> It probably never existed. When that page was created the links were
>>> made for pages that didn't exist to encourage people to write them -
>>> didn't work :)
>>>
>>> Nightly build wise... it's still an unorganized situation. In Commons
>>> we have some hand written scripts that are used on a zone (vmbuild) to
>>> build the code each night. Taglibs used to be built each night on
>>> Glenn's machine (I suspect that's not true anymore).
>>>
>>> We could expand the script for Commons to work from the Jakarta
>>> perspective and not the Commons one. 
>> +1 and would not be hard to do.  Makes sense to do this for all Jakarta
>> components that want nightlies and as long as the builds are
>> "reasonable" in execution time, this should not be a problem.  The
>> current script supports Ant, Maven 1 and Maven 2.   The script code is
>> in svn at jakarta/commons/proper/commons-nightly/.  The main script,
>> commons_nigthly.sh gets svn upped on vmbuild by a crontab wrapper before
>> executing each night, so if you just make changes to include a new build
>> or build type into this script and config and check in the changes, the
>> new component will be added. 
>> Phil
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>   
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Ortwin Glück]

Andrew C. Oliver wrote:

Ummwhy not out of Gump?


Commons-HttpClient is being built by Gump. We have always been very 
happy with it. What does it take to integrate some artifacts from 
HttpComponents?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Andrew C. Oliver]

Ummwhy not out of Gump?

Phil Steitz wrote:

Henri Yandell wrote:
  

On 1/16/07, Ortwin Glück <[EMAIL PROTECTED]> wrote:


Hi,

Does anyone (Henry?) know what happened to
  http://www.apache.org/dev/nightly-builds.html ?

It's referenced from
  http://www.apache.org/dev/
at the very bottom of the page. I'm looking for information how to get
nightly builds done for HttpComponents.
  

It probably never existed. When that page was created the links were
made for pages that didn't exist to encourage people to write them -
didn't work :)

Nightly build wise... it's still an unorganized situation. In Commons
we have some hand written scripts that are used on a zone (vmbuild) to
build the code each night. Taglibs used to be built each night on
Glenn's machine (I suspect that's not true anymore).

We could expand the script for Commons to work from the Jakarta
perspective and not the Commons one. 


+1 and would not be hard to do.  Makes sense to do this for all Jakarta
components that want nightlies and as long as the builds are
"reasonable" in execution time, this should not be a problem.  The
current script supports Ant, Maven 1 and Maven 2.   The script code is
in svn at jakarta/commons/proper/commons-nightly/.  The main script,
commons_nigthly.sh gets svn upped on vmbuild by a crontab wrapper before
executing each night, so if you just make changes to include a new build
or build type into this script and config and check in the changes, the
new component will be added.  


Phil


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  



--
No PST Files Ever Again
Buni Meldware Communication Suite
Email, Calendaring, ease of configuration/administration
http://buni.org



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Phil Steitz]

Henri Yandell wrote:
> On 1/16/07, Ortwin Glück <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> Does anyone (Henry?) know what happened to
>>   http://www.apache.org/dev/nightly-builds.html ?
>>
>> It's referenced from
>>   http://www.apache.org/dev/
>> at the very bottom of the page. I'm looking for information how to get
>> nightly builds done for HttpComponents.
>
> It probably never existed. When that page was created the links were
> made for pages that didn't exist to encourage people to write them -
> didn't work :)
>
> Nightly build wise... it's still an unorganized situation. In Commons
> we have some hand written scripts that are used on a zone (vmbuild) to
> build the code each night. Taglibs used to be built each night on
> Glenn's machine (I suspect that's not true anymore).
>
> We could expand the script for Commons to work from the Jakarta
> perspective and not the Commons one. 
+1 and would not be hard to do.  Makes sense to do this for all Jakarta
components that want nightlies and as long as the builds are
"reasonable" in execution time, this should not be a problem.  The
current script supports Ant, Maven 1 and Maven 2.   The script code is
in svn at jakarta/commons/proper/commons-nightly/.  The main script,
commons_nigthly.sh gets svn upped on vmbuild by a crontab wrapper before
executing each night, so if you just make changes to include a new build
or build type into this script and config and check in the changes, the
new component will be added.  

Phil


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds docu?

[Henri Yandell]

On 1/16/07, Ortwin Glück <[EMAIL PROTECTED]> wrote:

Hi,

Does anyone (Henry?) know what happened to
  http://www.apache.org/dev/nightly-builds.html ?

It's referenced from
  http://www.apache.org/dev/
at the very bottom of the page. I'm looking for information how to get
nightly builds done for HttpComponents.


It probably never existed. When that page was created the links were
made for pages that didn't exist to encourage people to write them -
didn't work :)

Nightly build wise... it's still an unorganized situation. In Commons
we have some hand written scripts that are used on a zone (vmbuild) to
build the code each night. Taglibs used to be built each night on
Glenn's machine (I suspect that's not true anymore).

We could expand the script for Commons to work from the Jakarta
perspective and not the Commons one. I often ponder if that should be
replaced with a Continuum instance (especially with Commons being just
about on Maven-2 now), but afaiu vmbuild is considered too
crap/overloaded to run lots of builds in Continuum.

Hen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Nightly builds docu?

[Ortwin Glück]

Hi,

Does anyone (Henry?) know what happened to
 http://www.apache.org/dev/nightly-builds.html ?

It's referenced from
 http://www.apache.org/dev/
at the very bottom of the page. I'm looking for information how to get 
nightly builds done for HttpComponents.


Ortwin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: nightly builds

[Will Glass-Husain]

Thanks.  Anyone want to take credit for setting up the Velocity
nightly build?  (which seems to have stopped).  It seems to be
sticking the files on svn.apache.org.

If no one steps up, I'll request privileges on svn.apache.org and dig into it.

WILL

On 8/1/06, Henri Yandell <[EMAIL PROTECTED]> wrote:


Pretty sure it's been done by each group separately. Phil just got the
Commons ones working again on a vmbuild zone - a rewrite (I think) of
scripts Craig has been running for ages.

Glenn (I think) runs some nightlies for the Taglibs on a machine of his
etc.

Hen

On Tue, 1 Aug 2006, Will Glass-Husain wrote:

> Hi,
>
> Sorry if this is something I should know, but how are the nightly
> builds put together?
>
> The Velocity build seems not to be working.
>
> https://issues.apache.org/jira/browse/INFRA-903
>
> WILL
>
> --
> Forio Business Simulations
>
> Will Glass-Husain
> [EMAIL PROTECTED]
> www.forio.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Forio Business Simulations

Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: nightly builds

[Henri Yandell]

Pretty sure it's been done by each group separately. Phil just got the 
Commons ones working again on a vmbuild zone - a rewrite (I think) of 
scripts Craig has been running for ages.


Glenn (I think) runs some nightlies for the Taglibs on a machine of his 
etc.


Hen

On Tue, 1 Aug 2006, Will Glass-Husain wrote:


Hi,

Sorry if this is something I should know, but how are the nightly
builds put together?

The Velocity build seems not to be working.

https://issues.apache.org/jira/browse/INFRA-903

WILL

--
Forio Business Simulations

Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

nightly builds

[Will Glass-Husain]

Hi,

Sorry if this is something I should know, but how are the nightly
builds put together?

The Velocity build seems not to be working.

https://issues.apache.org/jira/browse/INFRA-903

WILL

--
Forio Business Simulations

Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Help needed on JMeter nightly builds

[Sam Ruby]

Jordi Salvat i Alabart wrote:


You'll be happy to know that your effort responding your questions was 
not in vain. Gump runs are now building JMeter and producing meaningful 
results.

:-)


Gump is now building the JMeter's distribution files into 
jakarta-jmeter/dist. Would it be possible to copy all files found in 
there to http://cvs.apache.org/builds/jakarta-jmeter/nightly/ 
after each build? In this way we'll be able to decide how exactly we 
want to pack up our distribution without having to bug you again.

Added it to the list for tomorrow.  We'll see how it goes.


Just two more questions (hopefully last ones for a while):

1/ Would it be a good idea to run our unit tests during the nightly 
build? On one side, doing so would fit better into the "continuous 
integration" Gump concept. On the other side, looks like the build 
machines (or at least Nagoya) have a really tough time keeping up with 
the work, and our tests take a while... what's your opinion?

Go for it.  Yes, Nagoya is a bit pokey, but the price is right.  ;-)


2/ JMeter binary distribution contains all the jars for all the projects 
it depends on. I think it needs to be that way: JMeter is an app for 
plain users, not a library for developers, and we want it to be 
installable and runnable with minimum hassle for the user. The way it 
currently works this would cause those binaries to run against library 
versions different from the ones used at compilation -- which doesn't 
look very nice. The question is: does Gump provide a way to copy some of 
those jars into the jakarta-jmeter/lib directory before the build? Pls. 
note that I said "some", because there's a few we just can't distribute 
(licensing issues).

The basic strategy is to specify the the files that you copy with ant 
properties.  You can then tell gump to provide the actual jar name for 
this property.  The easiest way to do this is to move the  
elements for the jars that you want to do this with inside the  
element, and add a "property=" attribute.  This is best explained by 
example, so look for logkit.jar in the following files:

http://cvs.apache.org/viewcvs/jakarta-gump/project/jakarta-avalon.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup

http://cvs.apache.org/viewcvs/jakarta-avalon/build.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup

- Sam Ruby

P.S.  Don't be afraid to ask questions.  But perhaps this should be in 
the [EMAIL PROTECTED] mailing list?



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Help needed on JMeter nightly builds

[Jordi Salvat i Alabart]

Hi Sam.

You'll be happy to know that your effort responding your questions was 
not in vain. Gump runs are now building JMeter and producing meaningful 
results.

Gump is now building the JMeter's distribution files into 
jakarta-jmeter/dist. Would it be possible to copy all files found in 
there to http://cvs.apache.org/builds/jakarta-jmeter/nightly/ 
after each build? In this way we'll be able to decide how exactly we 
want to pack up our distribution without having to bug you again.

Just two more questions (hopefully last ones for a while):

1/ Would it be a good idea to run our unit tests during the nightly 
build? On one side, doing so would fit better into the "continuous 
integration" Gump concept. On the other side, looks like the build 
machines (or at least Nagoya) have a really tough time keeping up with 
the work, and our tests take a while... what's your opinion?

2/ JMeter binary distribution contains all the jars for all the projects 
it depends on. I think it needs to be that way: JMeter is an app for 
plain users, not a library for developers, and we want it to be 
installable and runnable with minimum hassle for the user. The way it 
currently works this would cause those binaries to run against library 
versions different from the ones used at compilation -- which doesn't 
look very nice. The question is: does Gump provide a way to copy some of 
those jars into the jakarta-jmeter/lib directory before the build? Pls. 
note that I said "some", because there's a few we just can't distribute 
(licensing issues).

Thanks,

Jordi.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Help needed on JMeter nightly builds

[Sam Ruby]

Jordi Salvat i Alabart wrote:


* Gump reads the project descriptors to establish a dependency tree, 
then builds each project in order.

Yes.


* Gump uses a modified "ant" which totally ignores all "classpath" 
settings -- instead it places all JARs exported by projects depended 
upon into the classpath.

Ant isn't modified, it is passed a "build.sysclasspath" paramter.  The 
version of Ant which is used to do the builds is built from cvs.

But, effectively, the result is the same.

Q1: is it then best practice to remove all those jars from our lib/*.jar 
in CVS?

While removing such jars is my preference, others will disagree. 
Suffice it to say that there is no consensus.

* Thus the Gump nightly builds always happen against the CVS versions of 
all projects -- which means that if I build JMeter from the sources on 
my workstation I won't get the exact same results (since I will be 
building against released versions of those projects).

True.

You also won't get the exact same results if you use a different 
compiler.  ;-)

* The copying of build results to 
http://cvs.apache.org/builds/jakarta-jmeter/nightly/ is not done by 
Gump. (Even though it must be run just after (some?) builds).

Q: how can I have the JMeter distribution files published there?

As you have an id on that machine, you are certainly welcome to publish 
files there.  The SCP utility is handy for such things.

Also, anything that I build with gump that you find of value, I am 
willing to upload.

You will find that a lot of things work this way around here.  While you 
will occasionally find somebody telling you what *not* to do, and often 
find that there are people who will tell you what they are willing to 
do, you will rarely find somebody telling you what to do.

In this case: if you want me to upload more, fine.  If you want me to 
upload less, fine.  Just don't ask me to build something different.

* The publishing of the src snapshot in that same directory has nothing 
to do with Gump.

gump starts out by doing a cvs update directory maintained separate from 
the build.  At the end of the gump run, that directory is zipped and 
tarred up and uploaded.

- Sam Ruby



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Help needed on JMeter nightly builds

[Jordi Salvat i Alabart]

Hi all.

Hi Sam. So it was YOU who repaired the JMeter build on the 2nd Jan! I 
was about to go mad. Anyway, thanks.

I think I get the picture now. Would you (or someone else) be so kind as 
reviewing this for severe misunderstandings?

* Gump reads the project descriptors to establish a dependency tree, 
then builds each project in order.

* Gump uses a modified "ant" which totally ignores all "classpath" 
settings -- instead it places all JARs exported by projects depended 
upon into the classpath.

Q1: is it then best practice to remove all those jars from our lib/*.jar 
in CVS?

* Thus the Gump nightly builds always happen against the CVS versions of 
all projects -- which means that if I build JMeter from the sources on 
my workstation I won't get the exact same results (since I will be 
building against released versions of those projects).

* The copying of build results to 
http://cvs.apache.org/builds/jakarta-jmeter/nightly/ is not done by 
Gump. (Even though it must be run just after (some?) builds).

Q: how can I have the JMeter distribution files published there?

* The publishing of the src snapshot in that same directory has nothing 
to do with Gump.

Salut,

Jordi.

Sam Ruby wrote:
Jordi Salvat i Alabart wrote:


Hi Sam. I'm taking this out of general to avoid bugging everyone 
around with my stupidness.


Don't be afraid to post e-mails like these on jakarta-general.  That way 
everybody can help, and everyone can learn from the answers.

First of all, thanks again for your help, and my apologies if you just 
don't have time to help newcomers.


I do get a lot of e-mails, so I may occasionally miss one.  If that 
happens, try again.  Or, ask on general.

I have many questions about the nightly build & snapshot process, how 
it names the results and where it places them. Every project in 
Jakarta seems to work in a slightly different way -- and JMeter most 
different of all. I also have questions on how the web site is 
generated and published (I'd like JMeter's to be generated from the 
xdocs instead of just pulled out from cvs/jakarta-jmeter/docs).


There are some general policies, and then each subproject in Jakarta is 
free to tailor them to their own needs.

The nightly build simply checks out jakarta-jmeter and builds the 
default target.   It is driven from the following project definition:

http://cvs.apache.org/viewcvs/jakarta-gump/project/jakarta-jmeter.xml

I am willing to upload to the jakarta web site anything that build 
produces, simply ask.

The way most jakarta projects work, as does jmeter, is that there is a 
"docs" target in the build that generates the docs directory from the 
xdocs sources. Simply build this and then commit the generated docs. 
Then somebody needs to go onto the daedalus.apache.org and execute a cvs 
update to get resynch the website with the cvs tree.  For a number of 
projects, I have a script that automatically does this four times a day, 
so this eliminates a step... all you need to do is build and commit. 
Jmeter is not currently in this script... but can be added upon request.

I've been checking the FAQ at 
http://www.apache.org/dev/committers.html#web, but it didn't help 
much. Either it's obsolete, or it doesn't apply to all jakarta projects.

Is there any documentation I could read to get better informed?


Most of the jakarta documentation is on jakarta.apache.org.  Try 
clicking on "gump" or "Website Maintenance".

- Sam Ruby





--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Help needed on JMeter nightly builds

[Jordi Salvat i Alabart]

Wow! I'm most amazed. It had never worked till the 2nd Jan. And then, 
suddently, it works from the 3rd onwards! Yes, *I* did a change to 
build.xml on the 2nd, but it was totally unrelated (different target).

Well, who knows. Anyway -- if it ain't broken, don't fix it :-)

Thanks a lot for your help!

Jordi.

Sam Ruby wrote:
Jordi Salvat i Alabart wrote:



JMeter nightly builds have been failing for a long while (long before 
I joined the project, actually). Noone in the project seems to know 
why: it builds OK everywhere else. I've tried e-mailing 
[EMAIL PROTECTED] to get access to Nagoya (where I believe the builds 
happen), but got no reply. I've e-mailed [EMAIL PROTECTED] for 
help (looked like the first logical step), but got no reply.


I'm not sure what you are seeing, but jmeter builds for me:

http://cvs.apache.org/builds/gump/2003-01-06/jakarta-jmeter.html
http://cvs.apache.org/builds/jakarta-jmeter/nightly/
http://gump.covalent.net/jars/2003-01-06/jakarta-jmeter/

Can you describe the problem you are seeing?

- Sam Ruby



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>






--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Help needed on JMeter nightly builds

[Sam Ruby]

Jordi Salvat i Alabart wrote:


JMeter nightly builds have been failing for a long while (long before I 
joined the project, actually). Noone in the project seems to know why: 
it builds OK everywhere else. I've tried e-mailing [EMAIL PROTECTED] to 
get access to Nagoya (where I believe the builds happen), but got no 
reply. I've e-mailed [EMAIL PROTECTED] for help (looked like the 
first logical step), but got no reply.

I'm not sure what you are seeing, but jmeter builds for me:

http://cvs.apache.org/builds/gump/2003-01-06/jakarta-jmeter.html
http://cvs.apache.org/builds/jakarta-jmeter/nightly/
http://gump.covalent.net/jars/2003-01-06/jakarta-jmeter/

Can you describe the problem you are seeing?

- Sam Ruby



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Help needed on JMeter nightly builds

[Jordi Salvat i Alabart]

Hi.

JMeter nightly builds have been failing for a long while (long before I 
joined the project, actually). Noone in the project seems to know why: 
it builds OK everywhere else. I've tried e-mailing [EMAIL PROTECTED] to 
get access to Nagoya (where I believe the builds happen), but got no 
reply. I've e-mailed [EMAIL PROTECTED] for help (looked like the 
first logical step), but got no reply.

I'm totally stuck on this matter. I need help. Any pointers welcome.

Thanks a lot,

Jordi


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Re: Broken nightly builds for some projects?

[otisg]

Thanks for the clarification.
Ok, I guess somebody will fix URLs on
http://jakarta.apache.org/site/binindex.html
then.

Otis

 On Fri, 15 Nov 2002, Sam Ruby
([EMAIL PROTECTED]) wrote:

> otisg wrote:
> > Ok, so it's a known problem that somebody is
> > working on, good :)
> > Do you have any estimate about how long it
> > will take to get nightly builds going again?
> 
> The nightly builds are going.  As I said,
the output has now been placed 
> at a new location.  In the case of lucene,
the output is at
> 
>
http://cvs.apache.org/builds/jakarta-lucene/nightly/
> 
> For more information, see
> 
>
http://marc.theaimsgroup.com/?l=jakarta-general&m=103694797821052&w=2
> 
> - Sam Ruby
> 
> 
> --
> To unsubscribe, e-mail:  
<mailto:general-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail:
<mailto:general-help@;jakarta.apache.org>
> 
> 
> 



Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag

--
To unsubscribe, e-mail:   <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>

Re: Broken nightly builds for some projects?

[Sam Ruby]

otisg wrote:

Ok, so it's a known problem that somebody is
working on, good :)
Do you have any estimate about how long it
will take to get nightly builds going again?


The nightly builds are going.  As I said, the output has now been placed 
at a new location.  In the case of lucene, the output is at

http://cvs.apache.org/builds/jakarta-lucene/nightly/

For more information, see

http://marc.theaimsgroup.com/?l=jakarta-general&m=103694797821052&w=2

- Sam Ruby


--
To unsubscribe, e-mail:   <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>

Re: Re: Broken nightly builds for some projects?

[otisg]

Ok, so it's a known problem that somebody is
working on, good :)
Do you have any estimate about how long it
will take to get nightly builds going again?
 I am asking because I have an article that
I will soon publish that has references to
some nightly builds, which is how I
discovered that they are not working.

Thanks,
Otis




 On Fri, 15 Nov 2002, Sam Ruby
([EMAIL PROTECTED]) wrote:

> otisg wrote:
> >  
> >
http://jakarta.apache.org/builds/jakarta-lucene/nightly/
> 
> I still have more clean up to do, but the
quick answer is that these 
> moved to cvs.apache.org.
> 
> - Sam Ruby
> 
> 
> --
> To unsubscribe, e-mail:  
<mailto:general-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail:
<mailto:general-help@;jakarta.apache.org>
> 
> 
> 



Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag

--
To unsubscribe, e-mail:   <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>

Re: Broken nightly builds for some projects?

[Sam Ruby]

otisg wrote:

 
http://jakarta.apache.org/builds/jakarta-lucene/nightly/

I still have more clean up to do, but the quick answer is that these 
moved to cvs.apache.org.

- Sam Ruby


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Broken nightly builds for some projects?

[otisg]

Hello,

Appologies if this is not the right list to
use for this, but what is with nightly
builds?  It looks like they are not working
for some projects, such as Lucene:
 
http://jakarta.apache.org/builds/jakarta-lucene/nightly/

There are some other projects with the same
problem, I noticed.

Who do I ask about getting this fixed?

Thank you,
Otis




Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag

--
To unsubscribe, e-mail:   <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>

RE: POI nightly builds and upcoming release howto

[Andrew C. Oliver]

In the mean time.. . can Marc (our build maestro) get karma to copy our
releases to the relevant server via ftp or whatever?

If not then does anyone object to us checking the whole file into a
subdirectory of our website in CVS so that it can be copied over?  We'll
follow this obviously less than perfect process until such time as the
technology to copy our files onto the server for download is developed. 
Thanks,

Andy

On Fri, 2002-03-01 at 18:48, Sam Ruby wrote:
> Scott Sanders wrote:
> >
> > I am happy to help with that, and I have even set my umask ;-)
> 
> I'm intrigued.  Do you have a logon to my machine that I don't know about?
> 
> ;-)
> 
> Actually, what I would like to do is to migrate from my hand crafted cron
> scripts to something that is generated from the project descriptors.  I'm
> also contemplating moving the hosting of these to either nagoya.apache.org
> or gump.covalent.net.
> 
> - Sam Ruby
> 
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org - port of Excel/Word/OLE 2 Compound Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: POI nightly builds and upcoming release howto

[Andrew C. Oliver]

On Fri, 2002-03-01 at 20:27, Scott Sanders wrote:
> I am happy to set up the daedalus release directory.
> 
> I have not cloned the real Sam Ruby in any way ;-)
> 

Starts singing "Will the real Sam Ruby..please stand up..."  *duck*

> Scott
> 
> > -Original Message-
> > From: Sam Ruby [mailto:[EMAIL PROTECTED]] 
> > Sent: Friday, March 01, 2002 3:48 PM
> > To: Jakarta General List
> > Subject: RE: POI nightly builds and upcoming release howto
> > 
> > 
> > Scott Sanders wrote:
> > >
> > > I am happy to help with that, and I have even set my umask ;-)
> > 
> > I'm intrigued.  Do you have a logon to my machine that I 
> > don't know about?
> > 
> > ;-)
> > 
> > Actually, what I would like to do is to migrate from my hand 
> > crafted cron scripts to something that is generated from the 
> > project descriptors.  I'm also contemplating moving the 
> > hosting of these to either nagoya.apache.org or gump.covalent.net.
> > 
> > - Sam Ruby
> > 
> > 
> > --
> > To unsubscribe, e-mail:   
> > <mailto:general-> [EMAIL PROTECTED]>
> > For 
> > additional commands, 
> > e-mail: <mailto:[EMAIL PROTECTED]>
> > 
> > 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org - port of Excel/Word/OLE 2 Compound Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: POI nightly builds and upcoming release howto

[Scott Sanders]

I am happy to set up the daedalus release directory.

I have not cloned the real Sam Ruby in any way ;-)

Scott

> -Original Message-
> From: Sam Ruby [mailto:[EMAIL PROTECTED]] 
> Sent: Friday, March 01, 2002 3:48 PM
> To: Jakarta General List
> Subject: RE: POI nightly builds and upcoming release howto
> 
> 
> Scott Sanders wrote:
> >
> > I am happy to help with that, and I have even set my umask ;-)
> 
> I'm intrigued.  Do you have a logon to my machine that I 
> don't know about?
> 
> ;-)
> 
> Actually, what I would like to do is to migrate from my hand 
> crafted cron scripts to something that is generated from the 
> project descriptors.  I'm also contemplating moving the 
> hosting of these to either nagoya.apache.org or gump.covalent.net.
> 
> - Sam Ruby
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:general-> [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: POI nightly builds and upcoming release howto

[Sam Ruby]

Scott Sanders wrote:
>
> I am happy to help with that, and I have even set my umask ;-)

I'm intrigued.  Do you have a logon to my machine that I don't know about?

;-)

Actually, what I would like to do is to migrate from my hand crafted cron
scripts to something that is generated from the project descriptors.  I'm
also contemplating moving the hosting of these to either nagoya.apache.org
or gump.covalent.net.

- Sam Ruby


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: POI nightly builds and upcoming release howto

[Andrew C. Oliver]

Oh great!  Thanks Scott!

-Andy

On Fri, 2002-03-01 at 17:53, Scott Sanders wrote:
> I am happy to help with that, and I have even set my umask ;-)
> 
> Scott
> 
> > -Original Message-
> > From: Peter Donald [mailto:[EMAIL PROTECTED]] 
> > Sent: Friday, March 01, 2002 2:30 PM
> > To: Jakarta General List
> > Subject: Re: POI nightly builds and upcoming release howto
> > 
> > 
> > On Sat, 2 Mar 2002 09:22, Andrew C. Oliver wrote:
> > > How do we get nightly builds/source releases happening and posting? 
> > > http://jakarta.apache.org/site/binindex.html
> > 
> > Ask Sam nicely to update his cron job to do that for you.
> > 
> > > Once we release how do we get the release put up: 
> > > http://jakarta.apache.org/site/binindex.html in the 
> > appropriate place.
> > 
> > Once you have signed the release, generated the HEADER.html 
> > to describe your 
> > release then you upload it all to the directory 
> > 
> > /www/jakarta.apache.org/builds/jakarta-poi/releases/1.5/
> > 
> > on jakarta.apache.org. If no one has permission 
> > to do that then 
> > you can ask for permission or get someone else to do it.
> > 
> > -- 
> > Cheers,
> > 
> > Pete
> > 
> > --
> > -
> > |  I thought there was a knob on the TV to turn up the 
> > intelligence.  |
> > |  There's a knob called "brightness", but it doesn't 
> > work.   |
> > --
> > -
> > 
> > --
> > To unsubscribe, e-mail:   
> > <mailto:general-> [EMAIL PROTECTED]>
> > For 
> > additional commands, 
> > e-mail: <mailto:[EMAIL PROTECTED]>
> > 
> > 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org - port of Excel/Word/OLE 2 Compound Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: POI nightly builds and upcoming release howto

[Andrew C. Oliver]

Great. Thanks Pete.

On Fri, 2002-03-01 at 17:29, Peter Donald wrote:
> On Sat, 2 Mar 2002 09:22, Andrew C. Oliver wrote:
> > How do we get nightly builds/source releases happening and posting?
> > http://jakarta.apache.org/site/binindex.html
> 
> Ask Sam nicely to update his cron job to do that for you.
> 
> > Once we release how do we get the release put up:
> > http://jakarta.apache.org/site/binindex.html in the appropriate place.
> 
> Once you have signed the release, generated the HEADER.html to describe your 
> release then you upload it all to the directory 
> 
> /www/jakarta.apache.org/builds/jakarta-poi/releases/1.5/
> 
> on jakarta.apache.org. If no one has permission to do that then 
> you can ask for permission or get someone else to do it.
> 
> -- 
> Cheers,
> 
> Pete
> 
> ---
> |  I thought there was a knob on the TV to turn up the intelligence.  |
> |  There's a knob called "brightness", but it doesn't work.   |
> ---
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org - port of Excel/Word/OLE 2 Compound Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: POI nightly builds and upcoming release howto

[Andrew C. Oliver]

:-)


On Fri, 2002-03-01 at 17:31, Peter Donald wrote:
> On Sat, 2 Mar 2002 09:29, Peter Donald wrote:
> > on jakarta.apache.org. If no one has permission to do that
> > then you can ask for permission or get someone else to do it.
> 
> Note to self. When writing Javadocs use HTML tags, when writing email - dont! 
> When swapping between two activities remember to kick your brain into action.
> 
> 
> -- 
> Cheers,
> 
> Pete
> 
> 
> Fools ignore complexity.  Pragmatists suffer it.
> Some can avoid it.  Geniuses remove it.
> -- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982
> 
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 
> 
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org - port of Excel/Word/OLE 2 Compound Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: POI nightly builds and upcoming release howto

[Scott Sanders]

I am happy to help with that, and I have even set my umask ;-)

Scott

> -Original Message-
> From: Peter Donald [mailto:[EMAIL PROTECTED]] 
> Sent: Friday, March 01, 2002 2:30 PM
> To: Jakarta General List
> Subject: Re: POI nightly builds and upcoming release howto
> 
> 
> On Sat, 2 Mar 2002 09:22, Andrew C. Oliver wrote:
> > How do we get nightly builds/source releases happening and posting? 
> > http://jakarta.apache.org/site/binindex.html
> 
> Ask Sam nicely to update his cron job to do that for you.
> 
> > Once we release how do we get the release put up: 
> > http://jakarta.apache.org/site/binindex.html in the 
> appropriate place.
> 
> Once you have signed the release, generated the HEADER.html 
> to describe your 
> release then you upload it all to the directory 
> 
> /www/jakarta.apache.org/builds/jakarta-poi/releases/1.5/
> 
> on jakarta.apache.org. If no one has permission 
> to do that then 
> you can ask for permission or get someone else to do it.
> 
> -- 
> Cheers,
> 
> Pete
> 
> --
> -
> |  I thought there was a knob on the TV to turn up the 
> intelligence.  |
> |  There's a knob called "brightness", but it doesn't 
> work.   |
> --
> -
> 
> --
> To unsubscribe, e-mail:   
> <mailto:general-> [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: POI nightly builds and upcoming release howto

[Peter Donald]

On Sat, 2 Mar 2002 09:29, Peter Donald wrote:
> on jakarta.apache.org. If no one has permission to do that
> then you can ask for permission or get someone else to do it.

Note to self. When writing Javadocs use HTML tags, when writing email - dont! 
When swapping between two activities remember to kick your brain into action.


-- 
Cheers,

Pete


Fools ignore complexity.  Pragmatists suffer it.
Some can avoid it.  Geniuses remove it.
-- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: POI nightly builds and upcoming release howto

[Peter Donald]

On Sat, 2 Mar 2002 09:22, Andrew C. Oliver wrote:
> How do we get nightly builds/source releases happening and posting?
> http://jakarta.apache.org/site/binindex.html

Ask Sam nicely to update his cron job to do that for you.

> Once we release how do we get the release put up:
> http://jakarta.apache.org/site/binindex.html in the appropriate place.

Once you have signed the release, generated the HEADER.html to describe your 
release then you upload it all to the directory 

/www/jakarta.apache.org/builds/jakarta-poi/releases/1.5/

on jakarta.apache.org. If no one has permission to do that then 
you can ask for permission or get someone else to do it.

-- 
Cheers,

Pete

---
|  I thought there was a knob on the TV to turn up the intelligence.  |
|  There's a knob called "brightness", but it doesn't work.   |
---

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

POI nightly builds and upcoming release howto

[Andrew C. Oliver]

Hi All,

Another question:

The POI committers have been
suckered^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H agreed to do an interim
production-level release (1.5) in the near future in order to reflect
the new packaging, capture a number of bug fixes and enhancements, etc
etc.  

How do we get nightly builds/source releases happening and posting?
http://jakarta.apache.org/site/binindex.html

Once we release how do we get the release put up:
http://jakarta.apache.org/site/binindex.html in the appropriate place.

We are building on GUMP but for some reason I don't see our builds up on
the site...?

Thanks,

Andy
-- 
http://www.superlinksoftware.com
http://jakarta.apache.org - port of Excel/Word/OLE 2 Compound Document 
format to java
http://developer.java.sun.com/developer/bugParade/bugs/4487555.html 
- fix java generics!
The avalanche has already started. It is too late for the pebbles to
vote.
-Ambassador Kosh


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: automated nightly builds

[Alef Arendsen]

There's a lot of possibilities. Personally I prefer using Ant in combination with 
cruisecontrol (by Martin Fowler, check out http://cruisecontrol.sourceforge.net). You 
might also check out http://jibe.sourceforge.net (the cvs can be found at 
http://www.sourceforge.net/projects/jibe), which uses cruisecontrol, ant and provides 
a lot of templates and stuff...

Ok, it is managed and created by me and is FAR FROM finished (but will be in the next 
two weeks).

Nightly builds are nice, but having a build when needed (so every hour or ten minutes 
even) lets you discover bugs way faster! With cruisecontrol this is possible (it 
checks the CVS every X minutes) and has a nice web interface...

I suggest: start out with cruisecontrol!

Alef Arendsen

-Original Message-
From: fabio [mailto:[EMAIL PROTECTED]]
Sent: Friday, 01 March 2002 15:18
To: Jakarta General List
Subject: Re: automated nightly builds


Please send to the list (or at least to me too :).

Thanks.

Fabio.

Danny Angus wrote:

> Hi,
> I was wondering how (if?) other projects (than james) manage automated
> nightly builds. I have a server that could do the checkout,building and
> upload.
>
> Does anyone have a shell script, ant script, or cron job I could rip-off?
> d.
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
Fabio Mengue - Centro de Computacao - Unicamp
[EMAIL PROTECTED]   [EMAIL PROTECTED]
Vacum ad brejus mobilet




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: automated nightly builds

[fabio]

Please send to the list (or at least to me too :).

Thanks.

Fabio.

Danny Angus wrote:

> Hi,
> I was wondering how (if?) other projects (than james) manage automated
> nightly builds. I have a server that could do the checkout,building and
> upload.
>
> Does anyone have a shell script, ant script, or cron job I could rip-off?
> d.
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
Fabio Mengue - Centro de Computacao - Unicamp
[EMAIL PROTECTED]   [EMAIL PROTECTED]
Vacum ad brejus mobilet




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: automated nightly builds

[Pier Fumagalli]

"Danny Angus" <[EMAIL PROTECTED]> wrote:

> Hi,
> I was wondering how (if?) other projects (than james) manage automated
> nightly builds. I have a server that could do the checkout,building and
> upload.
> 
> Does anyone have a shell script, ant script, or cron job I could rip-off?
> d.

Everything (everyting) is already build on Nagoya (and several other places)
by "GUMP" several times a day Sam??? :)

Pier


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

automated nightly builds

[Danny Angus]

Hi,
I was wondering how (if?) other projects (than james) manage automated
nightly builds. I have a server that could do the checkout,building and
upload.

Does anyone have a shell script, ant script, or cron job I could rip-off?
d.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Nightly Builds for jetspeed

[Paul Spencer]

Sam,
Would you add Jetspeed the the list of projects you post nightly.  The
ant target is release_binary.

Thank you,
Paul Spencer

Sam Ruby wrote:
> 
> Paul Spencer wrote:
> >
> > I would like to generate nightly build for the Jetspeed project.  What
> > do I need to do to accomplish this task.
> 
> Pretty much just, cron + cvs update + ant.  You can post the results using
> "scp".
> 
> I'm building jetspeed anyway nightly, and post the results for many
> projects.  Would you like me to add jetspeed to my list?  If so, release or
> release_binary?
> 
> - Sam Ruby
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly Builds for jetspeed

[Sam Ruby]

Paul Spencer wrote:
>
> I would like to generate nightly build for the Jetspeed project.  What
> do I need to do to accomplish this task.

Pretty much just, cron + cvs update + ant.  You can post the results using
"scp".

I'm building jetspeed anyway nightly, and post the results for many
projects.  Would you like me to add jetspeed to my list?  If so, release or
release_binary?

- Sam Ruby


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Nightly Builds for jetspeed

[Paul Spencer]

I would like to generate nightly build for the Jetspeed project.  What
do I need to do to accomplish this task.

Paul Spencer
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [NOTICE] + [PROPOSAL] nightly builds + nightly source checkouts

[Sam Ruby]

Craig R. McClanahan wrote:
>
> IMHO Gump serves a different, also valid, purpose as a tinderbox
> detector of incompatibilities.
>
> The goal of nightly builds is different -- it is to create something
> that ought to be marginally usable.  For that reason, a nightly build
> would use a stable Ant (for example), instead of hot-off-the-CVS code
> that Gump uses.

I have always done all of my development with the absolute latest Ant.  The
results have always been more than just marginally useful.

Now that other people are watching this too, this will become self
re-inforcing.  I am now building and posting a number of builds - all using
the latest versions of their dependencies.  I think that we are only a few
weeks away from the point whereby most Gump runs will be absolutely clean,
and a month or too from the point where people will actually expect it to
be clean.

If somebody wants me to, I'll gladly post *EVERY* subproject.

Alternatively, if somebody has a better idea, I'll gladly stop posting (but
continue building).

> That being said, it might well be possible to tweak the Gump scripts
> so that they operate in a different mode for nightly builds.  Sam?

Gump runs scripts.  The scripts can be set up to point to stable versions.

- Sam Ruby


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [NOTICE] + [PROPOSAL] nightly builds + nightly source checkouts

[Steve Downey]

> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 13, 2001 9:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [NOTICE] + [PROPOSAL] nightly builds + nightly source
> checkouts
> 

> 
> We will want each subproject to maintain their own versions
> (e.g. tomcat-4.0-source.sh and tomcat-4.0-build.sh) according to the
> standard conventions, so that no one person would need to 
> stay up to date
> on all the subproject build procedures.
> 
> We will also want a few things like stable releases of Ant, 
> XML parsers,
> etc. installed in "well known" places for build processes that require
> access to them.
> 

Documenting this would be wonderfull. A few less often build pieces, like
tester underneath tomcat-4, have some environment issues, eg, tester is
'happiest' if xereces is in ../../xerces-1_3_0. 

This was more of a problem when everything built in ../build and ../dist.
Now we have the opposite problem of having to copy from build/ and dist/ to
the shared runtime environment. But that's a different rant.

-SMD
<><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission
may contain confidential information and is intended only for the person(s)
named.  Any use, copying or disclosure by any other person is strictly
prohibited.  If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [NOTICE] + [PROPOSAL] nightly builds + nightly source checkouts

[Jeff Martin]

>
>IMHO Gump serves a different, also valid, purpose as a tinderbox detector
>of incompatibilities.
>
>The goal of nightly builds is different -- it is to create something that
>ought to be marginally usable.  For that reason, a nightly build would use
>a stable Ant (for example), instead of hot-off-the-CVS code that Gump
>uses.
>
>That being said, it might well be possible to tweak the Gump scripts so
>that they operate in a different mode for nightly builds.  Sam?
>


Gump probably can be tweaked to do this. The other option is Alexandria
which supports Ant builds, but as yet doesn't really support tinderbox.
http://staff.synamic.co.uk/~jmartin/ Currently only setup to build
Alexandria and Ant but builds docs for everything else (well most things)

>> Comments?
>>
>> -jon
>>
>
>Craig McClanahan
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [NOTICE] + [PROPOSAL] nightly builds + nightly source checkouts

[Craig R. McClanahan]

On Tue, 13 Mar 2001, Jon Stevens wrote:

> Hey all,
> 
> 
> [NOTICE]
> Brian asked me to remind you to clean up the nightly builds so that we don't
> have tons of old stuff eating up disk space.
> 
> Example:
> /x2/www/jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly
> 
> jakarta-tomcat-4.0/nightly > du -sk
> 424790  .
> 
> 424790 megs seems like a lot to me.
> 

Will be restarting my "clean out" job shortly.

> There are files all the way back to 20010216 which seems a bit excessive.
> Also excessive seems to be the .Z and .gz versions. I think it is safe to
> assume in this day and age that everyone can install gunzip on their server.
> 
> 
> [PROPOSAL]
> I would like to finagle this email into another discussion as well which is
> coming up with a more centralized system for doing nightly builds as well as
> nightly source checkouts.
> 

+1, but see further discussion below on the details

> Right now, we have cronjobs run by a number of different people putting
> files in a number of different locations. It would be nice to try to
> centralize this down to just one primary script and one configuration file
> that handles this the majority of this stuff.
> 
> So, in the builds directory, I would like to propose setting something up
> that looks like this:
> 
> /www/jakarta.apache.org
> builds/
> scripts/
> build-all.sh (or .pl or .py)
> cleanup-all.sh (or .pl or .py)
> build.conf
> projects/
> velocity-source.sh (or .pl or .py)
> velocity-build.sh (or .pl or .py)
> tomcat-4.0-source.sh (or .pl or .py)
> tomcat-4.0-build.sh (or .pl or .py)
> ...
> ...
> 
> build.conf:
> baseDirectory=/www/jakarta.apache.org/builds
> projectsDirectory=$baseDirectory/projects
> daysToKeep=7
> 
> We could then have the build-all script run through the projects directory
> looking for scripts to execute. It would first attempt to execute all of the
> "*source*" scripts it finds and then attempt to execute all of the "*build*"
> scripts it finds. What this would allow is for projects to have their own
> scripts to be run in order to do any source/build specific things for their
> projects. It would also allow for individual testing. Adding a new project
> is as simple as adding another set of scripts.
> 

We will want each subproject to maintain their own versions
(e.g. tomcat-4.0-source.sh and tomcat-4.0-build.sh) according to the
standard conventions, so that no one person would need to stay up to date
on all the subproject build procedures.

We will also want a few things like stable releases of Ant, XML parsers,
etc. installed in "well known" places for build processes that require
access to them.

> The individual scripts could set what their "output" directory is based on
> the projectsDirectory + projectName. projectsDirectory would be passed in to
> the source/build scripts on ARGV[0].
> 
> The cleanup-all.sh script would be a global cleanup script that would run at
> the end of the build-all.sh script to prune the files in the directories,
> keeping the "daysToKeep" number of files.
> 
> I know that I have most of the framework already done for the
> "project-build.sh" scripts and the "cleanup-all.sh" scripts, but I don't
> have the frameworks for the build scripts, however, I know that some
> projects already have that. Maybe we could consolidate those into this
> system?
> 
> Notes: In order to put a system like this into place, we will also need to
> have everyone shut off their existing cronjobs. :-)
> 

+1 for me (who does Servletapi, Tomcat 4.0, Struts, Watchdog), as soon as
it is ready.

> Sam, I'm sure that this probably fits into Gump somewhere as well, however,
> I'm not sure I want to or feel the need to go that far and come up with the
> "perfect" solution at this point. What do you feel about that?
> 

IMHO Gump serves a different, also valid, purpose as a tinderbox detector
of incompatibilities.

The goal of nightly builds is different -- it is to create something that
ought to be marginally usable.  For that reason, a nightly build would use
a stable Ant (for example), instead of hot-off-the-CVS code that Gump
uses.

That being said, it might well be possible to tweak the Gump scripts so
that they operate in a different mode for nightly builds.  Sam?

> Comments?
> 
> -jon
> 

Craig McClanahan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[NOTICE] + [PROPOSAL] nightly builds + nightly source checkouts

[Jon Stevens]

Hey all,


[NOTICE]
Brian asked me to remind you to clean up the nightly builds so that we don't
have tons of old stuff eating up disk space.

Example:
/x2/www/jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly

jakarta-tomcat-4.0/nightly > du -sk
424790  .

424790 megs seems like a lot to me.

There are files all the way back to 20010216 which seems a bit excessive.
Also excessive seems to be the .Z and .gz versions. I think it is safe to
assume in this day and age that everyone can install gunzip on their server.


[PROPOSAL]
I would like to finagle this email into another discussion as well which is
coming up with a more centralized system for doing nightly builds as well as
nightly source checkouts.

Right now, we have cronjobs run by a number of different people putting
files in a number of different locations. It would be nice to try to
centralize this down to just one primary script and one configuration file
that handles this the majority of this stuff.

So, in the builds directory, I would like to propose setting something up
that looks like this:

/www/jakarta.apache.org
builds/
scripts/
build-all.sh (or .pl or .py)
cleanup-all.sh (or .pl or .py)
build.conf
projects/
velocity-source.sh (or .pl or .py)
velocity-build.sh (or .pl or .py)
tomcat-4.0-source.sh (or .pl or .py)
tomcat-4.0-build.sh (or .pl or .py)
...
...

build.conf:
baseDirectory=/www/jakarta.apache.org/builds
projectsDirectory=$baseDirectory/projects
daysToKeep=7

We could then have the build-all script run through the projects directory
looking for scripts to execute. It would first attempt to execute all of the
"*source*" scripts it finds and then attempt to execute all of the "*build*"
scripts it finds. What this would allow is for projects to have their own
scripts to be run in order to do any source/build specific things for their
projects. It would also allow for individual testing. Adding a new project
is as simple as adding another set of scripts.

The individual scripts could set what their "output" directory is based on
the projectsDirectory + projectName. projectsDirectory would be passed in to
the source/build scripts on ARGV[0].

The cleanup-all.sh script would be a global cleanup script that would run at
the end of the build-all.sh script to prune the files in the directories,
keeping the "daysToKeep" number of files.

I know that I have most of the framework already done for the
"project-build.sh" scripts and the "cleanup-all.sh" scripts, but I don't
have the frameworks for the build scripts, however, I know that some
projects already have that. Maybe we could consolidate those into this
system?

Notes: In order to put a system like this into place, we will also need to
have everyone shut off their existing cronjobs. :-)

Sam, I'm sure that this probably fits into Gump somewhere as well, however,
I'm not sure I want to or feel the need to go that far and come up with the
"perfect" solution at this point. What do you feel about that?

Comments?

-jon


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Nightly builds

[Jeff Martin]

Little history,
about 6 months ago I added build support to Alexandria. It seemed to
make sense that since I wanted to test build and Alexandria already had a
means getting hold of the source from cvs without to much hassle it seemed
good to just added in the ability to kick off a build.xml file is there was
one.

This mean where I work we have a hourly process that checks out all the code
and builds it (also runs JUnit tests) and produces a nice html page with
shows any build errors in red. This works pretty well, what it doesn't
provide is confirmation that any interproject dependencies are not being
broken buy code which is in development, this is important information for
some people but distracting for others who what information on how their
changes are affecting their code not how other peoples affect their code.

Enter Sam and Gump,
at the same time Sam was working on Gump which allows him to see
where dependencies between development version of projects. A good example
of how this is useful is the relationship between Alexandria and Castor
thanks to Gump Sam was able to identify a change in the behavior of Castor
which made is slightly stricter in the way it processed xsd files. This
meant one of the files in Alexandria was failing to build properly, because
we had warning of this prior to the release of the next version of Castor
Sam was able to fix the problem (Cheers for that Sam, I was a bit slow on
the uptake there). Brilliant we've caught and fixed a problem before it even
occurred.

Today,
I'm looking at how to integrate the sets of code Gump and Alexandria
part of this is making sure that both styles of build (checks against
release and dev code) are supported and it is easy to have both type running
at the same time. The other side of this is to look at the differing ways in
which the actual build is handled. Alexandria used to be based around bash,
but it became clear that Using Ant throughout the process was a better way
to handle things. I personally would like to see Gump go the same way, but I
don't want to through out the baby with the bath water so we're not just
going to abandon Gump as it stands at the moment.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 15 February 2001 20:07
To: [EMAIL PROTECTED]
Subject: Re: Nightly builds


Hi Sam,

I (think ) I got gump to work, it's not updating/building. There are few 
issues/sugestions. I tried to find the alexandria list ( I assume the
discussion on gump happens on alexandria ), I'm sure it is somewhere and
I'll keep searching :-)

Anyway - it would be possible to switch tomcat3.x nightly builds to use
gump, with few small changes in the project definition. 

The main issue is that (IMHO) you should relax a bit the
dependencies: a number of projects had  releases, and I think other
projects should depend on the (stable) release of those projects.

For example, tomcat, servletapi, etc should depend on released-ant-1.2,
not jakarta-ant, etc. 


Whenever a project has a major release - we should of course update the
scripts to make all projects depend on the latest "stable" and fix all
projects that are in development mode to match the latest "stable".

Given that each project has independent release cycle, I don't think it's
normal for a stable release of a project to depend on a development
release of another project ( for example, tomcat 3.3 shouldn't depend on
the dev. release of ant - but on the latest "stable" ant. If ant1.3 will 
be released before 3.3 is "frozen", then tomcat3.3 should be fixed to
make sure it works with ant 1.3 - if not, it should stay dependent on
the released ant 1.2 ).

This can be resolved by adding "project/released-ant-12.xml", etc.

Another issue - wouldn't be better to generate build.xml instead of
build.sh and build.bat ? Most of the code inside build.sh can be done
easily in a "super" build.xml that calls ant. It is even possible to
use  tags to start different VMs. 

I think this would be easier to maintain and enhance.

Another think - one planned feature for tc3.x build was a mechanism to
triger a build from a web page ( so if someone does a change, he doesn't
have to wait until the next night to find out if it brakes something ). 
My plan was to use the  taglib ( that is also used to run the tests
from a web page ) and write a simple build.war that will allow runs of 
the build from the web. 
That would also allow a lot of simplification ( since wars are
self contained and have a stable environment/structure ). It would also
modularize a bit the build ( a page to update a repository, a page to
build, no more "echo \", etc )

Finally: it would be nice if the build scripts would get the sources using
 instead of . 


Costin


--

Re: Nightly builds

[cmanolache]

> Others can run builds with stable dependencies.  They are permitted, and
> even encouraged to do so using Gump.  The runs I have been making are to
> determine the impact of changes - something that I think that has not
> received enough attention, and so that's why I have been and will continue
> to focus the runs that I make on that.

That's a valid configuration, I'm not saying to drop it - I just want to
be sure that both "styles" are supported. My interest is in using gump for
tomcat3.x builds - maintaining the scripts for testing is enough effort,
if I can use gump for building I'll save time.

The tomcat nightly should include the latest tomcat and the stable
dependencies - whenever it'll be released, it can't depend on the
"latest" ant but on the "latest release".

> Since you gave the specific example of ant, I do not like the idea of
> ant-1.3 being released without some assessment of the impact of changes on
> other projects.  There was a change that would have gone into 1.3 that

True - I will probably start using/testing ant-1.3, since it'll probably
be released before tc3.3.

> Given the number of projects we have here, each project binding too closely
> to exactly one version of each of their prereqs means that someone who
> desires to compose a system out of these components is likely to run into

Assuming an change happens in ant-1.3 ( or ant-1.4 or 2.0 ), should
tomcat/xalan/etc  be updated to use the latest ant  or the stable ant ?

Yes, in theory all API/DTD changes should be backward compatible - but in
reality we are talking about projects that are in development mode, not
about "standard" APIs. And if a project has a dependency on another
project, it is expected to track the changes ( and we did changed the
build.xml several times already ), but with certain granularity.
 
IMHO relaxing the requirement to "latest released version" is a very good
idea. Maybe when a project enters "feature freeze" or "beta" we can update
the builds and make sure all other projects work with the freezed
APIs/DTDs, and roll back/fix what is broken. 


> problems.  So, in fact, I would be greatly pleased if there were multiple
> nightly builds going on out there with different combinations.  And

A tomcat3.x nightly build will happen soon.


> Making ant build.xml files as a target of gump would be a valuable
> addition.  It has been often discussed, but never contributed.
 
> Getting using http as an alternative to cvs would also make a great
> addition.

My time is as limited as anyone else, but I'll try to do at least (1).
( if you remember the nightly builds of tomcat used to be ant-based 
and used to use get, so most of the code is there, it just need to be
geenralized to gump )

> P.S.  What does it mean to have gump "working", but not
> "updating/building"?

It means: spell error, I meant "is no_w_ updating" (instead of "not").

Costin




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds

[Sam Ruby]

Copying alexandria-dev.

Others can run builds with stable dependencies.  They are permitted, and
even encouraged to do so using Gump.  The runs I have been making are to
determine the impact of changes - something that I think that has not
received enough attention, and so that's why I have been and will continue
to focus the runs that I make on that.

Since you gave the specific example of ant, I do not like the idea of
ant-1.3 being released without some assessment of the impact of changes on
other projects.  There was a change that would have gone into 1.3 that
would have caused xerces and xalan packaging builds to fail, this was
changed to a way that would still cause it to fail, but in order to change
it to make is succeed would have required developers to step up to 1.3, and
finally, a change was made that did not require any changes.

Given the number of projects we have here, each project binding too closely
to exactly one version of each of their prereqs means that someone who
desires to compose a system out of these components is likely to run into
problems.  So, in fact, I would be greatly pleased if there were multiple
nightly builds going on out there with different combinations.  And
alexandria can certainly house the various project definitions required,
and

Making ant build.xml files as a target of gump would be a valuable
addition.  It has been often discussed, but never contributed.

Getting using http as an alternative to cvs would also make a great
addition.

- Sam Ruby

P.S.  What does it mean to have gump "working", but not
"updating/building"?

-- Forwarded by Sam Ruby/Raleigh/IBM on 02/15/2001
03:18 PM ---

[EMAIL PROTECTED] on 02/15/2001 03:07:04 PM

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: Nightly builds



Hi Sam,

I (think ) I got gump to work, it's not updating/building. There are few
issues/sugestions. I tried to find the alexandria list ( I assume the
discussion on gump happens on alexandria ), I'm sure it is somewhere and
I'll keep searching :-)

Anyway - it would be possible to switch tomcat3.x nightly builds to use
gump, with few small changes in the project definition.

The main issue is that (IMHO) you should relax a bit the
dependencies: a number of projects had  releases, and I think other
projects should depend on the (stable) release of those projects.

For example, tomcat, servletapi, etc should depend on released-ant-1.2,
not jakarta-ant, etc.


Whenever a project has a major release - we should of course update the
scripts to make all projects depend on the latest "stable" and fix all
projects that are in development mode to match the latest "stable".

Given that each project has independent release cycle, I don't think it's
normal for a stable release of a project to depend on a development
release of another project ( for example, tomcat 3.3 shouldn't depend on
the dev. release of ant - but on the latest "stable" ant. If ant1.3 will
be released before 3.3 is "frozen", then tomcat3.3 should be fixed to
make sure it works with ant 1.3 - if not, it should stay dependent on
the released ant 1.2 ).

This can be resolved by adding "project/released-ant-12.xml", etc.

Another issue - wouldn't be better to generate build.xml instead of
build.sh and build.bat ? Most of the code inside build.sh can be done
easily in a "super" build.xml that calls ant. It is even possible to
use  tags to start different VMs.

I think this would be easier to maintain and enhance.

Another think - one planned feature for tc3.x build was a mechanism to
triger a build from a web page ( so if someone does a change, he doesn't
have to wait until the next night to find out if it brakes something ).
My plan was to use the  taglib ( that is also used to run the tests
from a web page ) and write a simple build.war that will allow runs of
the build from the web.
That would also allow a lot of simplification ( since wars are
self contained and have a stable environment/structure ). It would also
modularize a bit the build ( a page to update a repository, a page to
build, no more "echo \", etc )

Finally: it would be nice if the build scripts would get the sources using
 instead of .


Costin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds

[cmanolache]

Hi Sam,

I (think ) I got gump to work, it's not updating/building. There are few 
issues/sugestions. I tried to find the alexandria list ( I assume the
discussion on gump happens on alexandria ), I'm sure it is somewhere and
I'll keep searching :-)

Anyway - it would be possible to switch tomcat3.x nightly builds to use
gump, with few small changes in the project definition. 

The main issue is that (IMHO) you should relax a bit the
dependencies: a number of projects had  releases, and I think other
projects should depend on the (stable) release of those projects.

For example, tomcat, servletapi, etc should depend on released-ant-1.2,
not jakarta-ant, etc. 


Whenever a project has a major release - we should of course update the
scripts to make all projects depend on the latest "stable" and fix all
projects that are in development mode to match the latest "stable".

Given that each project has independent release cycle, I don't think it's
normal for a stable release of a project to depend on a development
release of another project ( for example, tomcat 3.3 shouldn't depend on
the dev. release of ant - but on the latest "stable" ant. If ant1.3 will 
be released before 3.3 is "frozen", then tomcat3.3 should be fixed to
make sure it works with ant 1.3 - if not, it should stay dependent on
the released ant 1.2 ).

This can be resolved by adding "project/released-ant-12.xml", etc.

Another issue - wouldn't be better to generate build.xml instead of
build.sh and build.bat ? Most of the code inside build.sh can be done
easily in a "super" build.xml that calls ant. It is even possible to
use  tags to start different VMs. 

I think this would be easier to maintain and enhance.

Another think - one planned feature for tc3.x build was a mechanism to
triger a build from a web page ( so if someone does a change, he doesn't
have to wait until the next night to find out if it brakes something ). 
My plan was to use the  taglib ( that is also used to run the tests
from a web page ) and write a simple build.war that will allow runs of 
the build from the web. 
That would also allow a lot of simplification ( since wars are
self contained and have a stable environment/structure ). It would also
modularize a bit the build ( a page to update a repository, a page to
build, no more "echo \", etc )

Finally: it would be nice if the build scripts would get the sources using
 instead of . 


Costin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds

[Sam Ruby]

Costin Manolache wrote:
>
> Sam - I would be willing to bet on Gump for doing the
> "normal" nightly for Tomcat 3.2 and 3.3.

I'm not "pushing" anybody to Gump.  Call it a "pull" model if you like...
;-)

>  - builds on multiple VMs ( i.e. JDK1.1 and Java2 )

The ability to switch JVMs was a design point for Gump.  Currently
unimplemented, but not difficult.

> - builds with multiple classpaths ( i.e. with and without JSSE )

No problem.

> My biggest concern - my current experience is that
> nightly builds are very tricky, and require a lot
> of attention. I can (kind-of) spend the time and
> fix my scripts when they brake ( since they are
> simple enough for me to manage ), but I'm a bit
> scared of a more complex system.

Gump is modular.  The individual "script" for tomcat can be found at:

http://jakarta.apache.org/builds/gump/2001-02-13/source_jakarta-tomcat.html

You can click on the links to see how dependent projects are defined.

The actual, platform dependent, script is generated from that definition.

The nice thing about gump is that the results are posted for all to see.
This makes it easy to debug.  I also do experiments on my ThinkPad, and
leave the official builds to a Linux box.

> There are 2 choices for scp: you either pull the binaries
> from the build machine or you push them.

Getting this right has proven to be tricky for me.  Ant builds were down
for weeks (perhaps even months) in the locus=>daedalus migration.

- Sam Ruby


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds

[cmanolache]

> > a project (jakarta) wide system, or is each project
> > responsible to make the nightly build and transfer the
> > results to /www/jakarta.apache.org/builds/{projectname}/nightly/
> 
> Craig does many, Costin does a few more, I currently do Ant, Jason van Zyl
> does velocity...
> 
> I'd be glad to post what Gump builds nightly, but as the saying goes "Life
> is like a box of chocolates..."  ;-)

Sam - I would be willing to bet on Gump for doing the "normal" nightly for
Tomcat 3.2 and 3.3.

The only problem is that we need some extra features ( I can help
integrate them in Gump if you want - but for now I'll just run them in
the old way ):

- builds on multiple VMs ( i.e. JDK1.1 and Java2 )
- builds with multiple classpaths ( i.e. with and without JSSE )

Another thing is the nightly run of watchdog and sanity - but I can do
some tricks in build.xml so the tests can be part of the build ( and trick
Gump who'll believe it's just doing a build :-)

My biggest concern - my current experience is that nightly builds are very
tricky, and require a lot of attention. I can (kind-of) spend the time and
fix my scripts when they brake ( since they are simple enough for me to
manage ), but I'm a bit scared of a more complex system.


---

Regarding the upload of the binaries on jakarta.apache.org:

There are 2 choices for scp: you either pull the binaries from the 
build machine or you push them.

The only way to push is by using scp. In order for that to work you need
to authorize login from the build machine into jakarta ( using
"authorized_keys" ). That's a bit dangerous ( since a pottential intruder
on the build machine might get access to jakarta ).

I would strongly recomend a "pull" method, where you use a cron script to
get the binaries from the build machine.  You can either use scp ( and
accept that jakarta is more secure than the build machine ) or htget.
The later will require you to place the binaries in a public place,
accessible via http or ftp.

In general, the build machine should be "untrusted" - it'll be used to run
complex scripts ( ant can run shell, test scripts, etc ) - i.e. code that
may be insecure. Don't keep it inside your firewall, don't store sensitive
information on it :-)


-- 
Costin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds

[Sam Ruby]

Ceki Gülcü wrote:
>
> While we are at it, who does the nightly builds? Is there
> a project (jakarta) wide system, or is each project
> responsible to make the nightly build and transfer the
> results to /www/jakarta.apache.org/builds/{projectname}/nightly/

Craig does many, Costin does a few more, I currently do Ant, Jason van Zyl
does velocity...

I'd be glad to post what Gump builds nightly, but as the saying goes "Life
is like a box of chocolates..."  ;-)

- Sam Ruby


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds

[Ceki Gülcü]

While we are at it, who does the nightly builds? Is there a project (jakarta) wide 
system, or is each project responsible to make the nightly build and transfer the 
results to  /www/jakarta.apache.org/builds/{projectname}/nightly/

Thanks, Ceki

At 09:04 13.02.2001 -0800, you wrote:
>Charles Benett wrote:
>
>> Hi!
>>
>> What's the procedure for making nightly, milestone and release builds of
>> jakart-james available on the binary and source build pages?
>>
>> Thanks
>>
>
>There are three basic tasks needed:
>
>* Upload the appropriate files to our server,
>  using "scp" or some equivalent file transfer
>  protocol.  The typical place for such files is
>  a hierarchy under:
>
>/www/jakarta.apache.org/builds/{project-name}/
>
>* Modify the links on your subproject home page
>  as desired to point at these download directories.
>
>* Update the Jakarta web site pages that point at
>  the downloads, by checking out the "jakarta-site2"
>  CVS module and following the instructions in the
>  README file (top level directory).
>
>I can assist (offline) if you have any questions along the way.
>
>>
>> Charles
>>
>
>Craig McClanahan
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]


Ceki Gülcü   e-mail: [EMAIL PROTECTED] (preferred)
av. de Rumine 5  [EMAIL PROTECTED]
CH-1005 Lausanne  
SwitzerlandTel: ++41 21 351 23 15


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds

[Craig R. McClanahan]

Charles Benett wrote:

> Hi!
>
> What's the procedure for making nightly, milestone and release builds of
> jakart-james available on the binary and source build pages?
>
> Thanks
>

There are three basic tasks needed:

* Upload the appropriate files to our server,
  using "scp" or some equivalent file transfer
  protocol.  The typical place for such files is
  a hierarchy under:

/www/jakarta.apache.org/builds/{project-name}/

* Modify the links on your subproject home page
  as desired to point at these download directories.

* Update the Jakarta web site pages that point at
  the downloads, by checking out the "jakarta-site2"
  CVS module and following the instructions in the
  README file (top level directory).

I can assist (offline) if you have any questions along the way.

>
> Charles
>

Craig McClanahan



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nightly builds

[Sam Ruby]

Charles Benett wrote:
>
> What's the procedure for making nightly, milestone and release
> builds of jakart-james available on the binary and source build
> pages?

Copy them to daedalus.apache.org:/www/jakarta.apache.org/builds.  You will
need to be familiar with ssh and scp.

Then either update jakarta-site2, and either send patches or request karma.

I'd be willing to take care of the nightly builds, but I have one
constraint: mine are built using Gump.  ;-)

- Sam Ruby


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Nightly builds

[Charles Benett]

Hi!

What's the procedure for making nightly, milestone and release builds of
jakart-james available on the binary and source build pages?

Thanks

Charles

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]