[JIRA] [xcode-plugin] (JENKINS-25433) Xcodebuild sigining fails
Reinhard Karbas commented on JENKINS-25433 Xcodebuild sigining fails Actually the only proper fix would be the third reply in the last link: http://stackoverflow.com/questions/26497863/xcode-6-1-error-while-building-ipa-using-testflight-app/26499526#26499526 Officially the resource rules are deprecated and I have seen another post where Apple has rejected a submission because of the included resource rules 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] [core] (JENKINS-25767) Build location restrictions are not stored with 1.590
Reinhard Karbas created JENKINS-25767 Build location restrictions are not stored with 1.590 Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Nov/14 8:26 PM Description: After installing the latest version (1.590) whenever I change a job the label / build machine restriction where the job can run is no longer stored in the job definition and the job runs on master instead on the appropriate slave I had to go back to 1.588 to have my build restrictions stored and handled properly again Environment: SLES 11 SP3 Jenkins master server Project: Jenkins Labels: configuration build Priority: Blocker Reporter: Reinhard Karbas 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Reinhard Karbas commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration I see the same issue after upgrading from 1.588 to 1.590 I have the same plugins in both versions and it works with 1.588 and is broken in 1.590 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Reinhard Karbas updated JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Change By: Reinhard Karbas (24/Nov/14 10:14 PM) Attachment: Jenkins-plugins-rk.doc 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Reinhard Karbas commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Added my list of plugins as attachment (jenkins-plugins-rk.doc) 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-plugin] (JENKINS-25433) Xcodebuild sigining fails
Reinhard Karbas reopened JENKINS-25433 Xcodebuild sigining fails I do not agree to close this issue as not being a bug Fact is that xcodesigning is called with a deprecated parameter and Apple listing in their TN that apps with a resource plist in them will be rejected We worked our way around now by creating a separate configuration to pull in the correct signing certificate without having to enter it in the xcode plugin However the plugin needs to be fixed to run codesigning without the resource rules Change By: Reinhard Karbas (10/Nov/14 3:52 PM) Resolution: NotADefect Status: Closed Reopened 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-plugin] (JENKINS-25433) Xcodebuild sigining fails
Reinhard Karbas commented on JENKINS-25433 Xcodebuild sigining fails I really need this fixed ASAP, it is starting to block load productions!! 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-24874) Xcode plugin hangs when using xcode6
Reinhard Karbas resolved JENKINS-24874 as Not A Defect Xcode plugin hangs when using xcode6 After creating the missing shared schemas for 2 of the xCode projects the build now works properly Change By: Reinhard Karbas (02/Oct/14 5:07 PM) Status: Open Resolved Resolution: NotADefect 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-24874) Xcode plugin hangs when using xcode6
Reinhard Karbas closed JENKINS-24874 as Not A Defect Xcode plugin hangs when using xcode6 Change By: Reinhard Karbas (02/Oct/14 5:08 PM) Status: Resolved Closed 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-24874) Xcode plugin hangs when using xcode6
Reinhard Karbas reopened JENKINS-24874 Xcode plugin hangs when using xcode6 After protests from the community I am re-opening the issue to get some sort of timeout implemented for xcodebuild to find schemas and fail the build if it times out. Change By: Reinhard Karbas (02/Oct/14 7:29 PM) Resolution: NotADefect Status: Closed Reopened 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-24874) Xcode plugin hangs when using xcode6
Reinhard Karbas created JENKINS-24874 Xcode plugin hangs when using xcode6 Issue Type: Bug Assignee: Unassigned Components: xcode Created: 26/Sep/14 2:48 PM Description: We have several components to build in one Jenkins job calling the xCode plugin several times The first two builds work, however the 3rd instance of the build gets stuck after the clean and never gets to the build step First build: openssl-ios $ /usr/bin/xcodebuild -version Xcode 6.0.1 Build version 6A317 Cleaning build directory: /Users/Jenkins/Ansible/Mobile3rdParty/openssl-ios/build/Release-iphoneos === == Available provisioning profiles openssl-ios $ /usr/bin/security find-identity -p codesigning -v 1) A0C22EDB47D2DFC413DCD56967B86D28B1374342 "Developer ID Application: Siemens Enterprise Communications GmbH Co. KG" 2) C19DB47077CAC502936224069C5218D77D163404 "iPhone Developer: Simon Hall (BDNNEYZ3AQ)" 3) F25A1E6F9A4774208A8C590C1953493BDEE6F005 "iPhone Distribution: Siemens Enterprise Communications, Inc." 3 valid identities found == Available SDKs openssl-ios $ /usr/bin/xcodebuild -showsdks OS X SDKs: OS X 10.9 -sdk macosx10.9 iOS SDKs: iOS 8.0 -sdk iphoneos8.0 iOS Simulator SDKs: Simulator - iOS 8.0 -sdk iphonesimulator8.0 == Available schemes openssl-ios $ /usr/bin/xcodebuild -list -project openssl.xcodeproj Information about project "openssl": Targets: crypto ssl Build Configurations: Debug Release Distribution If no build configuration is specified and -scheme is not passed then "Release" is used. Schemes: crypto ssl === Going to invoke xcodebuild:target: ALL, sdk: DEFAULT, project: openssl.xcodeproj, configuration: Release, clean: YES, archive:NO, symRoot: DEFAULT, configurationBuildDir: DEFAULT, codeSignIdentity: DEFAULT openssl-ios $ /usr/bin/xcodebuild -alltargets -project openssl.xcodeproj -configuration Release clean build === CLEAN TARGET crypto OF PROJECT openssl WITH CONFIGURATION Release === Second build: Cleaning build directory: /Users/Jenkins/Ansible/Mobile3rdParty/ZipArchive/build/Release-iphoneos === == Available provisioning profiles ZipArchive $ /usr/bin/security find-identity -p codesigning -v 1) A0C22EDB47D2DFC413DCD56967B86D28B1374342 "Developer ID Application: Siemens Enterprise Communications GmbH Co. KG" 2) C19DB47077CAC502936224069C5218D77D163404 "iPhone Developer: Simon Hall (BDNNEYZ3AQ)" 3) F25A1E6F9A4774208A8C590C1953493BDEE6F005 "iPhone Distribution: Siemens Enterprise Communications, Inc." 3 valid identities found == Available SDKs ZipArchive $ /usr/bin/xcodebuild -showsdks OS X SDKs: OS X 10.9 -sdk macosx10.9 iOS SDKs: iOS 8.0 -sdk iphoneos8.0 iOS Simulator SDKs: Simulator - iOS 8.0 -sdk iphonesimulator8.0 == Available schemes ZipArchive $ /usr/bin/xcodebuild -list -project ZipArchive.xcodeproj Information about project "ZipArchive": Targets: ZipArchive Build Configurations: Debug Distribution Release If no build configuration is specified and -scheme is not passed then "Debug" is used. Schemes: ZipArchive === Going to invoke xcodebuild:target: ZipArchive, sdk: DEFAULT, project: ZipArchive.xcodeproj, configuration: Release, clean: YES, archive:NO, symRoot: DEFAULT, configurationBuildDir: DEFAULT, codeSignIdentity: DEFAULT ZipArchive $ /usr/bin/xcodebuild -target ZipArchive -project ZipArchive.xcodeproj -configuration Release clean build === CLEAN TARGET ZipArchive OF PROJECT ZipArchive WITH CONFIGURATION Release === Third build: Cleaning build directory: /Users/Jenkins/Ansible/Mobile3rdParty/WebRTC/trunk/build/Release-iphoneos === == Available provisioning profiles trunk $
[JIRA] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Reinhard Karbas commented on JENKINS-23660 Attached log in Jenkins email incomplete What's the planned release date for 2.39? 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] [core] (JENKINS-23263) Move hudson.tasks.junit to a bundled plugin
Reinhard Karbas commented on JENKINS-23263 Move hudson.tasks.junit to a bundled plugin I don't think it is an email ext plugin problem, the token macro does not find the values: ERROR: Publisher hudson.plugins.emailext.ExtendedEmailPublisher aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at hudson.plugins.emailext.plugins.content.TestCountsContent.evaluate(TestCountsContent.java:50) at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:189) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:182) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:233) at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:71) at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:717) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:474) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:292) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:283) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:235) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1786) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) 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] [core] (JENKINS-23263) Move hudson.tasks.junit to a bundled plugin
Reinhard Karbas commented on JENKINS-23263 Move hudson.tasks.junit to a bundled plugin After going from version 1.575 to 1.578 now it seems the values for TEST_COUNTS is not set properly in Jenkins anymore and my email does not get generated properly Based on the description of this fix I assume this is the issue as the functionality was moved out to a new plugin However the name of the plugin is not shown anywhere What do I need to install to get this to work again? 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] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Reinhard Karbas commented on JENKINS-23660 Attached log in Jenkins email incomplete Which version of the plugin will contain 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] [core] (JENKINS-24426) Jenkins version 1.575 killing processes at end of shell script
Reinhard Karbas commented on JENKINS-24426 Jenkins version 1.575 killing processes at end of shell script Thanks for the info One more question: Should I use this switch for Jenkins on the master job or should it be a parameter on the slave machines where I need to disable that behavior? 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] [core] (JENKINS-24426) Jenkins version 1.575 killing processes at end of shell script
Reinhard Karbas created JENKINS-24426 Jenkins version 1.575 killing processes at end of shell script Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: core, slave-setup Created: 25/Aug/14 9:50 PM Description: It looks to me like the fix for Killing processes started by builds on Unix was broken as of 1.553. (issue 22641) has broken the way how Jenkins scripts are executed on a Linux host With version 1.575 when the shell script running the commands exits it now sends signal 15 which kills all child processes that have been started rendering our Linux test system unusable as sshd is being killed. This was not the case in 1.574, which I had to revert to to get this working properly again. Environment: Linux Jenkins Server, Linux slave Project: Jenkins Priority: Major Reporter: Reinhard Karbas 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] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Reinhard Karbas commented on JENKINS-23660 Attached log in Jenkins email incomplete Sorry for that When I update my Jenkins version I normally also update all the plugins Fact is that it still works with the older version of the plugin (I have several builds now where the log is zipped and attached properly) However with the newer version of the plugin the functionality is broken 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] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Reinhard Karbas updated JENKINS-23660 Attached log in Jenkins email incomplete Change By: Reinhard Karbas (04/Jul/14 10:37 AM) Priority: Minor Major Component/s: core 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] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete
Reinhard Karbas commented on JENKINS-23660 Attached log in Jenkins email incomplete The problem is not caused by the newer Jenkins version, but by a bug in the email-ext plugin I downgraded my plugin from 2.38.1 to 2.37.2.2 and the email is working correctly The log is zipped, attached and is complete The problem seems to happen when log files reach a certain size (2 MB?) 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] [core] (JENKINS-23660) Attached log in Jenkins email incomplete
Reinhard Karbas created JENKINS-23660 Attached log in Jenkins email incomplete Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: core, email-ext Created: 02/Jul/14 8:03 PM Description: I recently upgraded my Jenkins server from 1.559 to 1.570 and now the attached logs for the build jobs that run on the MAC are incomplete I had them attached as compressed file using the email-ext plugin, but with this version of Jenkins parts of the log are missing When attaching the uncompressed log I only get the first 2 MB of the log, which on the server has a size of about 14 MB Either the plugin has a problem or the log is not flushed out of memory before processing the post jobs. There are no error messages in the Jenkins log file The version of the email-ext plugin is 2.38.1 For now I am not attaching the log file to my job emails so I have to click on the link in the email to check the output Environment: Server SLES 11 SP2, client MAC OS X Mavericks Project: Jenkins Priority: Minor Reporter: Reinhard Karbas 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] [core] (JENKINS-23660) Attached log in Jenkins email incomplete
Reinhard Karbas commented on JENKINS-23660 Attached log in Jenkins email incomplete Please explain what LTS compared to bleeding edge means The version of Jenkins that I am using is officially released! 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] [core] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas commented on JENKINS-23094 HTTP error 405 when trying to restart ssh host When can I expect a fix for this and who can fix it? 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] [http_request] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas updated JENKINS-23094 HTTP error 405 when trying to restart ssh host Change By: Reinhard Karbas (28/May/14 4:27 PM) Priority: Major Blocker 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] [http_request] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas commented on JENKINS-23094 HTTP error 405 when trying to restart ssh host I just tried with the latest version (1.565) and it is still now working When trying it with Firefox instead of IE I see following message on the screen: POST is required for hudson.slaves.SlaveComputer.doLaunchSlaveAgent When I push the button to try to post again it works, but only on Firefox When will someone look at this to fix it? Until it is fixed I will have to stay on version 1.559! 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] [master-slave] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas updated JENKINS-23094 HTTP error 405 when trying to restart ssh host Change By: Reinhard Karbas (28/May/14 4:29 PM) Component/s: master-slave Component/s: http_request 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] [core] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas commented on JENKINS-23094 HTTP error 405 when trying to restart ssh host The problem is there is nothing in the log files I can see The only output I have is the one already stored in here The best output is the one I got from Mozilla with the Post error and the try Posting button which then makes it possible to restart the client I have the Server on a SLES 11 SP2 machine and for this test I am working with an Ubuntu client I manually disconnect the session and then push the launch slave agent button which leads to the error shown here If there is any additional logging I could turn on or some other file I could check please let me know 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] [http_request] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas commented on JENKINS-23094 HTTP error 405 when trying to restart ssh host This is still broken with 1.564! 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.
