Documentation/Builds

Build jobs and pom.xml

Here's a listing of all documentation pom.xml files and build job files. The pom.xml files live with the documentation in the respective repository. The build jobs live in the openstack-infra/config repository.

openstack-manuals, three branches, essex, folsom, master

openstack-admin-manual-compute (1) essex, folsom, master
openstack-admin-manual-netconn (1) essex, folsom, master
openstack-admin-manual-object (1) essex, folsom, master
openstack-cli-guide (1) folsom, master
openstack-glossary (1) folsom, master
openstack-install-deploy-guide-apt-fedora (1, shared with install/deploy ubuntu) essex, folsom, master
openstack-install-deploy-guide-ubuntu (shared with above) essex, folsom, master
openstack-basic-install (1) folsom, master
openstack-ha (1) folsom, master
openstack-ops (1) folsom, master

api-site (no branches for API docs)

openstack-api-programming guide (1)
api-quick-start (1)
api-reference (1)

compute-api (3) image-api (2) object-api (1) netconn-api (2) volume-api (1) identity-api (2)

operations-guide (1)

Total: 23 (ops) +14 (api) =37 books build with jobs, 24 pom.xml files get built

Version of Maven Plugin

The Maven Plugin is updated periodically with features we may want to incorporate in the OpenStack build process. Specifically 1.7.2 is what we use for Grizzly documentation as it contains features designed to make life easier. These changes also required some changes in pom.xml for each book. All these changes have been incorporated so this is information to describe the settings in pom.xml. A major new feature of this version of the plugin is that images are automatically handled for you. This saves two steps and adds a level of validation.

You no longer have to add a postProcess section to your pom.xml configuration to copy image files into the webhelp output directory unless you want to do a clean up step of deleting the renamed directory. Instead, these settings tell the build where to place the built files.

                          <targetDirectory>target/docbkx/webhelp/${release.path.name}/openstack-compute</targetDirectory>
                          <webhelpDirname>admin</webhelpDirname>
                          <pdfFilenameBase>bk-compute-adminguide-${release.path.name}</pdfFilenameBase>

The clouddocs-maven-plugin automatically detects which images you use in your document and copies them to the output directory. When you use .svg graphics, you do not have to create a .png version. Now, when you generate web help, the clouddocs-maven-plugin automatically converts the .svg to a .png file and uses it instead. You want to ensure all images have the <figure> tag and use contentwidth="6in" as an attribute on the <imageobject>. The system also checks for the availability of images before proceeding with the build, but you may still see "Figure not found" errors that you can safely ignore.

When you generate web help, by default the plugin now automatically generates a PDF and puts it in the webhelp directory, so links will no longer break to the PDF. You can also remove any pdf processing instructions from the book file itself.