Here is the toolchain information:
This is the info you wanted for
on the Toolchain for publishing. I set up 1.3 guides and they generate as PDF and HTML but somehow the release notes are not being pulled in during conversion.
There are no failure messages on the server or on my local machine when the build runs, and the XML is clean. You basically just get a blank page in PDF and HTML for the release notes.
The new ruby guide is here, set up according to what Matt/Sergey agreed on content:
For the release notes, there is XML typically in every guide that seems to serve as an include statement here:
The XML=>HTML conversion runs here: ssh email@example.com
, you can use Qakey.pem to access it
In ~/docs we recreated a shell script that will Git pull the current docs repo
Then it will do a make publish-push to trigger the XML=>HTML conversion
This make task runs a bunch of Perl scripts that do the conversion as well as includes. I believe all the Perl scripts called by make are under the Publish Then the make task syncs the new HTML with our web server.
Let me know if you need the key for access to this machine, but you should have it as it is the QA key for jenkins.