Changelog

2.29 (2018 Nov 09) - WARNING: Although issues have been fixed since 2.28, this version may carry extra risk and is not fully backwards compatible with 2.25 or older; consider waiting a few days to update in critical environments.

JENKINS-54128: Change the implementation of WorkflowRun#getLogFile to avoid creating a new temporary file each time the method is called.

Fix: Do not call WorkflowRun#getLogFile when an error occurs while opening the log file for a Pipeline to avoid logging an additional stack trace.

2.28 (2018 Nov 06) - WARNING: Although issues have been fixed since 2.27, this version may carry extra risk and is not fully backwards compatible with 2.25 or older; consider waiting a few days to update in critical environments.

2.27 (2018 Nov 01) - WARNING: Although major issues have been fixed since 2.26, this version carries extra risk and is not fully backwards compatible with 2.25 or older; consider waiting a few days to update in critical environments.

2.26 (2018 Oct 12) - WARNING: This version carries extra risk and is not fully backwards compatible; consider waiting a few days to update in critical environments. Update Pipeline Groovy Plugin to 2.58+ along with this update.

JEP-210: redesigned log storage system for Pipeline builds. This update involves a new log file format. Older releases will be able to display the whole-build log in a somewhat degraded fashion in the classic, though not Blue Ocean, UI. You are advised to also update Pipeline Groovy Plugin to 2.58.

2.26-beta-1 (2018 Oct 04)

JEP-210: redesigned log storage system for Pipeline builds. This update involves a new log file format. Older releases will be able to display the whole-build log in a somewhat degraded fashion in the classic, though not Blue Ocean, UI. You are advised to also update Pipeline Groovy Plugin to 2.58-beta-1.

Improves performance significantly when plugins/operations load many Pipeline builds (weather column, etc) just to check the Result

Makes an especially large difference for Performance-Optimized Pipelines with many steps

This makes the 'completed' field persistent for Pipeline Runs and will trigger a one-time re-save for legacy builds

Back-compatibilityIssue: the presence of the 'completed' field will introduce errors about double onLoad calls when downgrading to version 2.17. This can be fixed (to allow for loading in earlier versions) by searching for all build.xml files containing the following strings and removing those lines:

<completed>true</completed>

<completed>false</completed>

Bugfix: Fix one case where running Pipelines would not reflect an updated Resume Disabled status on the job

Part of Bugfix: Error "NullPointerException in SandboxContinuable.run0" after restart in Performance-Optimized Durability Setting (JENKINS-50407)

Remainder of bugfix is in Pipeline Groovy Plugin, version 2.47

Part of Major Bugfix: Error "NullPointerException in CPS VM thread at WorkflowRun$GraphL.onNewHead" as result of a race condition (JENKINS-49686)

The other part of the bugfix is in the Pipeline Groovy Plugin - version 2.47