Kim Haase wrote:
Thanks, Kristian --
Given my elementary knowledge of shell scripts this looks fine ...
One problem is that Myrna's build has already picked up my change --
COALESCE is in the Ref Manual already -- so probably the script won't
run Monday after all, if it is checking for changes. We might need to
wait for the next doc commit to make sure it works.
Actually, the Hudson build hasn't picked it up yet, since it was only
run once a week.
I confirmed that the reference documentation in dev/ has COALESCE, where
as the one in dev_test/ doesn't. The latest build happened early on the
3rd, the commit came late on the 3rd.
Regarding Myrna's build, we can discuss what to do about it.
I'm sure we can find a way to allow both the "build systems" to work
together. If Myrna is okay with continuing to run her build, there's no
point in disabling it just because we now have a different way to do it.
The one thing we should agree on, is how to tell if a build is newer
than the existing one. This can be a checksum of something (this only
work for certain scenarios), a revision number (preferably of the last
change) or something else.
A last alternative is to just keep overwriting the docs, even if the
same build is copied over the existing one (i.e. a newer build date but
no changes to the content).
As I have said earlier, my goal is to put a (easily automated) process
in place that is more transparent to the community. For instance, if
Myrna has to stop her build job for some reason, the community should
still be able to post new docs when changes are made. I think what
remains to achieve this, is to write a wiki page that describes the
process and provides the information needed for a Derby committer to
become a documentation publisher :)
I'll try to get this done, but it may be a while before everything is
ready. Then someone can test out the instructions.
Cheers,
--
Kristian
Kim
On 09/04/09 11:18, Kristian Waagan wrote:
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!
