Ok, I've been monitoring the nightlies for a few days now and it
looks to be completely hands off and it all happens on Apache
hardware. I also made sure that all configuration for doing the
nightlies are included either as files (nightly.sh) or as
configuration (cron job config), so in a worse case scenario, we can
be back up at a moments notice.
Next, I want to bring in the site generation for both 1.2.x and head.
I am planning to deploy the generated site over cvs.apache.org:/www/
struts.apache.org/ which means our existing web site will never be
more than 24 hours old.
If we don't want to do that, I could put together something like a
web console hosted on struts.zones.apache.org that we can use to kick
off an update.....or some kind of hook so that when a commit is made
to the documentation, a process is queued to regenerate and deploy a
new site after 4 hours.
I would also like to build in email notification if the nightly and/
or site generation fails like Gump gives us. The only issue with
relying on Gump is that Gump does not build all of what the nightlies
build, especially documentation.
Your thoughts?
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 24, 2005, at 1:29 AM, James Mitchell wrote:
Ok, that's what I needed. I'll see if I can pull it all together.
Thanks
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 24, 2005, at 12:09 AM, Wendy Smoak wrote:
From: "James Mitchell" <[EMAIL PROTECTED]>
BTW -- Can you tell me (wiki, mail-archive, etc) where to get
the latest instructions to build the web site and documentation
and how we want it laid out? I'm getting ready to add that task
to the nightly build and I don't want to do it wrong.
I haven't been able to get Maven to build a recursive multiproject
site. It either loops, or refuses to descend. Here's what I have:
echo "------ build multiproject site (head) ------"
cd /cygdrive/e/svn/struts/current/site/
maven multiproject:site > /path/to/build.log
echo "------ build multiproject site (head - Shale) ------"
cd /cygdrive/e/svn/struts/current/shale/build
maven multiproject:site >> /path/to/build.log
cp -r target/docs/* ../../site/target/docs/shale
echo "------ build multiproject site (head - Sandbox) ------"
cd /cygdrive/e/svn/struts/current/sandbox/
maven multiproject:site >> /path/to/build.log
cp -r target/docs/* ../site/target/docs/struts-sandbox
If you have a multiproject site for Ti, then you'd do the same
thing, and copy it up to sandbox/target/docs/struts-ti before you
copy the whole of sandbox/target/docs over to 'site'. Or maybe
you can get Maven to cooperate. :)
HTH,
--
Wendy
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
