[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao started work on JENKINS-60343 Change By: Marslo Jiao Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203357.1575290252000.8157.1576491720187%40Atlassian.JIRA.
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao Labels: container kubernetes kubernetes- plugin plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203357.1575290252000..1575961800164%40Atlassian.JIRA.
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao The docker images is using the specific user/group and home. The exact same Docker image works in * {{containerTemplate}} * , but will failed in {{ * Yaml syntax * as below:}} {code:java}java.nio.file.AccessDeniedException: /home/jenkins at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at hudson.FilePath.mkdirs(FilePath.java:3256) at hudson.FilePath.access$1300(FilePath.java:211) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1251) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1247) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3069) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748){code}{noformat}Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.12.56/10.244.12.56:58580 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1069) at hudson.FilePath.act(FilePath.java:1058) at hudson.FilePath.mkdirs(FilePath.java:1243) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:181) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:332) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:321) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:177) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286) at org.jenkinsci.plugins.workfl
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao Labels: plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203357.1575290252000.3332.1575961740372%40Atlassian.JIRA.
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao The docker images is using the specific user/group and home. The exact same Docker image works in {{containerTemplate}}, but will failed in {{Yaml syntax as below:}} { code:java}java.nio.file.AccessDeniedException: /home/jenkins at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at hudson.FilePath.mkdirs(FilePath.java:3256) at hudson.FilePath.access$1300(FilePath.java:211) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1251) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1247) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3069) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748){code}{ noformat}Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.12.56/10.244.12.56:58580 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1069) at hudson.FilePath.act(FilePath.java:1058) at hudson.FilePath.mkdirs(FilePath.java:1243) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:181) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:332) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:321) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:177) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsc
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao The docker images is using the specific user/group and home. The exact same Docker image works in {{containerTemplate}}, but will failed in {{Yaml syntax as below:}} {noformat}Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.12.56/10.244.12.56:58580 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1069) at hudson.FilePath.act(FilePath.java:1058) at hudson.FilePath.mkdirs(FilePath.java:1243) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:181) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:332) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:321) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:177) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao The docker images is using the specific user/group and home. The exact same Docker image works in {{containerTemplate}}, but will failed in {{Yaml syntax as below :}} {noformat} Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.12.56/10.244.12.56:58580 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1069) at hudson.FilePath.act(FilePath.java:1058) at hudson.FilePath.mkdirs(FilePath.java:1243) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:181) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:332) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:321) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:177) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMe
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao Summary: java.nio.file.AccessDeniedException : /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203357.1575290252000.2762.1575869580091%40Atlassian.JIRA.
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao The docker images is using the specific user/group and home. The exact same Docker image works in {{containerTemplate}}, but will failed in {{Yaml syntax:}} {noformat}// Dockerfile...ARG user=devopsARG group=${user}ARG uid=1000ARG gid=${uid}ENV HOME=/home/${user}...{noformat} h3. Jenkinsfile for {{containerTemplate}}: {noformat}podTemplate(cloud: ' DevOps My Kubernetes', containers: [ containerTemplate(name: 'jnlp',image: 'my.artifactory.com/my-jnlp:1.0',ttyEnabled: true,privileged: false,alwaysPullImage: false,workingDir: '/home/devops',resourceRequestCpu: '256m',resourceLimitCpu: '512m',resourceRequestMemory: '512Mi',resourceLimitMemory: '1024Mi' )]) { node(POD_LABEL) {stage ('info') { echo 'yes!' sh """idwhoamiecho ${WORKSPACE}realpath ${WORKSPACE} """} }}{noformat}h3. Jenkinfile for {{Yaml syntax}}:{noformat}podTemplate( cloud: ' DevOps My Kubernetes', showRawYaml: true, namespace: 'devops-ci', yaml: """apiVersion: v1kind: Podspec: containers: - name: jnlpimage: 'my.artifactory.com/my-jnlp:1.0'workingDir: '/home/devops'resources: limits:memory: "1024Mi"cpu: "512m" requests:memory: "512Mi"cpu: "256m" """) { node(POD_LABEL) { container('jnlp') {stage('Run shell') { sh """idwhoamiecho ${WORKSPACE}realpath ${WORKSPACE} """} }}}{noformat}h3. Results:{{containerTemplate}} works perfect by specific {color:#00875a}{{workingDir}}{color}: {noformat}[Pipeline] Start of Pipeline[Pipeline] podTemplate[Pipeline] {[Pipeline] nodeStill waiting to schedule task‘Jenkins’ doesn’t have label ‘container-test_6-95vj1’Agent container-test-6-95vj1-rbxr4-lrlqc is provisioned from template Kubernetes Pod Template---apiVersion: "v1"kind: "Pod"metadata: annotations:buildUrl: "http://my-jenkins.my-ci.svc.cluster.local:8080/job/container-test/6/" labels:jenkins: "slave"jenkins/container-test_6-95vj1: "true" name: "container-test-6-95vj1-rbxr4-lrlqc"spec: containers: - env:- name: "JENKINS_SECRET" value: ""- name: "JENKINS_TUNNEL" value: "my-jenkins.my-ci.svc.cluster.local:5"- name: "JENKINS_AGENT_NAME" value: "container-test-6-95vj1-rbxr4-lrlqc"- name: "JENKINS_NAME" value: "container-test-6-95vj1-rbxr4-lrlqc"- name: "JENKINS_AGENT_WORKDIR" value: "/home/devops"- name: "JENKINS_URL" value: "http://my-jenkins.my-ci.svc.cluster.local:8080/"image: "my.artifactory.com/my-jnlp:1.0"imagePullPolicy: "IfNotPresent"name: "jnlp"resources: limits:memory: "1024Mi"cpu: "512m" requests:memory: "512Mi"cpu: "256m"securityCo
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao The docker images is using the specific user/group and home. The exact same Docker image works in {{containerTemplate}}, but will failed in {{Yaml syntax:}} {noformat}// Dockerfile...ARG user=devopsARG group=${user}ARG uid=1000ARG gid=${uid}ENV HOME=/home/${user}...{noformat} h3. Jenkinsfile for {{containerTemplate}}: {noformat}podTemplate(cloud: 'DevOps Kubernetes', containers: [ containerTemplate(name: 'jnlp',image: 'my.artifactory.com/my-jnlp:1.0',ttyEnabled: true,privileged: false,alwaysPullImage: false,workingDir: '/home/devops',resourceRequestCpu: '256m',resourceLimitCpu: '512m',resourceRequestMemory: '512Mi',resourceLimitMemory: '1024Mi' )]) { node(POD_LABEL) {stage ('info') { echo 'yes!' sh """idwhoamiecho ${WORKSPACE}realpath ${WORKSPACE} """} }}{noformat}h3. Jenkinfile for {{Yaml syntax}}:{noformat}podTemplate( cloud: 'DevOps Kubernetes', showRawYaml: true, namespace: ' wukong devops -ci', yaml: """apiVersion: v1kind: Podspec: containers: - name: jnlpimage: 'my.artifactory.com/my-jnlp:1.0'workingDir: '/home/devops'resources: limits:memory: "1024Mi"cpu: "512m" requests:memory: "512Mi"cpu: "256m" """) { node(POD_LABEL) { container('jnlp') {stage('Run shell') { sh """idwhoamiecho ${WORKSPACE}realpath ${WORKSPACE} """} }}}{noformat}h3. Results:{{containerTemplate}} works perfect by specific {color:#00875a}{{workingDir}}{color}: {noformat}[Pipeline] Start of Pipeline[Pipeline] podTemplate[Pipeline] {[Pipeline] nodeStill waiting to schedule task‘Jenkins’ doesn’t have label ‘container-test_6-95vj1’Agent container-test-6-95vj1-rbxr4-lrlqc is provisioned from template Kubernetes Pod Template---apiVersion: "v1"kind: "Pod"metadata: annotations:buildUrl: "http://my-jenkins.my-ci.svc.cluster.local:8080/job/container-test/6/" labels:jenkins: "slave"jenkins/container-test_6-95vj1: "true" name: "container-test-6-95vj1-rbxr4-lrlqc"spec: containers: - env:- name: "JENKINS_SECRET" value: ""- name: "JENKINS_TUNNEL" value: "my-jenkins.my-ci.svc.cluster.local:5"- name: "JENKINS_AGENT_NAME" value: "container-test-6-95vj1-rbxr4-lrlqc"- name: "JENKINS_NAME" value: "container-test-6-95vj1-rbxr4-lrlqc"- name: "JENKINS_AGENT_WORKDIR" value: "/home/devops"- name: "JENKINS_URL" value: "http://my-jenkins.my-ci.svc.cluster.local:8080/"image: "my.artifactory.com/my-jnlp:1.0"imagePullPolicy: "IfNotPresent"name: "jnlp"resources: limits:memory: "1024Mi"cpu: "512m" requests:memory: "512Mi"cpu: "256m"securityCon
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao The docker images is using the specific user/group and home. The exact same Docker image works in {{containerTemplate}}, but will failed in {{Yaml syntax:}} {noformat}// Dockerfile...ARG user=devopsARG group=${user}ARG uid=1000ARG gid=${uid}ENV HOME=/home/${user}...{noformat} h3. Using Jenkinsfile for {{containerTemplate}}: {noformat}podTemplate(cloud: 'DevOps Kubernetes', containers: [ containerTemplate(name: 'jnlp',image: 'my.artifactory.com/my-jnlp:1.0',ttyEnabled: true,privileged: false,alwaysPullImage: false,workingDir: '/home/devops',resourceRequestCpu: '256m',resourceLimitCpu: '512m',resourceRequestMemory: '512Mi',resourceLimitMemory: '1024Mi' )]) { node(POD_LABEL) {stage ('info') { echo 'yes!' sh """idwhoamiecho ${WORKSPACE}realpath ${WORKSPACE} """} }}{noformat} h3. The Jenkinfile for {{Yaml syntax}}: {noformat}podTemplate( cloud: 'DevOps Kubernetes', showRawYaml: true, namespace: 'wukong-ci', yaml: """apiVersion: v1kind: Podspec: containers: - name: jnlpimage: 'my.artifactory.com/my-jnlp:1.0'workingDir: '/home/devops'resources: limits:memory: "1024Mi"cpu: "512m" requests:memory: "512Mi"cpu: "256m" """) { node(POD_LABEL) { container('jnlp') {stage('Run shell') { sh """idwhoamiecho ${WORKSPACE}realpath ${WORKSPACE} """} }}}{noformat} h3. results Results :{{containerTemplate }} works perfect by specific {color:# FF 00875a }{{workingDir}}{color}: {noformat}[Pipeline] Start of Pipeline[Pipeline] podTemplate[Pipeline] {[Pipeline] nodeStill waiting to schedule task‘Jenkins’ doesn’t have label ‘container-test_6-95vj1’Agent container-test-6-95vj1-rbxr4-lrlqc is provisioned from template Kubernetes Pod Template---apiVersion: "v1"kind: "Pod"metadata: annotations:buildUrl: "http://my-jenkins.my-ci.svc.cluster.local:8080/job/container-test/6/" labels:jenkins: "slave"jenkins/container-test_6-95vj1: "true" name: "container-test-6-95vj1-rbxr4-lrlqc"spec: containers: - env:- name: "JENKINS_SECRET" value: ""- name: "JENKINS_TUNNEL" value: "my-jenkins.my-ci.svc.cluster.local:5"- name: "JENKINS_AGENT_NAME" value: "container-test-6-95vj1-rbxr4-lrlqc"- name: "JENKINS_NAME" value: "container-test-6-95vj1-rbxr4-lrlqc"- name: "JENKINS_AGENT_WORKDIR" value: "/home/devops"- name: "JENKINS_URL" value: "http://my-jenkins.my-ci.svc.cluster.local:8080/"image: "my.artifactory.com/my-jnlp:1.0"imagePullPolicy: "IfNotPresent"name: "jnlp"resources: limits:memory: "1024Mi"cpu: "512m" requests:
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao moved an issue Jenkins / JENKINS-60343 java.nio.file.AccessDeniedException for specific workingDir during NodeProvision by kubernetes yaml syntax Change By: Marslo Jiao Project: Infrastructure Jenkins Key: INFRA JENKINS - 2370 60343 Workflow: classic default workflow JNJira + In-Review Component/s: kubernetes-plugin Component/s: docker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-50714 SonarQube Scanner 2.7 blocks Jenkins start Change By: Marslo Jiao SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.] The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for. !Screen Shot 2018-04-10 at 17.47.30.png|width=1000! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists { quote noformat } $ sudo /etc/init.d/jenkins stop Correct java version found [ ok ] Stopping jenkins (via systemctl): jenkins.service. appadmin jenkins @Jenkins:~$ ps aux | grep jenkins jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid – /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL= [ http://www.myjenkins.com |http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL= [ http://www.myjenkins.com |http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 $ sudo /etc/init.d/jenkins start Correct java version found [ ok ]
[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-50714 SonarQube Scanner 2.7 blocks Jenkins start Change By: Marslo Jiao SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.] The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for. !Screen Shot 2018-04-10 at 17.47.30.png|width=1000! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists{quote} {{ $ sudo /etc/init.d/jenkins stop }} {{ Correct java version found }} {{ [ ok ] Stopping jenkins (via systemctl): jenkins.service. }} {{ appadmin@Jenkins:~$ ps aux | grep jenkins }} {{ jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid – /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=[http://www.myjenkins.com|http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 }} {{ jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=[http://www.myjenkins.com|http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 }} {{ $ sudo /etc/init.d/jenkins start }} {{ Correct j
[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-50714 SonarQube Scanner 2.7 blocks Jenkins start Change By: Marslo Jiao SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.] The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for. !Screen Shot 2018-04-10 at 17.47.30.png|width=1000! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists { quote} { { $ sudo /etc/init.d/jenkins stop}} {{Correct java version found}} {{[ ok ] Stopping jenkins (via systemctl): jenkins.service.}} {{appadmin@Jenkins:~$ ps aux | grep jenkins}} {{jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid – /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=[http://www.myjenkins.com|http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}} {{jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=[http://www.myjenkins.com|http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}} {{$ sudo /etc/init.d/jenkins start}} {{Correct java version found}} {{[
[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-50714 SonarQube Scanner 2.7 blocks Jenkins start Change By: Marslo Jiao SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.] The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for. !Screen Shot 2018-04-10 at 17.47.30.png|width= 500 1000 ! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists{{$ sudo /etc/init.d/jenkins stop}}{{Correct java version found}}{{[ ok ] Stopping jenkins (via systemctl): jenkins.service.}}{{appadmin@Jenkins:~$ ps aux | grep jenkins}}{{jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid -- – /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL= [ http://www.myjenkins.com |http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}}{{jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL= [ http://www.myjenkins.com |http://www.myjenkins.com/] -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}} {{$ sudo /etc/init.d/jenkins start}}{{Correct java version found}}{{[
[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-50714 SonarQube Scanner 2.7 blocks Jenkins start Change By: Marslo Jiao SonarQube Scanner plugin location: [https://plugins.jenkins.io/sonar.] The Jenkins shows:Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for. !Screen Shot 2018-04-10 at 17.47.30.png |width=500 ! The /var/log/jenkins/jenkins.log has been attached: [^jenkins.log] Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists{{$ sudo /etc/init.d/jenkins stop}}{{Correct java version found}}{{[ ok ] Stopping jenkins (via systemctl): jenkins.service.}}{{appadmin@Jenkins:~$ ps aux | grep jenkins}}{{jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid -- /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=http://www.myjenkins.com -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}}{{jenkins 1456 40.3 4.9 16679712 1629084 ? Sl 17:50 3:11 /usr/bin/java -Djava.awt.headless=true -Xms512m -Xmx10240m -XX:PermSize=512m -XX:MaxPermSize=10240m -Dhttp.nonProxyHosts=blackduck.mycompany.com -Dhttps.nonProxyHosts=blackduck.mycompany.com -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=utf-8 -Djavax.net.ssl.keyStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/opt/java/jdk1.8.0_131/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Dhudson.footerURL=http://www.myjenkins.com -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ; -Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080}} {{$ sudo /etc/init.d/jenkins start}}{{Correct java version found}}{{[ ok ] Starting jenkins (via systemctl): jenkins.service.}}{{$ ps aux | grep j
[JIRA] (JENKINS-50714) SonarQube Scanner 2.7 blocks Jenkins start
Title: Message Title Marslo Jiao created an issue Jenkins / JENKINS-50714 SonarQube Scanner 2.7 blocks Jenkins start Issue Type: Bug Assignee: Sonar Team Attachments: jenkins.log, Screen Shot 2018-04-10 at 17.47.30.png Components: sonar Created: 2018-04-10 10:33 Environment: OS: Ubuntu 16.04 LTS. (4.4.0-116-generic #140-Ubuntu) JRE/JDK: 1.8.0_131 Jenkins Master: 2.114 Web Browser: Chrome 65.0.3325.181 Jenkins Installation: sudo apt install jenkins SonarQube Scanner: upgrade from 2.6.1 -> 2.7 Labels: sonar sonarqube plugin startup Priority: Blocker Reporter: Marslo Jiao SonarQube Scanner plugin location: https://plugins.jenkins.io/sonar. The Jenkins shows: Please Wait while Jenkins is getting ready to work But it will not getting to work no matter how long you are waiting for. The /var/log/jenkins/jenkins.log has been attached: jenkins.log Jenkins service cannot be stopped correctly also. And if restart Jenkins services after stopped. there's multi-services will exists $ sudo /etc/init.d/jenkins stop Correct java version found [ ok ] Stopping jenkins (via systemctl): jenkins.service. appadmin@Jenkins:~$ ps aux | grep jenkins jenkins 1455 0.0 0.0 18848 188 ? S 17:50 0:00 /usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/home/jenkins/jenkins_master --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid – /usr/
[JIRA] (JENKINS-42564) App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException)
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-42564 App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException) Change By: Marslo Jiao * Jenkins Master : # of executors: 0 * Build app succeed and also can be archived. The HockeyApp Path:_*App File (.ipa, .app.zip, .apk)*: *app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk*_Upload Error:_Uploading to HockeyApp..._ _/tmp/jtf7699425629259393086.tmp/xxx-14-debug.apk_ _java.lang.NullPointerException_ _at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)_ _at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)_ _at org.apache.http.impl.client.BasicCredentialsProvider.setCredentials(BasicCredentialsProvider.java:61)_ _at hockeyapp.HockeyappRecorder.createPreconfiguredHttpClient(HockeyappRecorder.java:165)_ _at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:252)_ _at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:204)_ _at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)_ _at hudson.model.Build$BuildExecution.post2(Build.java:185)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)_ _at hudson.model.Run.execute(Run.java:1753)_ _at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)_ _at hudson.model.ResourceController.execute(ResourceController.java:98)_ _at hudson.model.Executor.run(Executor.java:404)_ I've checked the Jenkins Master, and there's no folder like /_tmp_/jtf*.tmp folderBut When I downgrade the HockeyApp plugin to [1.2.1|http://ftp.icm.edu.pl/packages/jenkins/plugins/hockeyapp/1.2.1/hockeyapp.hpi], the application can be uploaded succeed with the exact same configuration. And the file can be found at JenkinsMarslo: _/tmp/jft*._tmp folder also._ _---_The second attempted:Change the *_App File (.ipa, .app.zip, .apk)_*: *_{color:#ff}**/**{color}/xxx-17-$\{BUILD_TYPE}.apk_*Error:_Uploading to HockeyApp..._ _No IPA/APK found to upload in: **/**/xxx-17-$\{BUILD_TYPE}.apk_ —The third attempted:Change the *__App File (.ipa, .app.zip, .apk): {color:#ff}$\{WORKSPACE}{color}/app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk__*Error:_Uploading to HockeyApp..._ _java.io.IOException: remote file operation failed: /home/salve/workspace/-job at hudson.remoting.Channel@b31cdf8:slave: java.io.IOException: Expecting Ant GLOB pattern, but saw '/home/slave/workspace/-job/app/build/outputs/apk/xxx-13-debug.apk'. See [http://ant.apache.org/manual/Types/fileset.html] for syntax_ _at hudson.FilePath.act(FilePath.java:992)_ _at hudson.FilePath.act(FilePath.java:974)_ _at hudson.FilePath.list(FilePath.java:1719)_ _at hudson.FilePath.list(FilePath.java:1704)_ _at hudson.FilePath.list(FilePath.java:1690)_ _at hockeyapp.HockeyappRecorder.performForAppli
[JIRA] (JENKINS-42564) App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException)
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-42564 App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException) Change By: Marslo Jiao Jenkins Master # of executors: 0Build app succeed and also can be archived. The HockeyApp Path:_*App File (.ipa, .app.zip, .apk)*: *app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk*_Upload Error:_Uploading to HockeyApp..._ _/tmp/jtf7699425629259393086.tmp/xxx-14-debug.apk_ _java.lang.NullPointerException_ _at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)_ _at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)_ _at org.apache.http.impl.client.BasicCredentialsProvider.setCredentials(BasicCredentialsProvider.java:61)_ _at hockeyapp.HockeyappRecorder.createPreconfiguredHttpClient(HockeyappRecorder.java:165)_ _at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:252)_ _at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:204)_ _at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)_ _at hudson.model.Build$BuildExecution.post2(Build.java:185)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)_ _at hudson.model.Run.execute(Run.java:1753)_ _at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)_ _at hudson.model.ResourceController.execute(ResourceController.java:98)_ _at hudson.model.Executor.run(Executor.java:404)_ I've checked the Jenkins Master, and there's no folder like /_tmp_/jtf*.tmp folderBut When I downgrade the HockeyApp plugin to [1.2.1|http://ftp.icm.edu.pl/packages/jenkins/plugins/hockeyapp/1.2.1/hockeyapp.hpi], the application can be uploaded succeed with the exact same configuration. And the file can be found at JenkinsMarslo: _/tmp/jft*._tmp folder also._ _---_The second attempted:Change the *_App File (.ipa, .app.zip, .apk)_*: *_{color:#ff}**/**{color}/xxx-17-$\{BUILD_TYPE}.apk_*Error:_Uploading to HockeyApp..._ _No IPA/APK found to upload in: **/**/ Copd xxx -17-$\{BUILD_TYPE}.apk_ --- — The third attempted:Change the *__App File (.ipa, .app.zip, .apk): {color:#ff}$\{WORKSPACE}{color}/app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk__*Error:_Uploading to HockeyApp..._ _java.io.IOException: remote file operation failed: /home/salve/workspace/-job at hudson.remoting.Channel@b31cdf8:slave: java.io.IOException: Expecting Ant GLOB pattern, but saw '/home/slave/workspace/-job/app/build/outputs/apk/xxx-13-debug.apk'. See [http://ant.apache.org/manual/Types/fileset.html] for syntax_ _at hudson.FilePath.act(FilePath.java:992)_ _at hudson.FilePath.act(FilePath.java:974)_ _at hudson.FilePath.list(FilePath.java:1719)_ _at hudson.FilePath.list(FilePath.java:1704)_ _at hudson.FilePath.list(FilePath.java:1690)_ _at hockeyapp.HockeyappRecorder.performForA
[JIRA] (JENKINS-42564) App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException)
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-42564 App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException) Change By: Marslo Jiao Jenkins Master # of executors: 0Build app succeed and also can be archived. The HockeyApp Path:_*App File (.ipa, .app.zip, .apk)*: *app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk*_Upload Error:_Uploading to HockeyApp..._ _/tmp/jtf7699425629259393086.tmp/xxx-14-debug.apk_ _java.lang.NullPointerException_ _at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)_ _at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)_ _at org.apache.http.impl.client.BasicCredentialsProvider.setCredentials(BasicCredentialsProvider.java:61)_ _at hockeyapp.HockeyappRecorder.createPreconfiguredHttpClient(HockeyappRecorder.java:165)_ _at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:252)_ _at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:204)_ _at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)_ _at hudson.model.Build$BuildExecution.post2(Build.java:185)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)_ _at hudson.model.Run.execute(Run.java:1753)_ _at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)_ _at hudson.model.ResourceController.execute(ResourceController.java:98)_ _at hudson.model.Executor.run(Executor.java:404)_ I've checked the Jenkins Master, and there's no folder like _ /_tmp_/jtf*.tmp ._ folder But When I downgrade the HockeyApp plugin to [1.2.1|http://ftp.icm.edu.pl/packages/jenkins/plugins/hockeyapp/1.2.1/hockeyapp.hpi], the application can be uploaded succeed with the exact same configuration. And the file can be found at JenkinsMarslo: _/tmp/jft*._tmp folder also._ _ — _---_ The second attempted:Change the *_App File (.ipa, .app.zip, .apk)_*: *_{color:#ff}**/**{color}/xxx-17-$\{BUILD_TYPE}.apk_*Error:_Uploading to HockeyApp..._ _No IPA/APK found to upload in: **/**/Copd-17-$\{BUILD_TYPE}.apk_ — --- The third attempted:Change the *__App File (.ipa, .app.zip, .apk): {color:#ff}$\{WORKSPACE}{color}/app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk__*Error:_Uploading to HockeyApp..._ _java.io.IOException: remote file operation failed: /home/salve/workspace/-job at hudson.remoting.Channel@b31cdf8:slave: java.io.IOException: Expecting Ant GLOB pattern, but saw '/home/slave/workspace/-job/app/build/outputs/apk/xxx-13-debug.apk'. See [http://ant.apache.org/manual/Types/fileset.html] for syntax_ _at hudson.FilePath.act(FilePath.java:992)_ _at hudson.FilePath.act(FilePath.java:974)_ _at hudson.FilePath.list(FilePath.java:1719)_ _at hudson.FilePath.list(FilePath.java:1704)_ _at hudson.FilePath.list(FilePath.java:1690)_ _at hockeyapp.HockeyappRecorder
[JIRA] (JENKINS-42564) App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException)
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-42564 App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException) Change By: Marslo Jiao Jenkins Master # of executors: 0Build app succeed and also can be archived. The HockeyApp Path:_*App File (.ipa, .app.zip, .apk)*: *app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk*_Upload Error:_Uploading to HockeyApp..._ _/tmp/jtf7699425629259393086.tmp/xxx-14-debug.apk_ _java.lang.NullPointerException_ _at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)_ _at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)_ _at org.apache.http.impl.client.BasicCredentialsProvider.setCredentials(BasicCredentialsProvider.java:61)_ _at hockeyapp.HockeyappRecorder.createPreconfiguredHttpClient(HockeyappRecorder.java:165)_ _at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:252)_ _at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:204)_ _at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)_ _at hudson.model.Build$BuildExecution.post2(Build.java:185)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)_ _at hudson.model.Run.execute(Run.java:1753)_ _at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)_ _at hudson.model.ResourceController.execute(ResourceController.java:98)_ _at hudson.model.Executor.run(Executor.java:404)_ I've checked the Jenkins Master, and there's no folder like _/_tmp_/jtf*.tmp._But When I downgrade the HockeyApp plugin to [1.2.1| [ http://ftp.icm.edu.pl/packages/jenkins/plugins/hockeyapp/1.2.1/hockeyapp.hpi] ] , the application can be uploaded succeed with the exact same configuration. And the file can be found at JenkinsMarslo: _/tmp/jft*._tmp folder also._ _ —The second attempted:Change the *_App File (.ipa, .app.zip, .apk)_*: *_{color:#ff}**/**{color}/xxx-17-$\{BUILD_TYPE}.apk_*Error:_Uploading to HockeyApp..._ _No IPA/APK found to upload in: **/**/Copd-17-$\{BUILD_TYPE}.apk_ —The third attempted:Change the *__App File (.ipa, .app.zip, .apk): {color:#ff}$\{WORKSPACE}{color}/app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk__*Error:_Uploading to HockeyApp..._ _java.io.IOException: remote file operation failed: /home/salve/workspace/-job at hudson.remoting.Channel@b31cdf8:slave: java.io.IOException: Expecting Ant GLOB pattern, but saw '/home/slave/workspace/-job/app/build/outputs/apk/xxx-13-debug.apk'. See [http://ant.apache.org/manual/Types/fileset.html] for syntax_ _at hudson.FilePath.act(FilePath.java:992)_ _at hudson.FilePath.act(FilePath.java:974)_ _at hudson.FilePath.list(FilePath.java:1719)_ _at hudson.FilePath.list(FilePath.java:1704)_ _at hudson.FilePath.list(FilePath.java:1690)_ _at hockeyapp.HockeyappRecorder.performForApplication(H
[JIRA] (JENKINS-42564) App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException)
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-42564 App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException) Change By: Marslo Jiao Jenkins Master # of executors: 0Build app succeed and also can be archived. The HockeyApp Path:_*App File (.ipa, .app.zip, .apk)*: *app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk*_Upload Error:_Uploading to HockeyApp...__/tmp/jtf7699425629259393086.tmp/xxx-14-debug.apk__java.lang.NullPointerException_ _at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)_ _at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)_ _at org.apache.http.impl.client.BasicCredentialsProvider.setCredentials(BasicCredentialsProvider.java:61)_ _at hockeyapp.HockeyappRecorder.createPreconfiguredHttpClient(HockeyappRecorder.java:165)_ _at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:252)_ _at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:204)_ _at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)_ _at hudson.model.Build$BuildExecution.post2(Build.java:185)_ _at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)_ _at hudson.model.Run.execute(Run.java:1753)_ _at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)_ _at hudson.model.ResourceController.execute(ResourceController.java:98)_ _at hudson.model.Executor.run(Executor.java:404)_ I've checked the Jenkins Master, and there's no folder like _/_tmp_/jtf*.tmp._ But When I downgrade the HockeyApp plugin to [1.2.1|[http://ftp.icm.edu.pl/packages/jenkins/plugins/hockeyapp/1.2.1/hockeyapp.hpi |http://ftp.icm.edu.pl/packages/jenkins/plugins/hockeyapp/1.2.1/hockeyapp.hpi ] , ] ] , the application can be uploaded succeed with the exact same configuration. And the file can be found at JenkinsMarslo: _/tmp/jft*._tmp folder also. _ __ _ --- — The second attempted:Change the *_App File (.ipa, .app.zip, .apk)_*: *_{color:#ff}**/**{color}/xxx-17-$\{BUILD_TYPE}.apk_*Error:_Uploading to HockeyApp...__No IPA/APK found to upload in: **/**/Copd-17-$\{BUILD_TYPE}.apk_ --- — The third attempted:Change the *__App File (.ipa, .app.zip, .apk): {color:#ff}$\{WORKSPACE}{color}/app/build/outputs/apk/xxx-$\{BUILD_NUMBER}-$\{BuildType}.apk__*Error:_Uploading to HockeyApp...__java.io.IOException: remote file operation failed: /home/salve/workspace/-job at hudson.remoting.Channel@b31cdf8:slave: java.io.IOException: Expecting Ant GLOB pattern, but saw '/home/slave/workspace/-job/app/build/outputs/apk/xxx-13-debug.apk'. See [ http://ant.apache.org/manual/Types/fileset.html ] for syntax__at hudson.FilePath.act(FilePath.java:992)__at hudson.FilePath.act(FilePath.java:974)__at hudson.FilePath.list(FilePath.java:1719)__at hudson.FilePath.list(FilePath.java:1704)_
[JIRA] (JENKINS-42564) App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException)
Title: Message Title Marslo Jiao created an issue Jenkins / JENKINS-42564 App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException) Issue Type: Bug Assignee: Unassigned Components: hockeyapp-plugin Created: 2017/Mar/08 8:23 AM Environment: Jenkins: 2.32.3 LTS HockeyApp: 1.2.2 Labels: plugin Priority: Critical Reporter: Marslo Jiao Jenkins Master # of executors: 0 Build app succeed and also can be archived. The HockeyApp Path: App File (.ipa, .app.zip, .apk): app/build/outputs/apk/xxx-${BUILD_NUMBER}-${BuildType}.apk Upload Error: Uploading to HockeyApp... /tmp/jtf7699425629259393086.tmp/xxx-14-debug.apk java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011) at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006) at org.apache.http.impl.client.BasicCredentialsProvider.setCredentials(BasicCredentialsProvider.java:61) at hockeyapp.HockeyappRecorder.createPreconfiguredHttpClient(HockeyappRecorder.java:165) at hockeyapp.HockeyappRecorder.performForApplication(HockeyappRecorder.java:252) at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:204) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.
[JIRA] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Marslo Jiao edited a comment on JENKINS-36863 Re: [Gitlab plugin] Credentials drop-down doesn't show API token credential! Well, issue reproduced again in my environment. * Jenkins: ` * 2.19.3 LTS ` * * GitLab Plugin: ` * 1.4.3 ` * * Credentials Plugin: ` * 1.10 ` * * Plain Credentials Plugin: ` * 1.3 ` * * Credentials shows *current*, and connect is failed. !abc.png! * Click `Add` button, and add a new credential !1234.png! * Credentials drop-list still CANNOT show the new item, but actually, the new credential has added successfully. !123.png! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Marslo Jiao edited a comment on JENKINS-36863 Re: [Gitlab plugin] Credentials drop-down doesn't show API token credential! Well, issue reproduced again in my environment. * Jenkins: *2.19.3 LTS** GitLab Plugin: *1.4.3** Credentials Plugin: *1.10** Plain Credentials Plugin: *1.3** Credentials shows *current*, and connect is failed. !abc.png! * Click ` * Add ` * button, and add a new credential !1234.png! * Credentials drop-list still CANNOT show the new item, but actually, the new credential has added successfully. !123.png! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-36863 [Gitlab plugin] Credentials drop-down doesn't show API token credential! Change By: Marslo Jiao Attachment: 1234.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Marslo Jiao commented on JENKINS-36863 Re: [Gitlab plugin] Credentials drop-down doesn't show API token credential! Well, issue reproduced again in my environment. Jenkins: `2.19.3 LTS` GitLab Plugin: `1.4.3` Credentials Plugin: `1.10` Plain Credentials Plugin: `1.3` Credentials shows current, and connect is failed. Click `Add` button, and add a new credential Credentials drop-list still CANNOT show the new item, but actually, the new credential has added successfully. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-issu
[JIRA] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-36863 [Gitlab plugin] Credentials drop-down doesn't show API token credential! Change By: Marslo Jiao Attachment: 123.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Marslo Jiao updated an issue Jenkins / JENKINS-36863 [Gitlab plugin] Credentials drop-down doesn't show API token credential! Change By: Marslo Jiao Attachment: abc.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [git] (JENKINS-23379) Git rev-parse branch failed because of specified colors in ~/.gitconfig
Marslo Jiao updated JENKINS-23379 Git rev-parse branch failed because of specified colors in ~/.gitconfig Change By: Marslo Jiao (10/Jun/14 2:56 AM) Attachment: git-plugin.png 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] [git] (JENKINS-23379) Git rev-parse branch failed because of specified colors in ~/.gitconfig
Marslo Jiao updated JENKINS-23379 Git rev-parse branch failed because of specified colors in ~/.gitconfig Change By: Marslo Jiao (10/Jun/14 2:54 AM) Description: The error shows as below because of the specified colors set in the [~/.gitconfig|https://github.com/Marslo/LinuxStuff/blob/master/Configs/HOME/Git/.gitconfig]:{noformat} > git config core.sparsecheckout > git checkout -f 0bd22591afff0f67e84f9ce97365e1772351b3ce > git branch -a > git rev-parse [1;32m(detached from 0bd2259) [m^{commit}FATAL: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3cehudson.plugins.git.GitException: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3ce at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1497) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:896) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231)Caused by: hudson.plugins.git.GitException: Command "git rev-parse [1;32m(detached from 0bd2259) [m^{commit}" returned status code 128:stdout: [1;32m(detached from 0bd2259) [m^{commit}stderr: fatal: ambiguous argument ' [1;32m(detached from 0bd2259) [m^{commit}': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git [...] -- [...]'{noformat}The full log has been attached.The color settings as blow, details can be found from [my github|https://github.com/Marslo/LinuxStuff/blob/master/Configs/HOME/Git/.gitconfig#L23]:{ noforamt noformat }[color] ui = true log = always status = always add = always push = always pull = always diff = always branch = always interactive = auto[color "branch"] current = green bold local = yellow remote = red[color "status"] added = yellow changed = red bold untracked = magenta normal dim[color "diff"] meta = blue bold frag = magenta old = red bold new = green bold whitespace = red reverse{noformat}Can git plugin "ignore" the settings automatically (the settings like colors). I've [Created a question in stackoverflow|http://stackoverflow.com/questions/24118259/how-can-jenkins-ignore-the-color-settings-in-gitconfig-by-using-git-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] [git] (JENKINS-23379) Git rev-parse branch failed because of specified colors in ~/.gitconfig
Marslo Jiao created JENKINS-23379 Git rev-parse branch failed because of specified colors in ~/.gitconfig Issue Type: Bug Assignee: Nicolas De Loof Attachments: git-plugin.png, Jenkins-Git-failed-full-log.txt Components: git Created: 10/Jun/14 2:53 AM Description: The error shows as below because of the specified colors set in the ~/.gitconfig: > git config core.sparsecheckout > git checkout -f 0bd22591afff0f67e84f9ce97365e1772351b3ce > git branch -a > git rev-parse [1;32m(detached from 0bd2259) [m^{commit} FATAL: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3ce hudson.plugins.git.GitException: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3ce at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1497) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:896) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.plugins.git.GitException: Command "git rev-parse [1;32m(detached from 0bd2259) [m^{commit}" returned status code 128: stdout: [1;32m(detached from 0bd2259) [m^{commit} stderr: fatal: ambiguous argument ' [1;32m(detached from 0bd2259) [m^{commit}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git [...] -- [...]' The full log has been attached. The color settings as blow, details can be found from my github: {noforamt} [color] ui = true log = always status = always add = always push = always pull = always diff = always branch = always interactive = auto [color "branch"] current = green bold local = yellow remote = red [color "status"] added = yellow changed = red bold untracked = magenta normal dim [color "diff"] meta = blue bold frag = magenta old = red bold new = green bold whitespace = red reverse Can git plugin "ignore" the settings automatically (the settings like colors). I've Created a question in stackoverflow Environment: Linux (Ubuntu 14.04 & SUSE Linux Enterprise Server 10 SP3), Jenkins 1.566, GIT plugin 2.2.1 Project: Jenkins Labels: git gitplugin gitconfig Priority: Major Reporter: Marslo Jiao 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] [git] (JENKINS-23379) Git rev-parse branch failed because of specified colors in ~/.gitconfig
Marslo Jiao updated JENKINS-23379 Git rev-parse branch failed because of specified colors in ~/.gitconfig Change By: Marslo Jiao (10/Jun/14 3:02 AM) Description: The error shows as below because of after set the * Branch name * specified colors from * Additional Behaviours * set in the [~/ -> *Check out to specific local branch* . gitconfig|https://github.com/Marslo/LinuxStuff/blob/master/Configs/HOME/Git/.gitconfig]: {noformat} > git config core.sparsecheckout > git checkout -f 0bd22591afff0f67e84f9ce97365e1772351b3ce > git branch -a > git rev-parse [1;32m(detached from 0bd2259) [m^{commit}FATAL: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3cehudson.plugins.git.GitException: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3ce at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1497) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:896) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231)Caused by: hudson.plugins.git.GitException: Command "git rev-parse [1;32m(detached from 0bd2259) [m^{commit}" returned status code 128:stdout: [1;32m(detached from 0bd2259) [m^{commit}stderr: fatal: ambiguous argument ' [1;32m(detached from 0bd2259) [m^{commit}': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git [...] -- [...]'{noformat} The full log Full Jenkins Console Output has been attached (Jenkins-Git-failed-full-log . txt). After analyzed, the error is because of the *specified colors* set in the ~/.gitconfig. The color settings as blow, details can be found from [my github|https://github.com/Marslo/LinuxStuff/blob/master/Configs/HOME/Git/.gitconfig#L23]:{noformat}[color] ui = true log = always status = always add = always push = always pull = always diff = always branch = always interactive = auto[color "branch"] current = green bold local = yellow remote = red[color "status"] added = yellow changed = red bold untracked = magenta normal dim[color "diff"] meta = blue bold frag = magenta old = red bold new = green bold whitespace = red reverse{noformat} The Here the Jenkins job setting as below :!git-plugin.png!Can git plugin "ignore" the settings automatically (the settings like colors). I've [Created a question in stackoverflow|http://stackoverflow.com/questions/24118259/how-can-jenkins-ignore-the-color-settings-in-gitconfig-by-using-git-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] [git] (JENKINS-23379) Git rev-parse branch failed because of specified colors in ~/.gitconfig
Marslo Jiao updated JENKINS-23379 Git rev-parse branch failed because of specified colors in ~/.gitconfig Change By: Marslo Jiao (10/Jun/14 2:57 AM) Description: The error shows as below because of the ** specified colors ** set in the [~/.gitconfig|https://github.com/Marslo/LinuxStuff/blob/master/Configs/HOME/Git/.gitconfig]:{noformat} > git config core.sparsecheckout > git checkout -f 0bd22591afff0f67e84f9ce97365e1772351b3ce > git branch -a > git rev-parse [1;32m(detached from 0bd2259) [m^{commit}FATAL: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3cehudson.plugins.git.GitException: Could not checkout HEAD with start point 0bd22591afff0f67e84f9ce97365e1772351b3ce at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1497) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:896) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231)Caused by: hudson.plugins.git.GitException: Command "git rev-parse [1;32m(detached from 0bd2259) [m^{commit}" returned status code 128:stdout: [1;32m(detached from 0bd2259) [m^{commit}stderr: fatal: ambiguous argument ' [1;32m(detached from 0bd2259) [m^{commit}': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git [...] -- [...]'{noformat}The full log has been attached.The color settings as blow, details can be found from [my github|https://github.com/Marslo/LinuxStuff/blob/master/Configs/HOME/Git/.gitconfig#L23]:{noformat}[color] ui = true log = always status = always add = always push = always pull = always diff = always branch = always interactive = auto[color "branch"] current = green bold local = yellow remote = red[color "status"] added = yellow changed = red bold untracked = magenta normal dim[color "diff"] meta = blue bold frag = magenta old = red bold new = green bold whitespace = red reverse{noformat} The Jenkins job setting as below:!git-plugin.png! Can git plugin "ignore" the settings automatically (the settings like colors). I've [Created a question in stackoverflow|http://stackoverflow.com/questions/24118259/how-can-jenkins-ignore-the-color-settings-in-gitconfig-by-using-git-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.