See GitHub Releases
- PR #116 - Show the full display name of runs in promoted build parameters
- JENKINS-40803 - Prevent infinite loop while promoting a build when the Config File Provider Plugin is installed.
SECURITY-746 -
Make permissions consistent for Approve, Re-Execute, and Force promotion actions
-
Users with just the Promotion/Promote permission are no longer allowed to re-execute or force promotions with a manual condition that specifies a list of users, unless the user is on that list
-
Users specified in a manual promotion condition are now allowed to force this promotion
-
Administrators are now able to approve any promotion with a manual condition
-
Compatibility Notes:
- This change alters the behavior of the Plugin in some conditions, jobs may require reconfiguration.
- Table below shows the permission changes.
Legend:
- Cells with bold red text - indicate combinations, which revoke dangerous permissions
- (manual condition) - Action
-
JENKINS-49433 -
Prevent NullPointerException in JobDSL when omitting
the
evenIfUnstableargument- Affected JobDSL
methods:
selfPromotion(),parameterizedSelfPromotion(),downstream()
- Affected JobDSL
methods:
-
JENKINS-48634 -
Prevent ClassCastException when running promotion from a status page
with empty forms
-
JENKINS-47573 -
Prevent the extension loading issue when the Rebuild Plugin
is not installed (regression in 2.30)
PR
#106 -
Update Jenkins core requirement to 1.625.3-
PR
#106 -
Update Maven plugin requirement to 3.0 and cleanup issues in library
dependency conflicts
-
JENKINS-22068 -
Fail promotion builds instead of hanging when a promotion is built/rebuilt directly
-
JENKINS-37368 -
Improve performance of DownstreamPass promotion condition listener logic
-
PR #103 -
Update the target core baseline to 1.609.3
JENKINS-29586
- Add support for ANSI color output in console- PR #102 - Fix link to the Fingerprint Wiki Page
-
JENKINS-40552 -
Prevent possible deadlock between JobPropertyImpl and
PromotionProcess
-
JENKINS-29358 -
Fix the sort order of the Promotion History
-
JENKINS-36623 -
Fix test runs against the 1.651.3 core (Plugin compatibility tester)
-
JENKINS-39362 -
Fix the binary compatibility issues in test runs by getting rid of
mockito-all
-
JENKINS-34826 -
Make the plugin compatible with
SECURITY-170
fix in Jenkins 1.651.2+ and 2.3+
-
PR #91 -
Prevent exceptions on startup if the optional JobDSL plugin is
missing
-
PR #90 -
Improve the workspace allocation performance
-
JENKINS-29776 -
Add Job DSL support for Promoted Builds Plugin
-
JENKINS-33147 -
PROMOTED_TIMESTAMP used to show the UTC timestamp instead of the local JVM one.
Behavior is configurable now
-
PR #76 -
Allow hiding promotion processes based on a parameter value
-
PR
#89 -
Migration to the new Jenkins Plugin parent POM
-
PR
#87 -
Fixes of minor issues discovered by FindBugs
-
JENKINS-34204 -
Fix minor issues in Job DSL support discovered during the local snapshot testing (not a regression)
-
JENKINS-32993 -
Expose the PROMOTED_TIMESTAMP variable in promotion processes
-
PR
#75 -
Add support for running promotions on inheritance projects
-
JENKINS-31908 -
Sort Promotions in UI by Number instead of customization ID
-
JENKINS-31406 -
Broken layout of promotion status pages in 1.625+
-
JENKINS-32006 -
Revert the erroneous fix of
JENKINS-13751
in 2.24
-
JENKINS-13751 -
Promotion process should provide the project's SCM to promotion
steps (reverted in 2.24.1)
-
JENKINS-31356 -
The plugin should consider approvers in the re-execution action
-
PR
#72 -
Fix exception if somebody calls
PromotionProcess::isFingerprintConfigured()
-
JENKINS-29793 -
Provide parameters from manual approval on all promotions
-
JENKINS-27716 -
Support disabling the promotion jobs in jenkins-1.585+
-
JENKINS-31320 -
Make the plugin compatible with breaking UI changes in Jenkins 1.619+
-
JENKINS-30212 -
Medium-sized promotion star icons were missing
-
JENKINS-30411 -
Add the PROMOTION_ENV token macro
-
JENKINS-25011 -
Fix the Folders support in Promoted builds parameter
- Now there is a support of global and relative addressing to builds ('.' and '..' markers are supported)
- See the built-in documentation for more details
- The change alters the default behavior
-
JENKINS-7739 -
Recursively evaluate downstream projects in DownstreamPassCondition
-
JENKINS-3549 -
Promotion Status column (last promotions for each type)
-
JENKINS-3549 -
Last Build Promotion Status column
-
JENKINS-16063 -
Inject PROMOTED_USER_ID variable into the build
-
FindBugs cleanup (potential NPEs,
concurrency, etc.)
The fix for JENKINS-25011 changes the default behavior for paths without an explicit absolute/relative address specification (e.g. project="myProject"). By default it will resolve relative paths and then falls back to global paths. If you have "myProject" within a folder and on the top level, another project may be returned after the plugin update. In order to restore the legacy behavior, use the hudson.plugins.promoted_builds.util.ItemPathResolver.enableResolutionAgainstRoot Boolean system property
- issue #24782 Prevent phantom builds from being scheduled when PromotionProcesses are built directly.
- issue #20492 partial fix, show re-execute button unconditionally
- fix an NPE in
getBuilds()when projectName is incorrect - added support for rebuild plugin
- Prevent log file being cluttered with permission exceptions when users have Item.EXTENDED_READ but not Item.CONFIGURE
- issue #8963 CRUD for promotion processes using REST API.
- issue #23565 Export build display name to promotion job.
- Repeating/Duplicating promotion parameters (issue #22005)
- Added
PROMOTED_USER_NAMEenvironment variable (issue #16063) - Fixed a couple of typos
- Fixed repeated exception being thrown when installed with literate plugin.
- Fixed NPE when no Manual Promotion was configured (issue #20166
- Enable editing parameters for re-executions (issue #8962)
- Added
PROMOTED_JOB_FULL_NAMEenvironment variable (issue #18958)
- Expose promotion information via the REST API
- Prevent duplication of promotion processes when creating promotion processes from other plugins
- Fix for an NPE, and diagnosis for another.
- Reduced plugin size by eliminating unnecessarily bundled library.
- NPE when used in 1.507+ (issue #17341)
- Test failures, and possibly visible bugs, when used with recent Jenkins (issue #15156)
- New promoted build parameter that can be used to select builds that have been promoted
- Fixed file parameter on ManualApproval not correctly uploading the file
- Build shouldn't be promoted by a deleted promotion process (issue #12799)
- Honor annotated console output (issue #15328)
- Added a trigger that allows projects to listen to promotions happening in other projects
- PROMOTE permission can be used in project matrix-based security (issue #14890)
- Downstream jobs textbox is now auto-complete-capable (issue #14560)
- Fix manual promotion of maven project and matrix project (issue #13631, issue #13472)
- Fix 404 when clicking the promotion's progress bar to view console output (pull-20)
- Fix preventing setting "Restrict where this project can be run" (issue #14197)
- Fixed incorrect link from the executor status (#17)
- Added a new promotion process that triggers right after a build is completed when it's parameterized. (#16)
- Fixed a 500 error when viewing promotion on a failed build (issue #12386)
- Image files are now in the PNG format.
- Improved hierarchical project support
- Fixed a possible NPE that fails the promotion (issue #11609)
- Added Promotion History per Promotion Process at Project's Promotion Status page (issue #10448)
- Don't run promotionProcess that are disabled (issue #10423)
- Manual approvement causes an NPE if project name or promotion name contains URI-unsafe chars (issue #11122)
- Modified the self-promotion condition so that it does not trigger for builds which are a failure. Also it is now configurable whether to self-promote for unstable builds. (issue #10250)
- Added a new promotion condition that immediately promotes itself.
- failed to Re-execute promotion if promotion builds plugin is disabled (issue #9588).
- promote plugin should provide ability to select slave node to run (issue #9260).
- Fix for NPE when promoting a build with a custom workspace (issue #9254).
- Fixed a problem where removing a promotion process leaves broken image links in the build history.
- Fixed a problem where deleting and recreating the promotion process with different case (abc vs ABC) can result in weird behavior on Windows.
- If a promotion criteria is met but the promotion fails, change the icon to represent that.
- Exposed the job name and the build number of the promotion target to the promotion process (
PROMOTED_JOB_NAMEandPROMOTED_NUMBER.) - If the build is parameterized, expose that to the promotion process as well
- Added a new promotion criteria where a promotion in upstream promotes a downstream build.
- Fully implemented manual approval with user / group permissions and display Approve button on promotion page (no longer need to allow force promotion to all)
- New promotion action to mark the promoted build as keep forever
- Promote a build even if downstream build is unstable. (issue #8626)
- Promote Builds Plugin can use custom workspace. (issue #8547)
- Invalid characters in Promotion name causes error. (issue #7972)
- Fix promotion permlinks. (issue #8367)
- Allow promotion actions to be reordered. (issue #8548)
- Promotion processes are now recognized as permalinks.
- If fingerprints are not available, use the upstream/downstream triggering information to determine the relationship as a fallback.
- Add the possibility to choose a different color for the star icon, to be able to differenciate the various promotion processes
- Use JDK configured for project when running promotions (issue #3526)
- Select node for running promotions from label configured for project (issue #4089) (does not yet run on exact node where promoted build ran, unless project is tied to a single node)
- Show most-recent first in promotion history tables (issue #6073)
- Fix for running on slave node (issue #4635)
- Copy promotions when a job is copied (issue #3489)
- Fix broken "Back to Promotion Status" link (issue #3562)
- Updated to work with Jenkins 1.320
- Re-doing a release as 1.3 had never shown up in the update center.
- Expose environment variable
PROMOTED_URLthat points to the URL of the build that's being promoted (report) - Internal modernization.
- Updated to work with the current Jenkins
- Fixed a problem where Jenkins may issue the same warning multiple times for the same configuration problem (report)
- SVN Tagging is now a permitted promotion step
- Promotion now fails if any actions are not performed (issue #2597)
- Improved logging of promotion build process so users can see what succeeded and what failed
- Promotion action to build another project no longer does nothing (issue #1765)
- Added "Promotion History" pane to the PromotedBuildAction page (issue #2794)
- Fixed 404 for last failed link while promotion build occuring (issue #2578)