Written in a Jupyter notebook to be meta
Located at a server where the project's main build is created, Jenkins triggers a new build every time a user checks in some changes into the source code, thus supporting the process of continuous integration for testing or development phases. The builds created are reflected on the Jenkins dashboard, with details logged in such as time and date created, build status such as success or failure, error messages in case of build failure, reports and other helpful details which helps the user keep track of the builds generated. Jenkins can be configured to be more user friendly by customizing it to send notifications when the build is generated. As it supports multiple projects, while a build is already in progress, a build queue is created according to the time-stamp with which each build is triggered.
Distributed builds are supported to reduce the load off of the central server, mostly used in case of large builds coupled with heavy trigger frequency.
Travis CI support for R is contributed by the community and may be removed or altered at any time
(from Travis CI website)