[JIRA] [gerrit-trigger-plugin] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
Curtis Kline commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit I am concerned about this bug being marked "fixed". I am running 2.11.1 of the trigger plugin, and I believe it still exhibits this 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] [s3] (JENKINS-23432) S3 publisher fails with String index out of range error
Curtis Kline created JENKINS-23432 S3 publisher fails with String index out of range error Issue Type: Bug Assignee: Michael Watt Components: s3 Created: 13/Jun/14 6:01 PM Description: Just updated Jenkins to latest LTS release and updated S3 plugin to 0.6. All S3 uploads fail with this error message in the console log: ERROR: Publisher hudson.plugins.s3.S3BucketPublisher aborted due to exception java.lang.StringIndexOutOfBoundsException: String index out of range: -25 at java.lang.String.substring(String.java:1937) at java.lang.String.substring(String.java:1904) at hudson.plugins.s3.S3Profile.upload(S3Profile.java:123) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:174) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1709) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: Jenkins 1.554.2 S3 Plugin 0.6 Project: Jenkins Priority: Major Reporter: Curtis Kline 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-client] (JENKINS-20387) Timeout (10min) on git clone command
Curtis Kline commented on JENKINS-20387 Timeout (10min) on git clone command I just ran into problems with this timeout when one of my repos got particularly large. This is a Windows development project, so a Windows slave has to clone the repo. This takes about 15 minutes (or 1.5 minutes on a Mac!!), and I am unable to figure out how to change the timeout value on my Windows slave. I am using JNLP to connect the slave to the master. Any suggestions would be appreciated. (wishing for a GUI option for controlling the timeout feature) 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] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
Curtis Kline commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit I would be willing to try it out on our test instance. Right now I am removing the Gerrit Trigger from all of the jobs we recently implemented it on due to this bug. Ah well, it was fun while it lasted! (Jenkins 1.509.4 and GT 2.10.1) 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.
