Make JobStepCreator
fields more consistent through the api
#3759
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief description of the PR.
This PR makes the
jobStepProperties
more consistent through the api.Related Issue
This PR fixes #3580.
Description of the solution adopted
Before the changes the following were the getter and setter methods of the
JobStepCreator
getStepProperties
setJobStepProperties
After the changes the getter and setter methods of the
JobStepCreator
are:getStepProperties
setStepProperties
: to use instead of the oldsetJobStepProperties
setJobStepProperties
: deprecated, left there only to ensure backward compatibilitygetJobStepPropertiesDeprecated
: deprecated, left there only to ensure backward compatibilitysetJobStepPropertiesDeprecated
: deprecated, left there only to ensure backward compatibilityAny side note on the changes made
JobStepCreator
will be the following:stepProperties
andjobStepProperties
will be present and functional, even if the latter is deprecated.