-
Notifications
You must be signed in to change notification settings - Fork 165
[JENKINS-27045] Jenkins CLI --username/--password options #77
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
Conversation
86e2f73
to
b751298
Compare
@i386 any idea why my Jenkins builds are getting out of memory errors like https://jenkins.ci.cloudbees.com/job/plugins/job/github-oauth-plugin/332/console ?
|
More out of memory woes. -> https://jenkins.ci.cloudbees.com/job/plugins/job/github-oauth-plugin/335/console Builds just fine locally for me. |
d9f6ee0
to
3f64c19
Compare
Controlled the memory issue by adding |
d96bebc
to
479c063
Compare
options. Here's an example: java -jar jenkins-cli.jar -s http://localhost:8080 -noKeyAuth who-am-i \ --username samrocketman --password-file ./personal-access-token Unfortunately, Jenkins core prevents Jenkins CLI LoginCommand from working correctly because it only stores the Username and mishandles creating the authentication token. This is a [bug in core][1]. [1]: https://github.com/jenkinsci/jenkins/blob/jenkins-2.47/core/src/main/java/hudson/cli/ClientAuthenticationCache.java#L65-L75
479c063
to
e5858c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Here's an example:
Unfortunately, Jenkins core prevents Jenkins CLI LoginCommand from working correctly because it only stores the Username and mishandles creating the authentication token. This is a bug in core.