[JIRA] (JENKINS-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins
Title: Message Title Tomonari Nakamura resolved as Fixed Jenkins / JENKINS-49396 NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins Change By: Tomonari Nakamura Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins
Title: Message Title Tomonari Nakamura commented on JENKINS-49396 Re: NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins Sergey Berezhnoy I'm a maintainer of backlog plugin. Sorry for late reply. I've fixed this problem and released new version 2.3. Please update the backlog plugin and try again. Thank you for your report. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins
Title: Message Title Tomonari Nakamura assigned an issue to Tomonari Nakamura Jenkins / JENKINS-49396 NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins Change By: Tomonari Nakamura Assignee: Tomonari Nakamura Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-36451) Repository Browser URL not saved in Project Pipeline Configuration
Title: Message Title Tomonari Nakamura commented on JENKINS-36451 Re: Repository Browser URL not saved in Project Pipeline Configuration I was worried about this issue too, so I have found a cause and fixed it. Please see PRs in Issue Links above. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] [ec2-plugin] (JENKINS-30208) Can't launch spot slave instance with aws-java-sdk 1.10.*
Title: Message Title Tomonari Nakamura created an issue Jenkins / JENKINS-30208 Can't launch spot slave instance with aws-java-sdk 1.10.* Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 29/Aug/15 5:50 PM Priority: Critical Reporter: Tomonari Nakamura I couldn't a launch spot instance with latest ec2-plugin. I investigated the cause by debuging on local machine and found that requestSpotInstances failed with a following error message. com.amazonaws.AmazonServiceException: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. (Service: AmazonEC2; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: cd0cd93d-cdc6-45d9-8cdd-5a5b72ed1416) As a result of a more detail investigation, a LaunchSpecification#setSecurityGroups caused the problem. When I commented out the code, I could launch an spot instance without the error ( of course, I couldn't access the instance because of lack of an appropriate security group ). workaround I downgraded version of aws-java-sdk to 1.9.40 written in pom.xml. It happens when the library whose version is 1.10.* or later is used. So I downgraded it manually and
[JIRA] [ec2-plugin] (JENKINS-19059) [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)
Title: Message Title Tomonari Nakamura commented on JENKINS-19059 Re: [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access) I have fixed this plugin to use with a master deployed internally and run it for over a year. A branch which includes my fix is https://github.com/ikikko/ec2-plugin/tree/JENKINS-19059/ssh-launcher-for-spot-instance . If there are some people who are interested in this fix and want to use it, I try to send it as a pull request. 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] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Tomonari Nakamura commented on JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session I've tried to use my fixed winstone, and broken stylesheet isn't appearing for over a week. So, I send a pull request (https://github.com/jenkinsci/winstone/pull/9 ). Check it and merge if no problem, please. 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] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Tomonari Nakamura commented on JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session I think that a problem may be sending content-type header when http response is 304 in winstone. Looking a capture http://imgur.com/9Y11bqz, css files are interpreted as 'text/html', but should be 'text/css'. According to RFC, the 304 response should not include non-releated header. If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. For example, Plack ( which is web app framework by Perl ) excludes Content-Type / Content-Length / Content-Disposition headers. https://metacpan.org/source/MIYAGAWA/Plack-1.0024/lib/Plack/Middleware/ConditionalGET.pm#L19 So, I fix a source code to exclude content-type when 304, and trying it in my using Jenkins server. https://github.com/ikikko/winstone/commit/1fedebd8095de85a378640f71c3de4bce2e25cae If no problem for a week, I'll send a pull request this. Currently, content-type header is normal and no problem occurs for three days. https://cacoo.com/diagrams/J5lvJfdIi8t9UCof It's ok that you fix in main repository source code before sending my pull request. At which time, consider about other headers (Content-length, content-disposition, and so on), please. 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.
