美文网首页
jenkins自带神坑,催命鬼

jenkins自带神坑,催命鬼

作者: 螃蟹和骆驼先生Yvan | 来源:发表于2019-01-22 14:23 被阅读85次

我的jenkins之前一直都是好的,这两天莫名其妙出现一个bug,如图:

ERROR: Build step failed with exception
net.sf.json.JSONException: A JSONObject text must begin with '{' at character 0 of 
    at net.sf.json.util.JSONTokener.syntaxError(JSONTokener.java:499)
    at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:919)
    at net.sf.json.JSONObject._fromString(JSONObject.java:1145)
    at net.sf.json.JSONObject.fromObject(JSONObject.java:162)
    at net.sf.json.JSONObject.fromObject(JSONObject.java:132)
    at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryToken$1.call(DockerRegistryToken.java:143)
    at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryToken$1.call(DockerRegistryToken.java:125)
    at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
    at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryToken.newKeyMaterialFactory(DockerRegistryToken.java:125)
    at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:222)
    at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:207)
    at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:199)
    at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:455)
    at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:431)
    at com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:373)
    at com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:311)
    at com.cloudbees.dockerpublish.DockerBuilder$Perform.access$100(DockerBuilder.java:291)
    at com.cloudbees.dockerpublish.DockerBuilder.perform(DockerBuilder.java:262)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
    at hudson.model.Build$BuildExecution.build(Build.java:206)
    at hudson.model.Build$BuildExecution.doRun(Build.java:163)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
    at hudson.model.Run.execute(Run.java:1815)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:97)
    at hudson.model.Executor.run(Executor.java:429)
Build step 'Docker Build and Publish' marked build as failure
我很头疼,之后我jenkins一步一步执行配置的脚本,发现打包并没有问题,就是在打包成镜像时候报错:
  确定问题之后,我查看官方一些记录和博客终于有一些人也莫名其妙遇到这个问题:
有的人提出设想是tocken认证里面认证文件一旦错误,就不会生成新的认证文件,所以必须删除旧的认证文件才行。

解决操作步骤:
1.登录Jenkins查看信息 http://<Jenkins Address>/systemInfo
2.确定Jenkins HOME 的位置,我这里就是/var/jenkins_home
3.删除仓库认证信息 rm -f /var/jenkins_home/.dockercfg
如图我是进入容器内部删除这个配置的然后就好了

相关文章

网友评论

      本文标题:jenkins自带神坑,催命鬼

      本文链接:https://www.haomeiwen.com/subject/djvljqtx.html