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
On 1/16/07, 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.
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
Henri Yandell wrote:
> On 1/16/07, 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.
>
> 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
Umm....why not out of Gump?
Phil Steitz wrote:
> Henri Yandell wrote:
>
>> On 1/16/07, 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.
>>>
>> 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: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
>
>
--
No PST Files Ever Again
Buni Meldware Communication Suite
Email, Calendaring, ease of configuration/administration
http://buni.org
Andrew C. Oliver wrote:
> Umm....why 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?
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:
> Umm....why not out of Gump?
>
> Phil Steitz wrote:
>> Henri Yandell wrote:
>>
>>> On 1/16/07, 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.
>>>>
>>> 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: general-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: general-help@jakarta.apache.org
>>
>>
>>
>>
>
>
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:
>> Umm....why not out of Gump?
>>
>> Phil Steitz wrote:
>>> Henri Yandell wrote:
>>>
>>>> On 1/16/07, 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.
>>>>>
>>>> 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: general-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: general-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>
>
> ------------------------------------------------------------ ---------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
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
> 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 i=
n 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:
> >> Umm....why not out of Gump?
> >>
> >> Phil Steitz wrote:
> >>> Henri Yandell wrote:
> >>>
> >>>> On 1/16/07, 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.
> >>>>>
> >>>> 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 Common=
s
> >>>> 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 Jakar=
ta
> >>> 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 i=
s
> >>> in svn at jakarta/commons/proper/commons-nightly/. The main script,
> >>> commons_nigthly.sh gets svn upped on vmbuild by a crontab wrapper bef=
ore
> >>> executing each night, so if you just make changes to include a new bu=
ild
> >>> or build type into this script and config and check in the changes, t=
he
> >>> new component will be added.
> >>> Phil
> >>>
> >>>
> >>> ------------------------------------------------------------ ---------
> >>> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> >>> For additional commands, e-mail: general-help@jakarta.apache.org
> >>>
> >>>
> >>>
> >>>
> >>
> >
> > ------------------------------------------------------------ ---------
> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: general-help@jakarta.apache.org
> >
>
> --
> Henning P. Schmiedehausen -- hps@intermeta.de | 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: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
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
>> 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:
>> >> Umm....why not out of Gump?
>> >>
>> >> Phil Steitz wrote:
>> >>> Henri Yandell wrote:
>> >>>
>> >>>> On 1/16/07, 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.
>> >>>>>
>> >>>> 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: general-unsubscribe@jakarta.apache.org
>> >>> For additional commands, e-mail: general-help@jakarta.apache.org
>> >>>
>> >>>
>> >>>
>> >>>
>> >>
>> >
>> > ------------------------------------------------------------ ---------
>> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: general-help@jakarta.apache.org
>> >
>>
>> --
>> Henning P. Schmiedehausen -- hps@intermeta.de | 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: general-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: general-help@jakarta.apache.org
>>
>>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
On 1/17/07, 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/)
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
On Jan 18, 2007, at 8:57 AM, Henri Yandell wrote:
> On 1/17/07, 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/)
>
> 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