Skip to content
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

Minor issue with Jenkins.__init__ in specialized_api #17

Closed
lechat opened this issue Jul 25, 2014 · 1 comment
Closed

Minor issue with Jenkins.__init__ in specialized_api #17

lechat opened this issue Jul 25, 2014 · 1 comment

Comments

@lechat
Copy link
Collaborator

lechat commented Jul 25, 2014

Hi,

Coming from use of jenkinsapi, I expected that Jenkins.__init__ parameters would be in the same order as ones in jenkinsapi. Apparently they are not. I think it would be a bit better to have the same order of params as in jenkinsapi: url, username, password and extra params would go next.

Aleksey

@lhupfeldt
Copy link
Owner

Hi Aleksey,

jenkinsflow has not supported direct use of jenkinsapifor a while. To use jenkinsapi you must use the jenkinsapi_wrapper supplied with jenkinsflow. That has the same order of common arguments as specialized_api and script_api. Note that __init__ should always be called with named arguments though.

Regards
Lars

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

2 participants