river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Hurley <Jim.Hur...@Sun.COM>
Subject Re: building an AR1 release candidate...
Date Tue, 06 Nov 2007 16:27:33 GMT
On Nov 5, 2007, at 5:55 PM, Frank Barnaby wrote:
> With regard to the official release-candidate builds, Continuum
> currently builds the project without the zip bundles.  It would be
> useful if (1) the continuum build-definition could be configured to
> build everything (including zip bundles) on its current schedule,
> or (2) an additional build-definition could be created to provide
> a separate process so that we can manually start an official
> candidate build (with zip bundles) when appropriate.
> There might be some benefit to the continuous build with zip bundles
> (option-1), which would provide the latest distribution to folks who
> want to use the latest build without having to download sources and
> build it on their own.
> Of course, both options only make sense if Continuum provides an
> archive area to provide access to the resulting zip bundles.  Do any
> of you understand Continuum enough to provide an answer?
> Frank

Hi Frank-

Per Phil's email below...  he did the original setup of our Continuum  
but it seems we need a set of people to take this over and make the  
you're discovering.  It seems you and Nigel are setup with  
permissions now
to do changes.  Any other committers interested in getting involved  
in this?

Does anyone know the answer to Frank's question above (does
Continuum provide an archive area to provide access to the resulting
zip bundles)?

thanks -Jim

Begin forwarded message:
> From: Phil Steitz <phil.steitz@gmail.com>
> Date: August 19, 2007 1:02:14 PM EDT
> To: river-dev@incubator.apache.org
> Subject: Re: Apache hardware (Was: How to start from here?)
> Using these instructions and a little hacking, I got the jstk build
> working on the Continuum instance on vmbuild1.apache.org.  To
> workaround the prebuilt-outrigger-logstore.jar dependency, I created a
> "fakeJini" directory in my home there including just a /lib directory
> including that jar and set JINI_HOME to point there.  Other than this
> hack, everything works directly out of svn.  We should fix the
> build_common.xml to eliminate that external dependency and then drop
> the "Jini" installation from the "River" profile.  The build is now
> set up to run under JDK 1.5 and executes "clean", then "all" and
> "jars".  If 1.6 or something else is preferred, let me know and I can
> change that.
> For now, the build is set up to run on the default schedule, which (I
> think) is hourly, but it will not run unless there are changes to svn.
>  Notifications (only on failure or error) are set to come to this
> list.
> Currently, Nigel and Frank are set up with permissions to modify the
> River build group.  Other committers who want to work on the CI build
> should register at http://vmbuild1.apache.org and then let one of us
> know so we can add you to the River group.  Right now, I think I am
> the only one who can add environment variable definitions (what
> Continuum calls "Profiles" made up of "Installations"), but any group
> member can add a build using one of the existing profiles.
> Phil

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message