Skip to content

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

Open
jonbrohauge opened this issue Oct 4, 2018 · 5 comments

Comments

@jonbrohauge
Copy link

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

@bicschneider
Copy link
Contributor

@jonbrohauge : What is the difference to #12 as there are no global configuration?

@jonbrohauge
Copy link
Author

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().

@bicschneider
Copy link
Contributor

Ahh.. That way.. Can you update the header to something like Add global configuration for available LeapWork Controllers for job to use..
When implemented it should of course also support Configuration-as-Code..

@jonbrohauge jonbrohauge changed the title Allow for use in Configuration-as-Code plugin Add global configuration for available LeapWork Controllers for job to use Configuration-as-Code plugin Oct 24, 2018
@jonbrohauge
Copy link
Author

As per request 😃

@romanchetto
Copy link
Contributor

Hello @jonbrohauge , @bicschneider .
Thank you for your advice, we will try to do this in the future release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants