[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Steven Shipton commented on JENKINS-38777 Re: Signing for "Unity-iPhone" requires a development team I managed to work around this issue by supplying the team as a command line argument. In Advanced Xcode build options -> Custom xcodebuild arguments Add DEVELOPMENT_TEAM=XXX where XXX = your developer prefix code You can get your prefix code from the Apple developer center: https://developer.apple.com/account/ios/identifier/bundle then pick an app to expand and copy the value from Prefix 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] [google-storage-plugin] (JENKINS-23670) Please add option to remove prefix from local path when performing Classic Upload
Title: Message Title Steven Shipton assigned an issue to Matthew Moore Jenkins / JENKINS-23670 Please add option to remove prefix from local path when performing Classic Upload Change By: Steven Shipton Assignee: MatthewMoore Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-storage-plugin] (JENKINS-23670) Please add option to remove prefix from local path when performing Classic Upload
Title: Message Title Steven Shipton commented on JENKINS-23670 Re: Please add option to remove prefix from local path when performing Classic Upload I changed the assignee to one of the maintainers to see if we can get any feedback. Maintainers are listed as Matthew Moore and Nghia Tran 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] [unity3d-plugin] (JENKINS-20349) Be able to specify Unity3D path per slave without installation on master
Steven Shipton commented on JENKINS-20349 Be able to specify Unity3D path per slave without installation on master Thanks for the clarification, changing to a directory path worked. The error message implied UNITY_WINDOWS was a path to an executable. I think my initial confusion was compounded by the fact that the values entered on the system configuration under 'Unity3d installations' are for the master and these values should be overridden per node. I don't have Unity installed on the master so was not sure an empty 'Installation directory' would be valid. It seems validation is working on the system configuration page as entering e.g. the windows path here on a non-windows master results in the following error message: 'Not a directory C:\Program Files (x86)\Unity\'. This same is not true on the node configuration page but that seems like a Jenkins issue rather than a plugin issue. The following would help prevent further user error (please consider as a feature request): Change error message from 'FATAL: Executable not found UNITY_WINDOWS' to 'directory not found UNITY_WINDOWS' A tooltip for Installation directory explaining that it does not need to be set and can be overridden per node Update to wiki documentation clarifying configuring nodes 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] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Steven Shipton commented on JENKINS-25765 Plugin does not appear as post build action or flexible publish action as of 1.2.0 Thanks, that fixed it. Java 7 hasn't been required until now so perhaps should be added to the documentation for this plugin, unless this is a Jenkins requirement? 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] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Steven Shipton updated JENKINS-25765 Plugin does not appear as post build action or flexible publish action as of 1.2.0 Change By: Steven Shipton (11/Dec/14 3:06 PM) Environment: Jenkins1.590 Java6 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] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Steven Shipton resolved JENKINS-25765 as Fixed Plugin does not appear as post build action or flexible publish action as of 1.2.0 Change By: Steven Shipton (11/Dec/14 3:05 PM) Status: Open Resolved Resolution: Fixed 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-plugin] (JENKINS-25913) Please modify clean after checkout behaviour to clean only tracked files
Steven Shipton created JENKINS-25913 Please modify clean after checkout behaviour to clean only tracked files Issue Type: Improvement Assignee: Nicolas De Loof Components: git-plugin Created: 04/Dec/14 2:42 PM Description: Currently 'clean after checkout' does 3 things: 1) Delete un-ignored untracked files and directories (similar to git clean -df) 2) Delete ignored untracked files and directories (similar to git clean -xdf) 3) Reset tracked files (similar to git reset) I would like to only do #3. It would also be useful to do #1 and #3 without doing #2. This is because we are using Unity which creates a lot of library files which we are happy to persist between builds. These files are required and take a long time to generate but do not affect the build outcome so are safe to leave. The file path is added to .gitignore. It may make sense to add a 'clean' behaviour and a 'reset' behaviour with somewhere we can pass our own parameters. Environment: Linux master, Mac PC slaves. Jenkins 1.590 Project: Jenkins Priority: Minor Reporter: Steven Shipton 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-plugin] (JENKINS-25913) Please modify clean after checkout behaviour to optionally clean ignored, un-ignored and tracked files
Steven Shipton updated JENKINS-25913 Please modify clean after checkout behaviour to optionally clean ignored, un-ignored and tracked files Change By: Steven Shipton (04/Dec/14 2:44 PM) Summary: Pleasemodifycleanaftercheckoutbehaviourto optionally clean only ignored,un-ignoredand trackedfiles 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] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Steven Shipton created JENKINS-25765 Plugin does not appear as post build action or flexible publish action as of 1.2.0 Issue Type: Bug Assignee: Unassigned Components: hockeyapp-plugin Created: 24/Nov/14 5:43 PM Description: After updating I could not find 'Upload to HockeyApp' as an option under the flexible publish action which I am currently using. Also could not find 'Upload to HockeyApp' as an option under post build actions. Downgraded to 1.1.0 and it is back. Environment: Jenkins 1.590 Project: Jenkins Priority: Major Reporter: Steven Shipton 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] [google-storage] (JENKINS-23670) Please add option to remove prefix from local path when performing Classic Upload
Steven Shipton updated JENKINS-23670 Please add option to remove prefix from local path when performing Classic Upload Changed from request to bug report as this is breaking 3rd party services which use the path. I.e. they interpret the \ as folders and not part of the filename Change By: Steven Shipton (11/Jul/14 6:16 PM) Issue Type: Improvement Bug 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] [google-storage] (JENKINS-23669) For Classic Upload it is not possible to use a folder within a bucket
Steven Shipton created JENKINS-23669 For Classic Upload it is not possible to use a folder within a bucket Issue Type: Bug Assignee: Unassigned Components: google-storage Created: 03/Jul/14 1:47 PM Description: Local file local_file.txt Specify remote path like: gs://my-bucket/my-folder The file gets added under my-bucket with filename "my-folder\local_file.txt" and not added to my-folder as intended. Folders do work with Build Log Upload Environment: Master on Linux instance Building on slave on Windows 8 machine Project: Jenkins Priority: Major Reporter: Steven Shipton 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] [google-storage] (JENKINS-23670) Please add option to remove prefix from local path when performing Classic Upload
Steven Shipton created JENKINS-23670 Please add option to remove prefix from local path when performing Classic Upload Issue Type: Improvement Assignee: Unassigned Components: google-storage Created: 03/Jul/14 1:55 PM Description: E.g. local file is Build/target/web/result.txt Upload to gs://my-cloud The filename in the cloud is "Build\target\web\result.txt" The desired filename in the cloud is "result.txt" Another plugin which handles this is the Flexible Publish plugin which has an additional field 'remove prefix' which will be removed prior to upload, so we could specify "Build/target/web" in this field to get the desired behaviour. https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin Please also note that ideally the path folder separator would be platform independent. I.e. we specify "Build/target/web" and this will work on Windows and Linux based slaves. Environment: Master on Linux instance Slave on Windows 8 machine Project: Jenkins Priority: Major Reporter: Steven Shipton 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-20941) Stored git credentials not used when submodule is updated
Steven Shipton updated JENKINS-20941 Stored git credentials not used when submodule is updated Change By: Steven Shipton (08/Apr/14 4:33 PM) Environment: Windows78slaves Cannotreproduceon Macslave (seecomments) ReproducedonRHELLinux6.5 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] [testflight] (JENKINS-20264) Testflight plugin hangs job forever if Testflightapp.com is having performance issues
Steven Shipton commented on JENKINS-20264 Testflight plugin hangs job forever if Testflightapp.com is having performance issues A consequence of this issue is that a manual abort of the build will not release the lock the JVM has on the file. So aborting and trying again causes an error when trying to delete the file (e.g. with git checkout/clean) or overwrite. 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.
