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 |
|---|---|---|
| jenkins.changes | 0000051398 50.2 KB | |
| jenkins.init | 0000005165 5.04 KB | |
| jenkins.logrotate | 0000000521 521 Bytes | |
| jenkins.spec | 0000004391 4.29 KB | |
| jenkins.sysconfig | 0000002913 2.84 KB | |
| jenkins.war | 0062953726 60 MB |
Revision 58 (latest revision is 494)
Sascha Peilicke (saschpe)
committed
(revision 58)
- Update to version 1.531: + Deleting an external run did not immediately remove it from build list, leading to errors from log rotation. (issue 19377) + When copying a directory from master to slave fails due to an error on the slave, properly report it. (issue 9540) + Identify user agent for Internet Explorer 11. (issue 19171) + Since 1.518, fingerprint serialization broke when job or file names contained XML special characters like ampersands. (issue 18337) + Robustness against truncated fingerprint files. (issue 19515) + JavaScript error in the checkUrl computation shouldn't break the job configuration page. (issue 19457) + Annotate the Advanced section if some fields are already customized. (issue 3107) + No events fired when project is enable/disable or the description is changed (issue 17108) - Changes from version 1.530: + Send Maven agent JARs to slaves on demand, not unconditionally upon connection. (issue 16261) + Occasional race condition during startup. (issue 18775) + Robustness against startup error for users of Global Build Stats plugin. (issue 17248) + 404s from Javadoc and HTML Publisher plugins. (issue 19168) + Build number symlinks and permalinks not updated for Maven module builds. (issue 18846) - Changes from version 1.529: + With Apache Maven 3.1 build, logging configuration from the Apache Maven distribution is not used. + Avoid log duplication with Apache Maven 3.1 builds + Ungraceful handling of empty matrix project axes. (issue 19135) + Updated Groovy to 1.8.9 to avoid GROOVY-4292. + CLI login command broken on Windows since 1.518. (issue 19192) + A malformed JUnit result file should mark that test suite as a failure, but not interrupt archiving of other tests. (issue 19186) + Build for $username now shows also build scheduled by user (issue 16178) - Changes from version 1.5.28: + Command line now supports "--sessionTimeout" option for controlling session timeout + Form validation methods weren't getting triggered when one of its dependency controls change. (issue 19124) + When POST is required for some HTTP operation but GET was used, the response should have status code 405. (issue 16918) + Correct help text of Label field in automatic installation of tools in global configuration. (issue 19091) + Use Guice from Google rather than a fork + Jenkins does not invoke ProcessKillers for Windows (issue 19156)
Comments 0