Support form-element-path installation through rest api #629
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.
I'm running an ATH against an existing Jenkins instance running in Kubernetes. The usual workflow is to login, go through the setup wizard (once), then perform a functional test.
This PR brings a few changes to support this way of running an ATH:
form-element-path
installation through rest apiExistingJenkinsController
: Initial support for authenticated Jenkins when usingTYPE=existing
ExistingJenkinsController
: checking for form-element-path can be skipped. (this is called later)