Parse the arguments of an execution and make it available inside Rundeck object #3
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
…eckExecution object
|
Vincent Behar » rundeck-api-java-client #3 SUCCESS |
gschueler
added a commit
to gschueler/rundeck-api-java-client
that referenced
this pull request
Apr 20, 2015
Refactor to use builders for trigger/run methods fixes #2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi,
Here is an improvement of the API in order to retrieve the optional execution parameters and store them in a map. I'm using this feature inside the Jenkins rundeck plugin, in order to expose the execution parameters as environment variable (I'll make a pull request using 2.1-SNAPSHOT very soon).
Could you consider merging my change if it suits you?
Thanks,
Reynald