On Wed, 13 Mar 2002, Sam Ruby <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
>>
>> I've just had a quick look over Sam's script, but I think he is
>> making it too easy for the projects 8-). The stuff the script does
>> in gather should be done by Ant inside the build.xml of the
>> specific projects IMHO.
>
> I have no problem with a little social engineering. ;-)
I'm not sure I understand what you want to say here.
These projects have asked you to do their nightly builds, telling them
they'd need a target that puts all things they want to deliver in a
nightly build isn't too much, is it? If it is, we can find a solution
for that as well 8-)
Let's assume the simplest possible case. All projects that want to
have nightly builds have an Ant target that collects everything that
they want to distribute.
What information would Gump need? Which target to run, where the
things are collected by Ant and where they should end up on the
website. Is there more?
The target can be specified by a new project definition, much like
dist-ant works today.
For the rest
<deliver fromdir="distribution/nightly" tosite="jakarta"
todir="jakarta-ant/nightly" />
we may even have multiple entries to pick up stuff from different
directories.
For Ant that could work today
<deliver fromdir="distribution/bin" tosite="jakarta"
todir="jakarta-ant/nightly" />
<deliver fromdir="distribution/src" tosite="jakarta"
todir="jakarta-ant/nightly" />
without further changes to dist-ant.
The different avalon projects would all specify the same todir.
This could lead to (pseudo shell script)
# only once, set up a scratch area
rm -rf nightly
mkdir nightly
foreach site # distinct tosite attributes in all deliver entries
mkdir $tosite
# once per deliver entry
cd nightly/$tosite
mkdirhier $todir/$date
cp $module/$fromdir/* $todir/$date
# at the end
foreach site
do
cd nightly/$tosite
tar cf $tosite.tar *
scp $tosite.tar daedalus...
done
This could be created by a stylesheet without too much trouble, I
guess, maybe the foreachs need to be rolled out, dunno.
The post_to_site script would untar xml.tar in /www/xml.apache.org/dist
and jakarta.tar in /www/jakarta.apache.org/builds. These would be
hard coded, at least in a first step.
In a less than ideal world, we could put an Ant target that creates
the deliverables into the gump descriptor literally and create a build
file from that.
Am I missing some important pieces?
Stefan
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
