Since we're now close to having a working Jenkins, I've written what we know into a build script, which I've been testing and tweaking. I've created a Jenkins3 server which is a plain Ubuntu server, fully updated, and I've set up a snapshot from which I can run the script. After several runs, it's pretty close to being complete and functional, but I haven't had a chance to test the Jenkins install itself yet.
No word from SR on what to do about this rather odd font, so I'm trying a simple install of the downloadable package to see if that'll do it:
cd /usr/share/fonts/truetype mkdir hannom cd hannom wget -O hannom.zip http://downloads.sourceforge.net/project/vietunicode/hannom/hannom%20v2005/hannomH.zip?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fvietunicode%2Ffiles%2Fhannom%2Fhannom%2520v2005%2F&ts=1305220899&use_mirror=cdnetworks-us-2 unzip hannom.zip find . -iname "*.ttf" | rename 's/\ /_/g' rm hannom.zip fc-cache -f -v
Ran another build of P5-Documentation, but now it fails like this:
Wrote teip5.epub in /var/lib/jenkins/jobs/TEIP5-Documentation/workspace mv teip5.epub Guidelines.epub java -jar Utilities/epubcheck-1.1.jar Guidelines.epub Epubcheck Version 1.1 ERROR: Guidelines.epub/OEBPS/ref-re.html(42): element "div" from namespace "http://www.w3.org/1999/xhtml" not allowed in this context Check finished with warnings or errors! make: *** [epub.stamp] Error 1 make: Leaving directory `/var/lib/jenkins/jobs/TEIP5-Documentation/workspace' make: *** [dist-doc.stamp] Error 2 Archiving artifacts
The Jenkins process runs as the jenkins user, but when oXygen is invoked, it tries to read/write from
/root/.com.oxygenxml, and since that directory is owned by root, it fails. I've chowned it to jenkins:root (jenkins appears to have no group), and I'm trying again. I've also created /root/.java, since oXygen seems to need that, and made it readable by the jenkins user.
I also discovered, from the remaining errors in the Stylesheets task, that there is no symbolic link trail for the Java jar executable. This is probably the result of my installing the Sun JDK manually instead of from the repos. So I did this, following the analogy of the java symbolic link:
sudo ln -s /usr/local/java/jdk1.6.0_25/bin/jar jar sudo ln -s /etc/alternatives/jar jar
And now the Stylesheets task completes!
Now there's just the blasted Han Nom font issue.
This blog is the location for all work involving software and hardware maintenance, updates, installs, etc., both routine and urgent, in the server room, the labs and the R&D rooms.
|<< <||Current||> >>|