incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: automating history charts and Clutch
Date Tue, 18 Sep 2012 20:17:28 GMT
On 18 September 2012 12:07, sebb <> wrote:
> On 18 September 2012 03:32, David Crossley <> wrote:
>> sebb wrote:
>>> David Crossley wrote:
>>> > Jukka Zitting wrote:
>>> >> crossley wrote:
>>> >> > r1386462
>>> >> > Modified:
>>> >> >     incubator/public/trunk/content/history/current.txt
>>> >>
>>> >> Thanks for keeping that file up to date! The graph at
>>> >> is quite useful.
>>> >>
>>> >> However, I'm wondering if there really is need to manually maintain
>>> >> separate text file when all the required information should already
>>> >> present in podlings.xml. Can we generate the current.txt file from
>>> >> podlings.xml, or (even better) have the client create the history
>>> >> graph directly from podlings.xml?
>>> >
>>> > It would be fantastic if someone could automate that.
>>> > At the moment, the current.txt (yellow) is maintained manually
>>> > and the entry.txt (green) is automatically handled by Clutch.
>>> > Ideally both would be automated independently of Clutch.
>>> Perhaps add a task to build.xml that generates current.txt and
>>> entry.txt from podlings.xml?
>>> Could extract the entry.txt code from clutch and extend it to handle current.txt
>>> If that sounds reasonable, I'm happy to give that a try.
>> That seems like a good solution, now that we have the podlings.xml file.
> I've created an XSLT script that generates a version of entry.txt.
> It currently generates the output in date order rather than reverse
> date order as that is easier - one can use position() for the number.

Eventually went with reverse data order as it was not much more difficult.

> Not sure why the order is currently reversed; the Javascript does not
> seem to care about ordering.
> Is there a reason for the reverse data order?
> I've started looking at current.txt.

Done, though the process requires xslt and Perl, as I could not work
out how to create a running total in XSLT.

Also the output is in increasing date order and includes one entry for
each distinct start/end date.
Not sure what dates were use originally as they don't all seem to
appear in podlings.xml.

The final total is 1 different from before, but agrees with podlings.xml

>>> Maybe at some point clutch itself could be run automatically whenever
>>> podlings.xml is updated.
>> Perhaps just run it twice per day regardless. There are other
>> things that it assesses too.
> I'd forgotten that.
>> Yesterday the podlings.xml was updated a number of times
>> in quick succession to catch up with laggard graduates.
>> So would not want to run cumbersome Clutch on each update.
> Very true, it does take quite a while.
>> Or perhaps it could be triggered by Ant, say 30 minutes after
>> the update, otherwise once per day.
> Tricky to get that right.
>> Clutch seems reasonably robust now. The main thing that
>> used to trip it up was project names with inconsistent
>> spellings for different resources. The recent addition of
>> the "resourceAliases" attribute in podlings.xml does assist.
> Yes, though we would need to ensure that the log file was available
> for inspection.
> Could perhaps be run by the apsite login on minotaur. This runs the
> people and projects builds.

Just realised that apsite won't be able to commit the generated output.

>> -David
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message