Newer versions are published on GitHub releases
- fix JENKINS-14438 Build cause condition fails on matrix projects
- fix JENKINS-14584 add more information about what a condition is evaluating (there might be more conditions which need some more logging)
- implement JENKINS-19300 Allow users to run conditional build steps if the build is running on a specific node
- fix JENKINS-13853 Conditional step is not being executed by UserCause when Jenkins > 1.427
- new condition: Cause Condition
- new condition: Shell Condition
- new Condition: WindowsBatch Condition
- Fixed JENKINS-12414. Now if no result has been set, the "Current status" is SUCCESS ("Current build status" run condition)
- JENKINS-12411 Expand environment and build variables directly wherever tokens can be used
- Add a Strings match condition to test if two strings are the same
- Add a Time condition to only run during a particular time of the day
- Add a Day of week condition to only run on certain days
- Links in help files open in a new window
- Add File exists and Files match to the core conditions
- Add build step runners that enable the user to choose what happens
if something goes wrong when evaluating a condition
Problems conditions may have when evaluationg - a regular expression is not valid, token expansion fails, expanded token expected to be a number, there is no spoon - Add Boolean condition to the core run conditions
- Add Numerical comparison to the core run conditions
- Initial release
Questions, Comments, Bugs and Feature Requests
Please post questions or comments about this plugin to the Jenkins User
mailing list.
To report a bug or request an enhancement to this plugin please create
a ticket in
JIRA.