[JIRA] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
Charles Doucette commented on JENKINS-24125 Git Polling fails for job restricted to Mac OS X slave (with Windows master) I can confirm that the name and paths of the git executables are correctly specified for the various platforms on the Git installations section of the Jenkins configuration page. Apparently I could override those tool locations on the OS/X slave node configuration page (I was not aware of this) - but why do I need to do that? Please explain to me how I can specify the proper git executable to use for both polling and building if they each use the same git executable specified by the job but polling runs on the master node but the job is built on the specified slave node? Thanks, Chuck 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-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
Charles Doucette commented on JENKINS-24125 Git Polling fails for job restricted to Mac OS X slave (with Windows master) So is it expected that all git installations will work on all platforms, even if the job can only be built on certain platforms? I didn't think so - so I assumed that the polling etc. would occur only on the appropriate node(s). If that is the case, then it seems as if the only appropriate path to the git executable would be "git" as you suggested (assuming the git executable will be found in the path and that the ".exe" suffix for windows is implicit/not-necessary). For some reason, the PATH variable defined on the OS/X slave for the user running Jenkins didn't seem to be used - thus "git" was not found and therefore we defined an alternate (platform specific) installation of git for Mac with an explicit directory instead of overriding the default installation just for the slave (which I didn't know I could/should do). 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] [gitlab-hook] (JENKINS-23743) Failure on Git Polling Log when using Linux Master and Windows Slave
Charles Doucette commented on JENKINS-23743 Failure on Git Polling Log when using Linux Master and Windows Slave FYI - When I used "Force polling using workspace - my problem was resolved". I see that this issue is resolved. What version of the plugin will include this fix? 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-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
Charles Doucette created JENKINS-24125 Git Polling fails for job restricted to Mac OS X slave (with Windows master) Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: GitPollingLog.txt, Mobile-iOS-develop-config.xml Components: git Created: 05/Aug/14 10:59 PM Description: I have defined two installations of git on our Windows master node: Default: git.exe (found in the PATH) Mac: /usr/local/bin/git (not found in the PATH) I have certain jobs that must run on a Mac. For those jobs, I have selected "Mac" for the git executable. When those jobs try to poll github for changes, they get errors like this: Started on Aug 5, 2014 6:38:03 PM Using strategy: Default poll Last Built Revision: Revision 33ce43e454fd2447f548f18dc3bc404ff1a2b021 (origin/release) /usr/local/bin/git ls-remote -h g...@github.com:everyscape/Mobile.git release # timeout=10 FATAL: hudson.plugins.git.GitException: Error performing command: /usr/local/bin/git ls-remote -h g...@github.com:everyscape/Mobile.git release hudson.util.IOException2: hudson.plugins.git.GitException: Error performing command: /usr/local/bin/git ls-remote -h g...@github.com:everyscape/Mobile.git release at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:459) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:357) at hudson.scm.SCM.poll(SCM.java:374) ... Caused by: hudson.plugins.git.GitException: Error performing command: /usr/local/bin/git ls-remote -h g...@github.com:everyscape/Mobile.git release at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1414) ... Caused by: java.io.IOException: Cannot run program "/usr/local/bin/git": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(Unknown Source) ... Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) ... I presume this fails because it is looking for /usr/local/bin/git on the Windows master node. When I manually build the job with that configuration - git works fine. If I switch the job's configuration to use the "Default" git executable (git.exe), then polling works fine, but when the job tries to run on the Mac then the git commands fail (since git.exe is not found on the Mac). So, until this issue is resolved somehow, either a) no jobs are started automatically, but they all build successfully when launched manually, or b) jobs are started automatically - but then they all fail to build. The job in question clones a specific branch of a repository from github. It is restricted to work on a slave node with the label of "iOS". There is a mac slave node with that label. We are running the latest LTS version (1.565.1) of Jenkins on a Windows server. FYI - this behavior worked fine on an older (1.x) version of this plugin. Thanks, Chuck Environment: Windows master, Mac slave Project: Jenkins Priority: Major Reporter: Charles Doucette 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
[JIRA] [git] (JENKINS-20512) Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins
Charles Doucette commented on JENKINS-20512 Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins I've experienced this problem in a different way. Our jenkins installation (master node) is on a Windows machine. We also have a mac mini running a slave node. There are two installations of git that are configured - one is for "Windows" and the other is for "Mac". We must define which installation of git to use for each job - or the wrong one is used and the git commands fail. We also do SCM polling. With Git plugin 1.5, git polling on the Windows machine works fine. With Git plugin 2.0, it attempts to use the Mac installation of git on Windows to do the polling, and the polling fails. 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] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
Charles Doucette commented on JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) I believe the directory is fine. The file reference should be relative to the workspace directory. The job is running on a mac slave node. Apparently, unlike the directory organization on the master node, it uses workspace instead of jobs as a top-level directory. Also, instead of having a workspace subdirectory, the directory matching the jobname is the workspace. Anyhow, the new plugin works, so I believe the issue is resolved. Thanks! 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] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
Charles Doucette
commented on JENKINS-17563
java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
FYI - I believe the configuration of the plugin (and the jobs that used it) have been completely changed.
Now the team token and api token is expected on the global jenkins configuration page (where you give every pair a name),
and on the job configuration, you select a token pair name.
On the old plugin, there was no global configuration and the team token and api token were listed in every project.
Anyhow, this is the current job output (with debug settings):
Started by user cdoucette
EnvInject - Loading node environment variables.
Building remotely on macmini-05 in workspace /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS
Uploading to testflight
File: /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS/Engineering/iOS/UScapeIt/UScapeIt.app.ipa
DSYM: /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS/Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip
POST Request: testflight.TestflightUploader$UploadRequest@f1f930c[filePath=Engineering/iOS/UScapeIt/UScapeIt.app.ipa,dsymPath=Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip,apiToken=***,teamToken=***,notifyTeam=true,buildNotes=This is the latest build of UScapeit (for iOS) which was built by Jenkins UScapeit-TestFlight 3.0.130.3
,file=/Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS/Engineering/iOS/UScapeIt/UScapeIt.app.ipa,dsymFile=/Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS/Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip,lists=UScapeIt,replace=false,proxyHost=,proxyUser=,proxyPass=,proxyPort=0,debug=true]
POST Answer: {
"bundle_version": "2.5 (87)",
"install_url": "https://testflightapp.com/install/52d0cb8f907775bb088ead1a407ab269-NDk1OTc5NQ/",
"config_url": "https://testflightapp.com/dashboard/builds/complete/4959795/",
"created_at": "2013-05-15 20:36:19",
"device_family": "iPhone",
"notify": true,
"team": "EveryScape",
"minimum_os_version": "4.3",
"release_notes": "This is the latest build of UScapeit (for iOS) which was built by Jenkins UScapeit-TestFlight 3.0.130.3\n",
"binary_size": 6580333
}
Testflight Upload speed: 4.54Mbps
Testflight Install Link: https://testflightapp.com/install/52d0cb8f907775bb088ead1a407ab269-NDk1OTc5NQ/
Testflight Configuration Link: https://testflightapp.com/dashboard/builds/complete/4959795/
Finished: SUCCESS
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] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
Charles Doucette created JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: testflight Created: 10/Apr/13 2:05 PM Description: Ever since a few versions ago - I have been unable to upload an application build to testflight. Here is the log - complete with debug: Started by user anonymous EnvInject - Loading node environment variables. Building remotely on macmini-05 in workspace /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS Uploading to testflight File: Engineering/iOS/UScapeIt/UScapeIt.app.ipa DSYM: Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip POST Request: testflight.TestflightUploader$UploadRequest@8d5f3bf[filePath=Engineering/iOS/UScapeIt/UScapeIt.app.ipa,dsymPath=Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip,apiToken=***,teamToken=***,notifyTeam=true,buildNotes=This is the latest build of UScapeit (for iOS) which was built by Jenkins UScapeit-TestFlight 3.0.126.49 ,file=Engineering/iOS/UScapeIt/UScapeIt.app.ipa,dsymFile=Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip,lists=UScapeIt,replace=false,proxyHost=,proxyUser=,proxyPass=,proxyPort=0,debug=true] java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) Here is a log from the machine - proving to me that the files actually exist: bash-3.2$ hostname macmini-05.mok3.com bash-3.2$ pwd /Users/Shared/JenkinsSlave/Home/workspace/UScapeit-iOS bash-3.2$ ls Engineering/iOS/UScapeIt/UScapeIt.app.* Engineering/iOS/UScapeIt/UScapeIt.app.dSYM.zip Engineering/iOS/UScapeIt/UScapeIt.app.ipa Environment: Mac OSX: bash-3.2$ uname -a Darwin macmini-05.mok3.com 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64 Project: Jenkins Priority: Major Reporter: Charles Doucette 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-15014) TestFlight automatically replaces old builds
Charles Doucette created JENKINS-15014 TestFlight automatically replaces old builds Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: testflight Created: 31/Aug/12 5:58 PM Description: I just defined a new Jenkins project to upload a build to testflight. I did not change the existing project's build #. After rebuilding the latest sources and uploading to testflight, it replaced the existing build, even though I specified nothing for the value of "replace", and according to the UploadAPI, the default value of the "replace" parameter is false. FYI - my team name is EveryScape, the product is UScapeit, and the replaced build # was/is 53. Environment: Mac OSX 10.8 (Mountain Lion) - Jenkins slave Project: Jenkins Labels: plugin Priority: Minor Reporter: Charles Doucette 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
