-
Notifications
You must be signed in to change notification settings - Fork 5
Add global configuration for available LeapWork Controllers for job to use Configuration-as-Code plugin #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@jonbrohauge : What is the difference to #12 as there are no global configuration? |
In #12 I request that the plugin be able to be downloaded as other plugins are, via the plugins installer in Jenkins. Here request the possibility to be able to globally define the Leapworks Controller that should manage the test suites. This is to ease maintenance across teams. And when it is possible to define the Controller globally, it can be configured via Configuration-as-Code due to the expose of i.e. a getController() and a setController(). |
Ahh.. That way.. Can you update the header to something like |
As per request 😃 |
Hello @jonbrohauge , @bicschneider . |
Being able to roll this plugin out preconfigured on to multiple Jenkins instances, it'd be great if the plugin could be updated/altered/fixed to be compliant "the standard Jenkins way" so it can be configured via the plugin Configuration-as-code plugin
The text was updated successfully, but these errors were encountered: