[JIRA] [google-container-registry-auth-plugin] (JENKINS-32700) 403 Forbidden
Title: Message Title Wei Z commented on JENKINS-32700 Re: 403 Forbidden Sorry for late reply. I have been on vacation. Are you expecting this plugin to work with docker command directly? Or are you also using it with a compatible plugin like "Docker Build Step Plugin" or "CloudBees Docker Custom Build Environment Plugin"? This plugin is not implemented for use with docker command directly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-container-registry-auth-plugin] (JENKINS-31459) Null Pointer in Configure System
Title: Message Title Wei Z resolved as Fixed Should be fixed by https://github.com/jenkinsci/google-container-registry-auth-plugin/commit/46098108550a4808cd4aaf7593be77ce322ca1ce Jenkins / JENKINS-31459 Null Pointer in Configure System Change By: Wei Z Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-container-registry-auth-plugin] (JENKINS-31459) Null Pointer in Configure System
Title: Message Title Wei Z commented on JENKINS-31459 Re: Null Pointer in Configure System I am able to reproduce it. Fix is on its way. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-container-registry-auth-plugin] (JENKINS-29115) A null/empty credential will show up when trying to add credentials
Title: Message Title Wei Z closed an issue as Fixed Jenkins / JENKINS-29115 A null/empty credential will show up when trying to add credentials Change By: Wei Z Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-container-registry-auth-plugin] (JENKINS-29115) A null/empty credential will show up when trying to add credentials
Title: Message Title Wei Z resolved as Fixed Fixed by https://github.com/jenkinsci/google-container-registry-auth-plugin/pull/1 Jenkins / JENKINS-29115 A null/empty credential will show up when trying to add credentials Change By: Wei Z Status: InProgress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-container-registry-auth-plugin] (JENKINS-29115) A null/empty credential will show up when trying to add credentials
Title: Message Title Wei Z started work on JENKINS-29115 Change By: Wei Z Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-container-registry-auth-plugin] (JENKINS-29115) A null/empty credential will show up when trying to add credentials
Title: Message Title Wei Z commented on JENKINS-29115 Re: A null/empty credential will show up when trying to add credentials A fix is ready. Will be published soon. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-container-registry-auth-plugin] (JENKINS-29115) A null/empty credential will show up when trying to add credentials
Title: Message Title Wei Z created an issue Jenkins / JENKINS-29115 A null/empty credential will show up when trying to add credentials Issue Type: Bug Assignee: Wei Z Attachments: Screen Shot 2015-06-16 at 11.31.23 PM.png Components: google-container-registry-auth-plugin Created: 27/Jun/15 5:27 PM Priority: Minor Reporter: Wei Z After installing this plugin, when you tried to add credentials, you will see an empty/blank credential (or a credential that will be marked as null) in the credential selection dropdown. If you select this and then try to save, you will see a NPE whose call stack's top frames look like this: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:723) This does not affect the usage of this plugin. The credential provided by this plugin should not appear in add
[JIRA] [docker-plugin] (JENKINS-26517) Unable to download docker-java 0.10.5-SNAPSHOT
Wei Z commented on JENKINS-26517 Unable to download docker-java 0.10.5-SNAPSHOT I am wondering when this can be fixed. I am trying to use this plugin, but there is always a failure when it tries to launch a docker slave. However, I am not able to investigate further where it went wrong because I can't do a "mvn hpi:run" of this plugin due to this docker-java dependency problem, which means I can't debug what/where is wrong. I think this will be a blocking issue for many users who want to use this plugin, and it also prevents open source community to contribute to this plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-24388) Add registry authentication
Wei Z commented on JENKINS-24388 Add registry authentication I am submitting a pull request to solve the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-24388) Add registry authentication
Wei Z assigned JENKINS-24388 to Wei Z Add registry authentication Change By: Wei Z (18/Dec/14 7:17 PM) Assignee: vjuranek WeiZ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-24388) Add registry authentication
Wei Z started work on JENKINS-24388 Add registry authentication Change By: Wei Z (18/Dec/14 7:17 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-26166) PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
Wei Z
created JENKINS-26166
PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
Issue Type:
Bug
Assignee:
Wei Z
Components:
docker-build-step-plugin
Created:
18/Dec/14 7:52 PM
Description:
PullImageCommand.isImagePulled() calls
ListImage images = client.listImagesCmd().withFilters(String.format("{\"%s\":[\"true\"]}", fromImage)).exec();
Syntax wise, it is correct, however, list image currently only accept one filter now, which is dangling (whose value is true or false).
See https://docs.docker.com/reference/commandline/cli/#filtering_1,
Also see here for the docker daemon implemenation:
https://github.com/docker/docker/blob/v1.1.0/server/server.go#L668
So the above call with fromImage as the filter simply doesn't do anything, and I have also Eclipse debug out below to prove this. The below debugger output is when it hits breakpoint inside of that function. Note that "fromImage" is "wzheng2310/foo", but the returned result contains only one entry " "tutum/hello-world:latest".
his PullImageCommand (id=9570)
fromImage "wzheng2310/foo" (id=9644)
registry "" (id=9645)
tag "1" (id=9646)
client DockerClientImpl (id=9577)
images ArrayListE (id=9578)
elementData Object10 (id=9579)
0 Image (id=9582)
created 1416605801
id "7e6d00854917cab52b56fb2f2fd6300b485462c6dacf42483215c341954dacaa" (id=9584)
parentId "6853da9a3f45429aec73c2da79057ddb84af2322f874eb6a51d17ad2a4ceba61" (id=9585)
repoTags String1 (id=9586)
0 "tutum/hello-world:latest" (id=9587)
hash -1796321746
hash32 0
value (id=9588)
size 0
virtualSize 255255458
modCount 1
size 1
Environment:
Jenkins version 1.554.1, Ubuntu 14.04
Project:
Jenkins
Priority:
Minor
Reporter:
Wei Z
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-26166) PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
Wei Z started work on JENKINS-26166 PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters() Change By: Wei Z (18/Dec/14 7:53 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-26167) none default registry in PullImageCommand not working as expected
Wei Z created JENKINS-26167 none default registry in PullImageCommand not working as expected Issue Type: Bug Assignee: Wei Z Components: docker-build-publish-plugin Created: 18/Dec/14 8:24 PM Description: This is likely a bug on docker daemon, but we need a workaround. When a registry value is entered in the pull command, the current implementation will do client.pullImageCmd(fromImageRes).withTag(tagRes).withRegistry(registryRes).exec(); However, docker daemon show the following logs, which means that it still goes to the default docker hub to look for the image. Note that the POST request has QS parameter "registry=abcdef.com" in it, but docker daemon ignores it and still does: Calling GET https://index.docker.io/v1/repositories/wzheng2310/foo/images So we need a workaround for this before that issue is fixed on docker daemon side. debug server.go:1036 Calling POST /images/create info POST /images/create?tag=1fromImage=wzheng2310/fooregistry=abcdef.com d64cc68b +job pull(wzheng2310/foo, 1) debug session.go:259 registry Calling GET https://index.docker.io/v1/repositories/wzheng2310/foo/images debug http.go:162 https://index.docker.io/v1/repositories/wzheng2310/foo/images HEADERS: map[User-Agent:docker/1.2.0 go/go1.3.1 git-commit/fa7b24f kernel/3.13.0-43-generic os/linux arch/amd64] debug server.go:1036 Calling GET /images/json info GET /images/json?all=0filters=%7B%22wzheng2310%2Ffoo%22:%5B%22true%22%5D%7D d64cc68b +job images() d64cc68b -job images() = OK (0) debug pull.go:89 Retrieving the tag list debug http.go:162 https://registry-1.docker.io/v1/repositories/wzheng2310/foo/tags HEADERS: map[User-Agent:docker/1.2.0 go/go1.3.1 git-commit/fa7b24f kernel/3.13.0-43-generic os/linux arch/amd64] debug session.go:214 Got status code 200 from https://registry-1.docker.io/v1/repositories/wzheng2310/foo/tags Environment: Jenkins 1.554.1, Ubuntu 14.04 Project: Jenkins Priority: Minor Reporter: Wei Z This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-26167) none default registry in PullImageCommand not working as expected
Wei Z started work on JENKINS-26167 none default registry in PullImageCommand not working as expected Change By: Wei Z (18/Dec/14 8:24 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-26166) PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
Wei Z commented on JENKINS-26166 PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters() Below is some console log that I added inside of isImagePulled() function to illustrate the problem better. Docker INFO: Pulling image wzheng2310/foo:1 Docker INFO: isImagePulled: images size is 3 Docker INFO: isImagePulled: image is wzheng2310/foo:1 Docker INFO: isImagePulled: image is wzheng2310/foo:latest Docker INFO: isImagePulled: image is wei_private_repo/container-2:latest Docker INFO: isImagePulled: image is ..com/wei_private_repo/container-1:1 Docker INFO: isImagePulled: image is ..com/wei_private_repo/container-1:latest Docker INFO: isImagePulled: image is ..com/wei_private_repo/container-2:1 Docker INFO: isImagePulled: image is ..com/wei_private_repo/container-2:2 Docker INFO: isImagePulled: image is wei_private_repo/container-1:latest Docker INFO: isImagePulled: image is debian:jessie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
