Book Image

Extending Jenkins

By : Donald Simpson
Book Image

Extending Jenkins

By: Donald Simpson

Overview of this book

Jenkins CI is the leading open source continuous integration server. It is written in Java and has a wealth of plugins to support the building and testing of virtually any project. Jenkins supports multiple Software Configuration Management tools such as Git, Subversion, and Mercurial. This book explores and explains the many extension points and customizations that Jenkins offers its users, and teaches you how to develop your own Jenkins extensions and plugins. First, you will learn how to adapt Jenkins and leverage its abilities to empower DevOps, Continuous Integration, Continuous Deployment, and Agile projects. Next, you will find out how to reduce the cost of modern software development, increase the quality of deliveries, and thereby reduce the time to market. We will also teach you how to create your own custom plugins using Extension points. Finally, we will show you how to combine everything you learned over the course of the book into one real-world scenario.
Table of Contents (16 chapters)
Extending Jenkins
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Properties files and Messages


The Messages.properties and config_fr.properties files are there to provide users with i18n internationalization, as described here:

https://wiki.jenkins-ci.org/display/JENKINS/Internationalization

There is some more detail on localization and internationalization at this link:

http://www.w3.org/International/questions/qa-i18n

In Jenkins plugin development, all we really need to do is provide config_LOCALE.properties files to cater to each language. For example, if the user's LOCALE variable is set to fr, the messages in the config_fr.properties file will be used—other LOCALE files can be added as desired to support other languages.

Your plugin code is able to use and refer to the properties at runtime, as follows:

Messages.GravenBuilder_Task()

The Messages.java class in the target directory is generated at build time, based on these properties files.