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

Utility forces http (no SSL support?) #4

Open
mtdeguzis opened this issue Jun 15, 2018 · 6 comments
Open

Utility forces http (no SSL support?) #4

mtdeguzis opened this issue Jun 15, 2018 · 6 comments

Comments

@mtdeguzis
Copy link

Description

Jenkins can and should be run over SSL/https. This utility does not allow you to specify https. Does it handle the protocol?

./butler jobs export --server https://myhost:port--username mtdeguzis --password $(read -s password && echo $password)

Get http://https//myhost:port/view/all/api/xml: dial tcp: lookup https on *************:53: no such host

Related Issue

Changes proposed

Screenshots

@kcwhite
Copy link

kcwhite commented Aug 10, 2018

Agreed, having the same problem.

@mtdeguzis
Copy link
Author

Ended up writing my own for the time being that targets any cluster Jenkins node, can remove/disable/enable a job on either side.

@kcwhite
Copy link

kcwhite commented Aug 13, 2018

Nice. Are you able to share the code?

@mtdeguzis
Copy link
Author

I'll see if I can get it approved

@icereed
Copy link
Contributor

icereed commented Nov 14, 2018

This would be solved in #6.

@sunkarakamal
Copy link

sunkarakamal commented Dec 10, 2018

is there any way to pass nocertificatecheck parameter ,since our Jenkins uses self signed when i run butler command it says "Get https://xxxxxx8443/api/xml: x509: certificate signed by unknown authority"

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

4 participants