-
Notifications
You must be signed in to change notification settings - Fork 2
Conversation
@@ -25,11 +25,10 @@ flow-definition.description = description | |||
|
|||
com.tikal.jenkins.plugins.multijob.MultiJobProject.description = description | |||
|
|||
hudson.plugins.buildblocker.BuildBlockerProperty = blockOn | |||
hudson.plugins.buildblocker.BuildBlockerProperty.type = com.adq.jenkins.xmljobtodsl.dsl.strategies.custom.DSLBlockOnStrategy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need the custom type? what does it do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a custom type, the buildBlockerProperty is currently being skipped over during translation:
description("Test")
keepDependencies(false)
properties {
LeastLoadDisabledProperty {
leastLoadDisabled(false)
}
naginatorOptOutProperty {
optOut(false)
}
heavyJobProperty {
weight(1)
}
throttleConcurrentBuilds()
}
There is a blockOn property though. Checked these docs and it doesn't seem to be deprecated. Maybe both should be available
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just mean, what is the code in the custom type doing? Do we need to try to preserve that or can we delete those files? is it being used for something else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The custom type looks like it's meant to create a similar block under the blockOn property. It gets the following properties by their name: useBuildBlocker, blocking jobs, blockLevel, scanQueueFor and formats them as inner methods and parameters in order to return the DSL. This is the only place the custom type is being used so we may be able to delete, but should we still make sure the blockOn property is supported? Or is useBuildBlocker, which is the dynamic dsl, used in place of that ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm fine with this, we can check later what's up with blockOn
Ticket
JIRA-2881
Overview
buildblocker attribute is currently labeled as blockOn and as a custom type. Changing buildBlockerProperties to match Job DSL plugin
Testing
Test XML Used:
DSL Output: