Modified items

All recently modified items, latest first.

gerrit-tools-1.0.0-1.lbn36.x86_64: gerrindex - inspect gerrit's lucene indexes gerrdb - inspect gerrit's h2 databases

gerrit-plugins-3.8.1-2.lbn36.noarch: A range of useful prepackaged Gerrit plugins - ready to deploy into your Gerrit via: ssh -p 'gerrit init --install-plugin <name>'

gerrit-3.8.1-2.lbn36.noarch: Gerrit is a web based code review system, facilitating online code reviews for projects using the Git version control system. Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer. Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer. This functionality enables a more centralized usage of Git.

jenkins-plugin-installation-manager-2.13.0-1.lbn36.noarch: The plugin manager downloads plugins and their dependencies into a folder so that they can easily be imported into an instance of Jenkins. The goal of this tool is to replace the Docker install-plugins.sh script and the many other implementations of plugin management that have been recreated across Jenkins. The tool also allows users to see more information about the plugins they are downloading such as available updates and security warnings. By default, plugins will be downloaded; the user can specify not to download plugins using the --no-download option. Usage ----- /usr/bin/jenkins-plugins --help

jenkins-cli-2.489-1.lbn36.noarch: Jenkins CLI tool (wrapper for jenkins-cli.jar) /usr/bin/jenkins-cli

jenkins-2.489-1.lbn36.noarch: Jenkins monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Jenkins focuses on the following two jobs: - Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity. - Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong.