Hi there, On 15-02-03 09:44 AM, Sebastian Rahtz wrote:

happy to set up the job on oxjenkins, shall I do that now or wait a bit?

Go for it. I just tested some of my normal stuff using the new plugin, and it seems to work a treat so far. You'll find the config.xml file for Jenkins in the usual place. The job has to be called "oxygen-tei" (there are some paths in the build-for-jenkins.sh script that depend on that). If you read that script, you'll see it's heavily based on your update-and-upload.sh script, but there are some nifty shenanigans around making the updateSite.oxygen script permanently available at the same URL, while behind the scenes it's shifting its location and has to be regenerated every time based on the previous version. But as far as I know, if you just install the config.xml in a job called oxygen-tei, it'll work. I'm keeping ten versions of the plugin, because we need to let people roll back when things go wrong, and because it gets built often (due to changes in itself, the Stylesheets, or P5). I know your Jinks occasionally has space issues, so that might be something to watch out for, but it's not huge.

the work monitoring oxjenkins is fairly small, so leave that with me for now.

OK.

...

The next step is to create some tests we can run in Oxygen to check core functionality of the add-on. I envisage this as an Oxygen project with a bunch of sample files that are transformed or otherwise manipulated and the results checked.

do you know how to drive oxygen from the command line, then? cool.

No, I was planning to write some ant tasks that would be run by a user in the Oxygen interface. Along the lines of: - Create sample file based on template X. - Transform using Stylesheets transformation Y. - Validate result with schema Z. That sort of thing. Not very sophisticated, but the idea would be that when we're about to release a new version of the plugin, someone subscribed to the latest Jinks build would run the tests and confirm nothing is wildly broken, then we'd go ahead and build/upload to the release location. It would be nicer to have automated testing happening as part of the build, of course. If I can learn how to do that, I'll have a go at it. But I don't know where to start right now. Cheers, Martin

-- Sebastian Rahtz Chief Data Architect University of Oxford IT Services 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431