-
Bug
-
Resolution: Unresolved
-
Minor
-
None
After upgrading to 1.7.3 version of this plugin, new parameter showed up:
configure block level ( ) block on global level ( ) block on node level
Unfortunately none of the options is selected by default, so that all of our configured jobs simply do not block at all.
It would be nice to provide default value equivalent to behavior prior version 1.7.3.
Workaround is obviously to set some option for all broken jobs.
[JENKINS-32531] Missing default value for configure block level setting
Michal Ševčenko
created issue -
Michal Ševčenko
made changes -
| Description |
Original:
After upgrading to 1.7.3 version of this plugin, new parameter showed up: {quote}configure block level ( ) block on global level ( ) block on node level{quote} Unfortunately the none of the options is selected by default, so that all of our configured jobs simply does not block at all. It would be nice to provide default value equivalent to behavior prior version 1.7.3. Workaround is obviously to set some option for all broken jobs. |
New:
After upgrading to 1.7.3 version of this plugin, new parameter showed up: {quote}configure block level ( ) block on global level ( ) block on node level{quote} Unfortunately none of the options is selected by default, so that all of our configured jobs simply does not block at all. It would be nice to provide default value equivalent to behavior prior version 1.7.3. Workaround is obviously to set some option for all broken jobs. |
Michal Ševčenko
made changes -
| Description |
Original:
After upgrading to 1.7.3 version of this plugin, new parameter showed up: {quote}configure block level ( ) block on global level ( ) block on node level{quote} Unfortunately none of the options is selected by default, so that all of our configured jobs simply does not block at all. It would be nice to provide default value equivalent to behavior prior version 1.7.3. Workaround is obviously to set some option for all broken jobs. |
New:
After upgrading to 1.7.3 version of this plugin, new parameter showed up: {quote}configure block level ( ) block on global level ( ) block on node level{quote} Unfortunately none of the options is selected by default, so that all of our configured jobs simply do not block at all. It would be nice to provide default value equivalent to behavior prior version 1.7.3. Workaround is obviously to set some option for all broken jobs. |
| Workflow | Original: JNJira [ 168174 ] | New: JNJira + In-Review [ 182994 ] |
I just found out that this is problem not only by migration to new version, but also of the UI itself. The UI does neither preset any value for the option, nor validates that some option is set. So if the user only checks that job should be blocking, without setting the parameter, job does not block.