[JIRA] (JENKINS-61003) Does not install correct binary per node platform
Title: Message Title Paul Eipper commented on JENKINS-61003 Re: Does not install correct binary per node platform Example, check the nodejs install tool, which does the autodetection: https://github.com/jenkinsci/nodejs-plugin/blob/3e952e8c85548a992f84cf682e69440702d76780/src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java#L169 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.204472.1581014438000.2951.1581014580119%40Atlassian.JIRA.
[JIRA] (JENKINS-61003) Does not install correct binary per node platform
Title: Message Title Paul Eipper created an issue Jenkins / JENKINS-61003 Does not install correct binary per node platform Issue Type: Bug Assignee: David Pires Attachments: Screen Shot 2020-02-06 at 15.36.18.png, Screen Shot 2020-02-06 at 15.37.14.png, Screen Shot 2020-02-06 at 15.39.30.png Components: terraform-plugin Created: 2020-02-06 18:40 Priority: Critical Reporter: Paul Eipper When setting multiple installers in the global config, the tool will always install the first listed, and will not correctly select per platform / cpu type of each node. Should probably autodetect based on node type, or have some option to filter by label. Add Comment
[JIRA] (JENKINS-60017) Gitea PR build fails if Jenkins user is not admin of the repo
Title: Message Title
Paul Eipper edited a comment on JENKINS-60017
Re: Gitea PR build fails if Jenkins user is not admin of the repo
Same Similar problem here, but even adding user as Admin, the error persists:{code:java}21:18:09 Querying the current revision of pull request #58...21:18:09 org.jenkinsci.plugin.gitea.client.api.GiteaHttpStatusException: HTTP 403/Forbidden21:18:09 at org.jenkinsci.plugin.gitea.client.impl.DefaultGiteaConnection.getObject(DefaultGiteaConnection.java:900)21:18:09 at org.jenkinsci.plugin.gitea.client.impl.DefaultGiteaConnection.fetchPullRequest(DefaultGiteaConnection.java:618)21:18:09 at org.jenkinsci.plugin.gitea.GiteaSCMSource.retrieve(GiteaSCMSource.java:178)21:18:09 at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582)21:18:09 at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98)21:18:09 at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299)21:18:09 at hudson.model.ResourceController.execute(ResourceController.java:97)21:18:09 at hudson.model.Executor.run(Executor.java:427)21:18:09 Finished: FAILURE{code}
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.202839.157260585.4753.1579826400128%40Atlassian.JIRA.
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title Paul Eipper commented on JENKINS-43353 Re: Ability to abort all previous running builds How to use the milestone solution in a declarative pipeline ? Brandon Squizzato Do you have a sample Jenkinsfile doing this? 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.180501.1491336786000.4683.1579818660423%40Atlassian.JIRA.
[JIRA] (JENKINS-60017) Gitea PR build fails if Jenkins user is not admin of the repo
Title: Message Title Paul Eipper commented on JENKINS-60017 Re: Gitea PR build fails if Jenkins user is not admin of the repo Same problem here, but even adding user as Admin, the error persists: 21:18:09 Querying the current revision of pull request #58... 21:18:09 org.jenkinsci.plugin.gitea.client.api.GiteaHttpStatusException: HTTP 403/Forbidden 21:18:09 at org.jenkinsci.plugin.gitea.client.impl.DefaultGiteaConnection.getObject(DefaultGiteaConnection.java:900) 21:18:09 at org.jenkinsci.plugin.gitea.client.impl.DefaultGiteaConnection.fetchPullRequest(DefaultGiteaConnection.java:618) 21:18:09 at org.jenkinsci.plugin.gitea.GiteaSCMSource.retrieve(GiteaSCMSource.java:178) 21:18:09 at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582) 21:18:09 at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98) 21:18:09 at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299) 21:18:09 at hudson.model.ResourceController.execute(ResourceController.java:97) 21:18:09 at hudson.model.Executor.run(Executor.java:427) 21:18:09 Finished: FAILURE 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
[JIRA] (JENKINS-60825) ExcludeOriginPRBranchesSCMHeadFilter NullPointerException
Title: Message Title Paul Eipper commented on JENKINS-60825 Re: ExcludeOriginPRBranchesSCMHeadFilter NullPointerException It actually creates a folder for the multibranch project, but the indexing there contains the same error: [Mon Jan 20 17:42:29 GMT 2020] Starting branch indexing... Looking up repository myog/my-project Checking branches... Checking branch MYPROJECT-1531-Fix-Menu ERROR: [Mon Jan 20 17:42:30 GMT 2020] Could not fetch branches from source org.jenkinsci.plugin.gitea.GiteaSCMNavigator::https://git.intranet.myorg.com::myorg::my-project java.lang.NullPointerException at org.jenkinsci.plugin.gitea.BranchDiscoveryTrait$ExcludeOriginPRBranchesSCMHeadFilter.isExcluded(BranchDiscoveryTrait.java:239) at jenkins.scm.api.trait.SCMSourceRequest.isExcluded(SCMSourceRequest.java:196) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:333) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:286) at org.jenkinsci.plugin.gitea.GiteaSCMSource.retrieve(GiteaSCMSource.java:247) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:641) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1032) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427) [Mon Jan 20 17:42:30 GMT 2020] Finished branch indexing. Indexing took 1.5 sec FATAL: Failed to recompute children of My Org » my-project java.lang.NullPointerException at org.jenkinsci.plugin.gitea.BranchDiscoveryTrait$ExcludeOriginPRBranchesSCMHeadFilter.isExcluded(BranchDiscoveryTrait.java:239) at jenkins.scm.api.trait.SCMSourceRequest.isExcluded(SCMSourceRequest.java:196) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:333) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:286) at org.jenkinsci.plugin.gitea.GiteaSCMSource.retrieve(GiteaSCMSource.java:247) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:641) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1032) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427) Finished: FAILURE
[JIRA] (JENKINS-60825) ExcludeOriginPRBranchesSCMHeadFilter NullPointerException
Title: Message Title Paul Eipper created an issue Jenkins / JENKINS-60825 ExcludeOriginPRBranchesSCMHeadFilter NullPointerException Issue Type: Bug Assignee: Unassigned Components: gitea-plugin Created: 2020-01-20 18:24 Environment: Gitea Plugin 1.1.2 Jenkins ver. 2.204.1 Gitea 1.10.0 Priority: Major Reporter: Paul Eipper After setting up a Gitea Organization job, the scan crashes on some repos with the following error: Looking up repository myorg/my-project Checking branches... Checking branch MYPROJECT-1531-Fix-Menu ERROR: Failed to create or update a subproject my-project java.lang.NullPointerException at org.jenkinsci.plugin.gitea.BranchDiscoveryTrait$ExcludeOriginPRBranchesSCMHeadFilter.isExcluded(BranchDiscoveryTrait.java:239) at jenkins.scm.api.trait.SCMSourceRequest.isExcluded(SCMSourceRequest.java:196) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:333) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:286) at org.jenkinsci.plugin.gitea.GiteaSCMSource.retrieve(GiteaSCMSource.java:247) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:327) at jenkins.branch.MultiBranchProjectFactory$BySCMSourceCriteria.recognizes(MultiBranchProjectFactory.java:263) at jenkins.branch.OrganizationFolder$SCMSourceObserverImpl$1.recognizes(OrganizationFolder.java:1405) at jenkins.branch.OrganizationFolder$SCMSourceObserverImpl$1.complete(OrganizationFolder.java:1420) at jenkins.scm.api.trait.SCMNavigatorRequest.process(SCMNavigatorRequest.java:254) at
[JIRA] (JENKINS-58624) docker.withRegistry doesn't use build environment
Title: Message Title Paul Eipper commented on JENKINS-58624 Re: docker.withRegistry doesn't use build environment Of note: I tried setting a docker tool location, with override on the slave to "/usr/local", but it still failed to find the docker command. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.200791.1563924433000.19827.1563925980045%40Atlassian.JIRA.
[JIRA] (JENKINS-58624) docker.withRegistry doesn't use build environment
Title: Message Title Paul Eipper commented on JENKINS-58624 Re: docker.withRegistry doesn't use build environment Probably related to https://issues.jenkins-ci.org/browse/JENKINS-47415 since it fails in the fingerprint. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.200791.1563924433000.19826.1563924600043%40Atlassian.JIRA.
[JIRA] (JENKINS-58624) docker.withRegistry doesn't use build environment
Title: Message Title
Paul Eipper created an issue
Jenkins / JENKINS-58624
docker.withRegistry doesn't use build environment
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-commons-plugin
Created:
2019-07-23 23:27
Environment:
Jenkins 2.176.2, linux master, agent on macOS 10.13.6
Priority:
Major
Reporter:
Paul Eipper
When running a pipeline script like this:
node('docker') {
def CURRENT_VERSION
def builtImage
stage('Clone repository') {
checkout scm
}
stage('Output version') {
CURRENT_VERSION = sh (returnStdout: true,
script: 'python "${SCRIPTS}/version.py" show all'
).trim()
}
stage('Build image') {
builtImage = docker.build("${DOCKER_IMAGE}:${CURRENT_VERSION}", ".")
}
stage('Push image') {
docker.withRegistry("${DOCKER_REGISTRY}", "${DOCKER_CREDENTIALS}") {
builtImage.push()
}
}
}
The build fails on the docker.withRegistry stage with error docker command not found:
Successfully built 8e4939ceb3f6
Successfully tagged org/project:2.5.2.112-1-g3cab587
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.io.IOException: error=2, No such file or directory
at
[JIRA] (JENKINS-47415) DockerClient.version doesn't use build environment
Title: Message Title
Paul Eipper edited a comment on JENKINS-47415
Re: DockerClient.version doesn't use build environment
I have the same issue by just building an image and trying to get the reference to it:{code:title=Jenkinsfile}node(docker) {stage('Build image') {builtImage = docker.build("corp/api:1.0", ".")}}{code}The stack trace generated is:{code}(...)Successfully built 9a71968963a9Successfully tagged corp/api:1.0[Pipeline] dockerFingerprintFrom[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to zerg at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693) at hudson.remoting.UserResponse.retrieve(UserRequest.java:310) at hudson.remoting.Channel.call(Channel.java:908) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:296) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:277) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:274) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspect(DockerClient.java:198) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:218) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:129) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:249) at hudson.Proc$LocalProc.(Proc.java:218) at hudson.Launcher$LocalLauncher.launch(Launcher.java:930) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260) at hudson.remoting.UserRequest.perform(UserRequest.java:207) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:358) 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 java.lang.Thread.run(Thread.java:748){code}The environment is running with master macOS machine and a slave macOS machine.Only the slave has docker installed.The install location on the slave for the docker binary is in ` {{ /usr/local/bin ` }} , which is not by default in PATH.It is set as an extended extra variable on the executor configuration by setting an environment variable named ` {{
[JIRA] (JENKINS-47415) DockerClient.version doesn't use build environment
Title: Message Title
Paul Eipper commented on JENKINS-47415
Re: DockerClient.version doesn't use build environment
I have the same issue by just building an image and trying to get the reference to it:
Jenkinsfile
node(docker) {
stage('Build image') {
builtImage = docker.build("corp/api:1.0", ".")
}
}
The stack trace generated is:
(...)
Successfully built 9a71968963a9
Successfully tagged corp/api:1.0
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to zerg
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
at hudson.remoting.Channel.call(Channel.java:908)
at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:296)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:277)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:274)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspect(DockerClient.java:198)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:218)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:129)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate(ACL.java:260)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at hudson.Proc$LocalProc.(Proc.java:249)
at hudson.Proc$LocalProc.(Proc.java:218)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:930)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260)
at hudson.remoting.UserRequest.perform(UserRequest.java:207)
at hudson.remoting.UserRequest.perform(UserRequest.java:53)
at hudson.remoting.Request$2.run(Request.java:358)
at
[JIRA] (JENKINS-47415) DockerClient.version doesn't use build environment
Title: Message Title
Paul Eipper edited a comment on JENKINS-47415
Re: DockerClient.version doesn't use build environment
I have the same issue by just building an image and trying to get the reference to it:{code:title=Jenkinsfile}node(docker) {stage('Build image') {builtImage = docker.build("corp/api:1.0", ".")}}{code}The stack trace generated is:{code}(...)Successfully built 9a71968963a9Successfully tagged corp/api:1.0[Pipeline] dockerFingerprintFrom[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to zerg at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693) at hudson.remoting.UserResponse.retrieve(UserRequest.java:310) at hudson.remoting.Channel.call(Channel.java:908) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:296) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:277) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:274) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspect(DockerClient.java:198) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:218) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:129) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:249) at hudson.Proc$LocalProc.(Proc.java:218) at hudson.Launcher$LocalLauncher.launch(Launcher.java:930) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260) at hudson.remoting.UserRequest.perform(UserRequest.java:207) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:358) 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 java.lang.Thread.run(Thread.java:748){code}The environment is running with master macOS machine and a slave macOS , only machine.Only the slave has docker installed. The install location on the slave for the docker binary is in `/usr/local/bin`, which is not by default in PATH , but .It is set as an extended variable on the executor configuration by setting an environment variable named
[JIRA] (JENKINS-47415) DockerClient.version doesn't use build environment
Title: Message Title
Paul Eipper commented on JENKINS-47415
Re: DockerClient.version doesn't use build environment
I have the same issue by just building an image and trying to get the reference to it:
Jenkinsfile
node(docker) {
stage('Build image') {
builtImage = docker.build("corp/api:1.0", ".")
}
}
The stack trace generated is:
(...)
Successfully built 9a71968963a9
Successfully tagged corp/api:1.0
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to zerg
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
at hudson.remoting.Channel.call(Channel.java:908)
at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:296)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:277)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:274)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspect(DockerClient.java:198)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:218)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:129)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate(ACL.java:260)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at hudson.Proc$LocalProc.(Proc.java:249)
at hudson.Proc$LocalProc.(Proc.java:218)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:930)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260)
at hudson.remoting.UserRequest.perform(UserRequest.java:207)
at hudson.remoting.UserRequest.perform(UserRequest.java:53)
at hudson.remoting.Request$2.run(Request.java:358)
at
[JIRA] (JENKINS-36925) EnvInject
Title: Message Title Paul Eipper commented on JENKINS-36925 Re: EnvInject Just tripped on this issue. In my case it was caused because on the Prepare Environment I had a shell script that created a properties file. It seems the default folder at that point is the Jenkins home folder. 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-37560) Export KEYCHAIN_NAME environment variable
Title: Message Title
Paul Eipper created an issue
Jenkins / JENKINS-37560
Export KEYCHAIN_NAME environment variable
Issue Type:
New Feature
Assignee:
Unassigned
Components:
xcode-plugin
Created:
2016/Aug/19 6:00 PM
Priority:
Minor
Reporter:
Paul Eipper
When using the DeveloperProfileLoader, the plugin will generate a name for the Keychain based on this code:
String keyChain = "jenkins-"+build.getProject().getFullName().replace('/', '-');
https://github.com/jenkinsci/xcode-plugin/blob/2f8f70/src/main/java/au/com/rayh/DeveloperProfileLoader.java#L52 This is a request to have that name exported as an environment variable, to avoid having to hardcode the same logic in other parts of the build script. Currently, to access the generated keychain in a shell script, it has to be written like this:
security show-keychain-info "jenkins-${JOB_NAME/\//-}"
This request is so the same shell could be done like this:
security show-keychain-info "${KEYCHAIN_NAME}"
[JIRA] (JENKINS-37533) Git notifyCommit polling not triggered with Parameterized Build variable in Repository URL
Title: Message Title
Paul Eipper updated an issue
Jenkins / JENKINS-37533
Git notifyCommit polling not triggered with Parameterized Build variable in Repository URL
Change By:
Paul Eipper
Polling will not trigger when the Git Repository URL has a variable that is set by Parameterized Build plugin.Step to reproduce:1. Create Freestyle Job2. Set "This project is parameterized"3. Add String parameter named `PROJECT` with default value of your git project name4. Set the Git Repository URL to expand that variable, ex: ` {code} git_u...@git.example.com:${PROJECT}.git ` {code} 5. Enable Poll SCM in the Build Triggers with no schedule6. Save the project and do a push to the repositoryResults:- Expected: job is triggered with default Parameterized Build values- Actual: the job is not triggeredRelated:https://issues.jenkins-ci.org/browse/JENKINS-26315 (same issue for global variables)https://issues.jenkins-ci.org/browse/JENKINS-27692 (github plugin had same issue)https://issues.jenkins-ci.org/browse/JENKINS-9686 (mercurial had same issue)https://issues.jenkins-ci.org/browse/JENKINS-14276 (branch variable on polling)https://issues.jenkins-ci.org/browse/JENKINS-20427 (branch variable on polling)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37533) Git notifyCommit polling not triggered with Parameterized Build variable in Repository URL
Title: Message Title
Paul Eipper created an issue
Jenkins / JENKINS-37533
Git notifyCommit polling not triggered with Parameterized Build variable in Repository URL
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2016/Aug/19 12:31 AM
Priority:
Major
Reporter:
Paul Eipper
Polling will not trigger when the Git Repository URL has a variable that is set by Parameterized Build plugin. Step to reproduce: 1. Create Freestyle Job 2. Set "This project is parameterized" 3. Add String parameter named `PROJECT` with default value of your git project name 4. Set the Git Repository URL to expand that variable, ex: `git_u...@git.example.com:$ {PROJECT} .git` 5. Enable Poll SCM in the Build Triggers with no schedule 6. Save the project and do a push to the repository Results:
Expected: job is triggered with default Parameterized Build values
Actual: the job is not triggered
Related: https://issues.jenkins-ci.org/browse/JENKINS-26315 (same issue for global variables) https://issues.jenkins-ci.org/browse/JENKINS-27692 (github plugin had same issue) https://issues.jenkins-ci.org/browse/JENKINS-9686 (mercurial had same issue) https://issues.jenkins-ci.org/browse/JENKINS-14276 (branch variable on polling) https://issues.jenkins-ci.org/browse/JENKINS-20427 (branch variable on polling)
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Paul Eipper commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade Thanks it worked: remove JENKINS_HOME/plugins/dashboard-view/WEB-INF/lib/joda-time-1.6.jar copy JENKINS_HOME/plugins/analysis-core/WEB-INF/lib/joda-time-2.1.jar to that folder edit the files and change the version listed from "1.6" to "2.1": JENKINS_HOME/plugins/dashboard-view/WEB-INF/licenses.xml JENKINS_HOME/plugins/dashboard-view/META-INF/maven/org.jenkins-ci.plugins/dashboard-view/pom.xml restart Jenkins 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-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Paul Eipper edited a comment on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade I am not sure how to perform the "updating files e.g. pom.xml" step 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-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Paul Eipper commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade I am not sure how to perform the "updating files e.g. pom.xml" 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-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Paul Eipper edited a comment on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 Template Project plugin version 1.5.2Multiple SCMs plugin not installed Other SCM plugins:Git client plugin - 1.19.6 Git plugin - 2.5.0 Pipeline: SCM Step - 2.1 Pipeline: Step API - 2.2 SCM API Plugin - 1.2 Subversion Plug-in - 2.6 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-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Paul Eipper commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 Template Project plugin version 1.5.2 Multiple SCMs plugin not installed 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-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title
Paul Eipper edited a comment on JENKINS-31712
Re: Use SCM from another project is removed after upgrading to 1.5.1
This is in the system log:{code :java }Failed to instantiate Key[type=hudson.plugins.templateproject.ProxySCM$DescriptorImpl, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Guice provision errors:1) Error injecting constructor, java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at hudson.plugins.templateproject.ProxySCM$DescriptorImpl.(ProxySCM.java:113)1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:389) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1233) at hudson.plugins.git.GitSCM.onLoaded(GitSCM.java:1714) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:926) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.privateGetMethodRecursive(Class.java:3048) at java.lang.Class.getMethod0(Class.java:3018) at java.lang.Class.getMethod(Class.java:1784) at hudson.model.Descriptor.(Descriptor.java:285) at hudson.scm.SCMDescriptor.(SCMDescriptor.java:71) at hudson.plugins.templateproject.ProxySCM$DescriptorImpl.(ProxySCM.java:113) at hudson.plugins.templateproject.ProxySCM$DescriptorImpl$$FastClassByGuice$$4e632614.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269) at
[JIRA] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Paul Eipper commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 This is in the system log: Failed to instantiate Key[type=hudson.plugins.templateproject.ProxySCM$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at hudson.plugins.templateproject.ProxySCM$DescriptorImpl.(ProxySCM.java:113) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:389) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1233) at hudson.plugins.git.GitSCM.onLoaded(GitSCM.java:1714) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:926) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.privateGetMethodRecursive(Class.java:3048) at java.lang.Class.getMethod0(Class.java:3018) at java.lang.Class.getMethod(Class.java:1784) at hudson.model.Descriptor.(Descriptor.java:285) at hudson.scm.SCMDescriptor.(SCMDescriptor.java:71) at hudson.plugins.templateproject.ProxySCM$DescriptorImpl.(ProxySCM.java:113) at hudson.plugins.templateproject.ProxySCM$DescriptorImpl$$FastClassByGuice$$4e632614.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Paul Eipper updated an issue Jenkins / JENKINS-36281 Dashboard trend graphs not displayed following plugin upgrade Change By: Paul Eipper Attachment: jenkins-dashboard-view.log 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-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Paul Eipper commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade Is there a step by step workaround to fix this? 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-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Paul Eipper commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Our environment is OSX master and slave. I compiled SSH Agent plugin to enable the native ssh-agent with this patch: https://github.com/jenkinsci/ssh-agent-plugin/pull/2 The credentials provided work for both the main and submodule clone operations. In my setup the credential is a single SSH key that has read access to the main and all submodule repos. I have not tested if you need to unlock multiple keys. 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Paul Eipper commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Today I am using SSH Agent Plugin, which works with Git Plugin both for clone and submodule as is. Does this new beta feature removes the need for SSH Agent Plugin in that case? 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] [build-failure-analyzer-plugin] (JENKINS-32369) Option to disabe build log scan output
Title: Message Title Paul Eipper created an issue Jenkins / JENKINS-32369 Option to disabe build log scan output Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 08/Jan/16 7:07 PM Priority: Minor Reporter: Paul Eipper The data generated by BFA in the build log is not related to the build so there should be a way to disable the log appending it does, preferably outputting that log to the jenkins log where it can be filtered. Add Comment
[JIRA] [build-failure-analyzer-plugin] (JENKINS-24171) BFA is blindly adding text to gzipped log
Title: Message Title Paul Eipper commented on JENKINS-24171 Re: BFA is blindly adding text to gzipped log Can we have an option to disable build log output from BFA? 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] [clang-scanbuild-plugin] (JENKINS-30162) Integrate with Dashboard View plugin
Title: Message Title Paul Eipper commented on JENKINS-30162 Re: Integrate with Dashboard View plugin Check https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins for reference implementation. 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] [xcode-plugin] (JENKINS-20916) Code Sign error: No matching provisioning profile found
Title: Message Title Paul Eipper commented on JENKINS-20916 Re: Code Sign error: No matching provisioning profile found See https://issues.jenkins-ci.org/browse/JENKINS-30979 And https://stackoverflow.com/questions/25637472/jenkins-ios-build-using-credentials-and-developer-profile 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] [xcode-plugin] (JENKINS-30979) Unlock Keychain integrate with Developer Profile
Title: Message Title
Paul Eipper commented on JENKINS-30979
Re: Unlock Keychain integrate with Developer Profile
This is the script I need to run to add the keychain and keep it unlocked without timeouts:
# enable temporary keychain
security list-keychain -s "jenkins-${JOB_NAME}"
security list-keychain
# disable keychain timeout
security set-keychain-settings "jenkins-${JOB_NAME}"
security show-keychain-info
The only issue is that concurrent builds with different temporary keychains have conflicts, since the keychain is serial.
Another option would be to use this build option (not tried yet):
OTHER_CODE_SIGN_FLAGS='--keychain jenkins-${JOB_NAME}'
To force xcodebuild to use that.
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] [xcode-plugin] (JENKINS-30979) Unlock Keychain integrate with Developer Profile
Title: Message Title
Paul Eipper edited a comment on JENKINS-30979
Re: Unlock Keychain integrate with Developer Profile
This is the script I need to run to add the keychain and keep it unlocked without timeouts:{code}# enable temporary keychainsecurity list-keychain -s "jenkins-${JOB_NAME}"security list-keychain# disable keychain timeoutsecurity set-keychain-settings "jenkins-${JOB_NAME}"security show-keychain-info "jenkins-${JOB_NAME}" {code}The only issue is that concurrent builds with different temporary keychains have conflicts, since the keychain is serial.Another option would be to use this build option (not tried yet):{code}OTHER_CODE_SIGN_FLAGS='--keychain jenkins-${JOB_NAME}'{code}To force xcodebuild to use that.
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] [xcode-plugin] (JENKINS-30979) Unlock Keychain integrate with Developer Profile
Title: Message Title
Paul Eipper created an issue
Jenkins / JENKINS-30979
Unlock Keychain integrate with Developer Profile
Issue Type:
New Feature
Assignee:
Unassigned
Components:
xcode-plugin
Created:
15/Oct/15 10:42 PM
Priority:
Minor
Reporter:
Paul Eipper
Selecting "Unlock Keychain" option only show the globally configured keychains, or manual option.
There should be an option to unlock the keychain provided by the Credentials plugin through the ".developerprofile" file.
Current workaround is having a execute script step that runs this line:
security list-keychain -s "jenkins-${JOB_NAME}"
Which works because the Credentials plugin already unlocks the keychain, just doesn't it add it to the keychain list.
Ideally the Xcode Plugin should have the option to easily just use that keychain.
[JIRA] [slave-setup-plugin] (JENKINS-30954) Add run before build script
Title: Message Title Paul Eipper created an issue Jenkins / JENKINS-30954 Add run before build script Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: slave-setup-plugin Created: 14/Oct/15 2:39 PM Priority: Major Reporter: Paul Eipper Would be great to have a script that is run on slaves before each job execution. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [clang-scanbuild-plugin] (JENKINS-30162) Integrate with Dashboard View plugin
Title: Message Title Paul Eipper created an issue Jenkins / JENKINS-30162 Integrate with Dashboard View plugin Issue Type: New Feature Assignee: Josh Kennedy Components: clang-scanbuild-plugin Created: 26/Aug/15 6:30 PM Priority: Minor Reporter: Paul Eipper Extend the plugin to be displayed as a DashboardPortlet as described in https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View so that the trend graph can be displayed as a portlet. Add Comment
[JIRA] [jabber-plugin] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
Paul Eipper commented on JENKINS-9233 Builds hang on jabber notification when XMPP server is not responding Thanks for the feedback. You believe we would need a patch in Smack lib? 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] [jabber-plugin] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
Paul Eipper commented on JENKINS-9233 Builds hang on jabber notification when XMPP server is not responding Still happening here. @kutzi: what do you think about @cforce suggestion? 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] [clang-scanbuild-plugin] (JENKINS-17092) Clang Scan-Build Plugin needs updating to handle newer scan-build output directory layout
Paul Eipper commented on JENKINS-17092 Clang Scan-Build Plugin needs updating to handle newer scan-build output directory layout Please apply the fix, it's been available as a pull request on github since 2013: https://github.com/jenkinsci/clang-scanbuild-plugin/pull/3 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] [xcode] (JENKINS-24766) Add support to multiple Xcode versions
Paul Eipper created JENKINS-24766 Add support to multiple Xcode versions Issue Type: New Feature Assignee: Unassigned Components: xcode Created: 18/Sep/14 6:29 PM Description: Using Environment Injector Plugin it is possible to define DEVELOPER_DIR to point to another Xcode installation. This feature request is to incorporate that into Xcode Plugin so that multiple versions can be configured on Jenkins settings and selected on the job setup. See more details here: http://andymolloy.tumblr.com/post/33504271829/specifying-xcode-version-for-jenkins-projects Project: Jenkins Priority: Major Reporter: Paul Eipper 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-18666) Submodule reference
Paul Eipper commented on JENKINS-18666 Submodule reference Please consider merging the pull request as the git-client-plugin now supports this. 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/groups/opt_out.
[JIRA] [git] (JENKINS-18698) Toplevel git reference repos
Paul Eipper commented on JENKINS-18698 Toplevel git reference repos Not exactly this, but simply enabling reference repos for submodules would already help those that do have externally managed reference clones: https://issues.jenkins-ci.org/browse/JENKINS-18666 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/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17052) Change to root directory of host configuration didn't work
Paul Eipper commented on JENKINS-17052 Change to root directory of host configuration didnt work I agree, it should be enough to automatically perform a "cd" into the concatenated Remote Directory paths after login. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-18519) Add submodule reference support
Paul Eipper commented on JENKINS-18519 Add submodule reference support Created pull request on github: https://github.com/jenkinsci/git-client-plugin/pull/12 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/groups/opt_out.
[JIRA] [git] (JENKINS-18666) Submodule reference
Paul Eipper created JENKINS-18666 Submodule reference Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 08/Jul/13 9:15 PM Description: Method `submoduleUpdate` should accept `reference` the same way as `clone` does. git submodule update --init --recursive --reference $reference Project: Jenkins Labels: git plugin Priority: Major Reporter: Paul Eipper 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/groups/opt_out.
[JIRA] [git] (JENKINS-18666) Submodule reference
Paul Eipper edited a comment on JENKINS-18666 Submodule reference Needs the parameter to be available on git-client-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/groups/opt_out.
[JIRA] [git-client] (JENKINS-18519) Add submodule reference support
Paul Eipper updated JENKINS-18519 Add submodule reference support Change By: Paul Eipper (08/Jul/13 9:18 PM) URL: https://github.com/jenkinsci/git-client-plugin/pull/12 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/groups/opt_out.
[JIRA] [git] (JENKINS-18666) Submodule reference
Paul Eipper updated JENKINS-18666 Submodule reference Change By: Paul Eipper (08/Jul/13 9:21 PM) Description: Method`submoduleUpdate`shouldaccept`reference`thesamewayas`clone`does.gitsubmoduleupdate--init--recursive--reference$reference Speedsupsubmoduleupdatewhenusingalocalmirror. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-18519) Add submodule reference support
Paul Eipper created JENKINS-18519 Add submodule reference support Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 26/Jun/13 6:41 PM Description: Method `submoduleUpdate` should accept `reference` the same way as `clone` does. git submodule update --init --recursive --reference $reference Project: Jenkins Labels: git plugin Priority: Major Reporter: Paul Eipper 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/groups/opt_out.
[JIRA] (JENKINS-13885) Failures not copied when path contains whitespaces
Paul Eipper created JENKINS-13885:
-
Summary: Failures not copied when path contains whitespaces
Key: JENKINS-13885
URL: https://issues.jenkins-ci.org/browse/JENKINS-13885
Project: Jenkins
Issue Type: Bug
Components: clang-scanbuild
Affects Versions: current
Reporter: Paul Eipper
Assignee: Josh Kennedy
The scan-build step fails to write to paths that contain spaces:
{code}
EXECUTING COMMAND:[/Volumes/Overmind HD/Jenkins/checker-264/scan-build, -k, -v,
-v, -o, /Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports, xcodebuild, -target,
ProjectExample, -configuration, Debug, -sdk, iphonesimulator, clean, build]
[workspace] $ /Volumes/Overmind HD/Jenkins/checker-264/scan-build -k -v -v -o
/Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports xcodebuild -target
ProjectExample -configuration Debug -sdk iphonesimulator clean build
scan-build: Emitting reports for this run to '/Volumes/Overmind
HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports/2012-05-23-1'.
(...)
scan-build: 0 bugs found.
scan-build: The analyzer encountered problems on some source files.
scan-build: Preprocessed versions of these sources were deposited in
'/Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports/2012-05-23-1/failures'.
scan-build: Please consider submitting a bug report using these files:
scan-build: http://clang-analyzer.llvm.org/filing_bugs.html
{code}
Checking /Volumes after the build there is an file named Overmind containing
various scan-build path error related messages, as in:
{code}
usage: uname [-amnprsv]
Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.0
Thread model: posix
clang: error: no such file or directory: 'HD/Jenkins/Home/jobs/Project'
clang: error: no such file or directory:
'Example-Develop/workspace/clangScanBuildReports/2012-05-23-1/failures/clang_other_error_khPht3.mi.info.txt'
(...)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13885) Failures not copied when path contains whitespaces
[
https://issues.jenkins-ci.org/browse/JENKINS-13885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Eipper updated JENKINS-13885:
--
Description:
The scan-build step fails to write to paths that contain spaces.
From the build log:
{noformat}
EXECUTING COMMAND:[/Volumes/Overmind HD/Jenkins/checker-264/scan-build, -k, -v,
-v, -o, /Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports, xcodebuild, -target,
ProjectExample, -configuration, Debug, -sdk, iphonesimulator, clean, build]
[workspace] $ /Volumes/Overmind HD/Jenkins/checker-264/scan-build -k -v -v -o
/Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports xcodebuild -target
ProjectExample -configuration Debug -sdk iphonesimulator clean build
scan-build: Emitting reports for this run to '/Volumes/Overmind
HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports/2012-05-23-1'.
(...)
scan-build: 0 bugs found.
scan-build: The analyzer encountered problems on some source files.
scan-build: Preprocessed versions of these sources were deposited in
'/Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports/2012-05-23-1/failures'.
scan-build: Please consider submitting a bug report using these files:
scan-build: http://clang-analyzer.llvm.org/filing_bugs.html
{noformat}
Checking /Volumes after the build there is a file named Overmind containing
various scan-build path error related messages, as in:
{noformat}
usage: uname [-amnprsv]
Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.0
Thread model: posix
clang: error: no such file or directory: 'HD/Jenkins/Home/jobs/Project'
clang: error: no such file or directory:
'Example-Develop/workspace/clangScanBuildReports/2012-05-23-1/failures/clang_other_error_khPht3.mi.info.txt'
(...)
{noformat}
was:
The scan-build step fails to write to paths that contain spaces:
{code}
EXECUTING COMMAND:[/Volumes/Overmind HD/Jenkins/checker-264/scan-build, -k, -v,
-v, -o, /Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports, xcodebuild, -target,
ProjectExample, -configuration, Debug, -sdk, iphonesimulator, clean, build]
[workspace] $ /Volumes/Overmind HD/Jenkins/checker-264/scan-build -k -v -v -o
/Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports xcodebuild -target
ProjectExample -configuration Debug -sdk iphonesimulator clean build
scan-build: Emitting reports for this run to '/Volumes/Overmind
HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports/2012-05-23-1'.
(...)
scan-build: 0 bugs found.
scan-build: The analyzer encountered problems on some source files.
scan-build: Preprocessed versions of these sources were deposited in
'/Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports/2012-05-23-1/failures'.
scan-build: Please consider submitting a bug report using these files:
scan-build: http://clang-analyzer.llvm.org/filing_bugs.html
{code}
Checking /Volumes after the build there is an file named Overmind containing
various scan-build path error related messages, as in:
{code}
usage: uname [-amnprsv]
Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.0
Thread model: posix
clang: error: no such file or directory: 'HD/Jenkins/Home/jobs/Project'
clang: error: no such file or directory:
'Example-Develop/workspace/clangScanBuildReports/2012-05-23-1/failures/clang_other_error_khPht3.mi.info.txt'
(...)
{code}
Failures not copied when path contains whitespaces
--
Key: JENKINS-13885
URL: https://issues.jenkins-ci.org/browse/JENKINS-13885
Project: Jenkins
Issue Type: Bug
Components: clang-scanbuild
Affects Versions: current
Reporter: Paul Eipper
Assignee: Josh Kennedy
The scan-build step fails to write to paths that contain spaces.
From the build log:
{noformat}
EXECUTING COMMAND:[/Volumes/Overmind HD/Jenkins/checker-264/scan-build, -k,
-v, -v, -o, /Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports, xcodebuild, -target,
ProjectExample, -configuration, Debug, -sdk, iphonesimulator, clean, build]
[workspace] $ /Volumes/Overmind HD/Jenkins/checker-264/scan-build -k -v -v
-o /Volumes/Overmind HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports xcodebuild -target
ProjectExample -configuration Debug -sdk iphonesimulator clean build
scan-build: Emitting reports for this run to '/Volumes/Overmind
HD/Jenkins/Home/jobs/Project
Example-Develop/workspace/clangScanBuildReports/2012-05-23-1'.
(...)
scan-build:
[JIRA] (JENKINS-13772) Produce tokens with Token Macro plugin
Paul Eipper created JENKINS-13772: - Summary: Produce tokens with Token Macro plugin Key: JENKINS-13772 URL: https://issues.jenkins-ci.org/browse/JENKINS-13772 Project: Jenkins Issue Type: New Feature Components: xcode Affects Versions: current Reporter: Paul Eipper Export tokens read from the configured project to be built. I am specially interested in these values: XCODE_BUNDLE_SHORT_VERSION = CFBundleShortVersionString XCODE_BUNDLE_VERSION = CFBundleVersion Also, after the build is completed: XCODE_BUILD_OUTPUT_DIR = Build output directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
