Kim Haase wrote:
A nightly build has been lovely (thanks, Myrna!) but realistically, once a week would be fine for a build of the latest docs.I wish I could volunteer for this, since I'm the one who always complains when the process breaks down, but I can't afford the time to learn about cron jobs and checksums (about which I am extremely ignorant). So many thanks to whoever takes this on.
Hi Kim,I have written the first version of the script checking for updates and deploying the docs. It must be run from people.a.o. See the script attached, and please comment on it if you something that should be changed. Currently both the deploy directory and the MD5 checksum file must exist (it doesn't have to contain a checksum though).
I tested it and hopefully something should appear in http://db.apache.org/derby/docs/dev_test/ in a little while (during tomorrow at latest). To navigate easier, you can use the links from the official documentation page [1], and then just replace dev with dev_test.
I have also changed the Hudson job to check for changes every Monday (just after midnight UTC) and every Wednesday (around 20 in the evening/night UTC). My crontab will run the script a little later (to allow the build to finish).
Since Kim committed a change yesterday, a new build of the docs should be built and published some time on Monday (under dev_test). Let's see what happens!
-- Kristian [1] http://db.apache.org/derby/manuals/index.html
Kim On 09/04/09 07:41, Kristian Waagan wrote:Myrna van Lunteren wrote:On Thu, Sep 3, 2009 at 3:05 AM, Kristian Waagan<[email protected]> wrote:Hello, I have now configured a Hudson job building the Derby documentation.Great! Thanks for all your work on setting up the Hudson system. I have one question...I've a automated process that copies nightly built docs out to /www/db.apache.org/derby/docs/dev. Can/Should I stop that job?Hi Myrna,I think you can stop the job, but I would appreciate if you kept everything around for a while :) Maybe you want to test out the new script when it's ready, or integrate it in such a way that your builds work as a backup system in case Hudson goes down.The docs take a little less than 1 hour to build on the Apache server we're using.How often do we want to check for changes and rebuild the docs? The website also has some stuff that looks like old cruft to me: /www/db.apache.org/derby/docs/10.0-bak /www/db.apache.org/derby/docs/10.1_old /www/db.apache.org/derby/docs/10.4_old docs-10.0.tar docs-10.0.tar.gz docs-10.0.zip Does anyone object to deleting these?There are also some old files lying around in dev/, so I would delete that one too and "repopulate" it.Some of the directories have wrong ownership and/or wrong permissions. I have taken action to fix that by sending mails to Rick, Andrew and the infrastructure team. To allow any committer to fix issues, it is important that the files/dirs have group ownership set to 'db' and that the group is given write access.
deploy_dev_docs.sh
Description: Bourne shell script
