Add a step for executing a control task #53
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fhervieux
force-pushed
the
control-tasks
branch
from
ec9188e to
c7799ec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds a Jenkins Pipeline steps for executing a control task. It takes a host id, a control task name, and optional parameters. The task is executed with the same code than for the deployments.
I had to upgrade the dependencies to XL Deploy libraries for it to work as executing tasks on the previous version resulted in an exception: java.lang.ClassCastException: com.xebialabs.deployit.engine.api.dto.ValidatedConfigurationItem cannot be cast to java.lang.String