Jenkins 1.507
Jenkins 1.507 summary
Jenkins 1.507 screenshot
Jenkins 1.507 description
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.
Get Jenkins and give it a try to see how useful it can actually be for you!
What's New in This Release:
· Show the reason for a skipped test if the test result contains one (issue 8713)
· an in-progress build was dropped from JSON API when lazy-loading was introduced. (issue 15583)
· In-progress builds now survive the "reload from disk" administrator action. (issue 3265)
· If artifact archiving failed with an I/O error, the build nonetheless was considered to be a success. (issue 2058)
· Fixed a bad interaction between Windows symlinks and build record lazy loading. (issue 15587)
· Remember the lastStable/Failed/Successful/etc builds to avoid eager loading builds. (issue 16089)
· Wrong build result in post build steps after failed pre build step in maven projects. (issue 17177)
Jenkins 1.507 keywords
Jenkins 1.507 for Developers
masocongty