Literate1.0Minimum Jenkins requirement: 1.609.1ID: literate
The plugin provides support for the literate-style multi-branch project type.
What is a literate-style project
A Literate-style project is a project where the instructions on how to build the project are part of the actual project themselves. At its simplest, if the project has a README.md file that contains a build section with a literate code block containing the build instructions, that is a literate style project.
Your typical GNU native code project might use something like
Simple build with environment
ANT projects may do something like
Several environments, build commands depending on the environment
We could have a more complex project, e.g.
The literate style lets us intersperse comments around the actual build steps to assist in documenting the build instructions.
The plugin includes some facilities to support lightweight promotions using manual approval.
You can define the command associated with a promotion just like a build command, in a specific question. But you are free to choose the name of the section. This name will need to be provided to the job configuration.
Of course, the release process doesn't make sense for all branches. It will usually be valid only for master branch. The literate plugin allows you to specify such a restriction.
What is a multi-branch project
A multi-branch project is a project that automagically creates a sub-project for every branch in your source control. When the branch is deleted (assuming you configure the project to auto prune dead branches) then the sub-project will be removed. Branches are cheap and easy to create in Source Control. They should be just as easy to create in Jenkins... with a literate-style multi-branch project they are trivial to create.
The advantage that literate-style projects bring to multi-branch projects is that you can even change the build system in your branch without breaking the job for your branch.
How to install
This plugin is currently in beta version. It means it is available from the jenkins experimental update center. Once you have configured your Jenkins instance to target the experimental update center, you can install the literate plugin as any other plugin.
This plugin is no longer in beta version. You can install the literate plugin as any other plugin, without having to use the experimental update center.
- Screw it, let's cut an official release... while there are some things I think should be done first, given that workflow enables the same problems and doesn't provide a solution we may as well just ship it!
- The plugin is now available in the official update center.