jenkins
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:
1. 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.
2. 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.
-
6
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:tools:building/jenkins && cd $_
- Create Badge
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000142 142 Bytes | |
jenkins.changes | 0000006460 6.31 KB | |
jenkins.init | 0000006279 6.13 KB | |
jenkins.logrotate | 0000000498 498 Bytes | |
jenkins.spec | 0000003892 3.8 KB | |
jenkins.sysconfig | 0000002777 2.71 KB | |
jenkins.war | 0045387291 43.3 MB |
Revision 12 (latest revision is 494)
- Update to version 1.430: * Added way to mark all plugins to be updated at once (issue 10443) * Fixed a bug in the UI JavaScript behavior with IE * Matrix project pages don't show latest test results. (issue 10864) * Bundling the translation assistance plugin in the hope of increasing the contribution. * Introduce a fine-grained permission to control who is allowed to run the Groovy Console. * Add support for maven-android-plugin integration test reports (issue 10913)
Comments 0