[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18027) HP Application Automation Tools no longer works with latest Jenkins update
Rahul Goyal commented on JENKINS-18027 HP Application Automation Tools no longer works with latest Jenkins update The same happens with me on Windows Platform . 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-18671) Clock Difference broken on Manage Nodes page
Florian Doersch commented on JENKINS-18671 Clock Difference broken on Manage Nodes page same here, time differences between "3 mo 7 days behind" to "43 years ahead" . 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] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Adrien CLERC commented on JENKINS-17931 cvs rlog files in /tmp are not deleted Thanks for the quick patch. Unfortunately, I won't be able to do a local build, due to a lack of resources (both time and platform). I don't know if someone can provide me a nightly build. Anyway, it seems good for me. Does the build failed from BuildHive matter? 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Rolf Geuenich updated JENKINS-18686 Missing delete button for post build step I don't have a delete button. I've jenkins 1.522 and email-ext 2.30.2. I use jenkins with Firefox 22.0 but IE shows the same result. Maybe a problem caused by the german language? Change By: Rolf Geuenich (11/Jul/13 7:10 AM) Attachment: 2013-07-11_09-03-36_Jenkins.png 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] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Sascha Vogt commented on JENKINS-17931 cvs rlog files in /tmp are not deleted I don't know how all these various Jenkins instances for Jenkins work but the working build including the latest snapshot is available here: https://jenkins.ci.cloudbees.com/job/plugins/job/cvs-plugin/ws/target/ If this solves your issue, please let us 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18686) Missing delete button for post build step
Rolf Geuenich updated JENKINS-18686 Missing delete button for post build step I've used "Quick Locale Switcher" to see jenkins in english and have the same result. Change By: Rolf Geuenich (11/Jul/13 7:18 AM) Attachment: 2013-07-11_09-16-35_Jenkins_en.png 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] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Robert Kleinschmager commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers I also have this problem: all maven2/maven3 jobhave disappeared, when I try to create a new job of type Build a maven2/3 project the same exceptions occurs 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] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Robert Kleinschmager updated JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers Change By: Robert Kleinschmager (11/Jul/13 7:27 AM) Priority: Major Critical 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] [teamconcert] (JENKINS-18691) Team Concert plugin is adding components to a workspace
Julian Payne commented on JENKINS-18691 Team Concert plugin is adding components to a workspace Heather - that does indeed fix my problem - I should have known this - it is complicated but I realize that it is not a problem of the plugin. Please close this issue. If you have a chance to discuss with the RTC team it would be nice to have the default behaviour being that when you choose just a subset of components the flow is scoped appropriately. 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-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
Nicolas De Loof created JENKINS-18701 winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Jul/13 7:45 AM Description: http://github.com/jenkinsci/winstone/commit/26c7de06a9be7eea8d2c959f0366b2d287d99388 changed logging framework to use java.util.logger, then level switched from (1:9) range to (Integer.MIN_VALUE:MAX_VALUE). setting JENKINS_DEBUG_LEVEL to 5 in jenkins sysconif, expecting INFO, result in FINEST logging. actual impact on jenkins probably was hidden by JENKINS-16952. Project: Jenkins Priority: Major Reporter: Nicolas De Loof 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-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
Nicolas De Loof commented on JENKINS-18701 winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL see https://github.com/jenkinsci/winstone/pull/10 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] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Robert Kleinschmager commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers solved it, you also need to update the Maven Integration plugin/Maven Project plugin to version 1.522 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] [configurationslicing] (JENKINS-18702) Support for Execute ant target slicer
Andreas Ebbert-Karroum created JENKINS-18702 Support for Execute ant target slicer Issue Type: New Feature Affects Versions: current Assignee: mdonohue Components: configurationslicing Created: 11/Jul/13 8:28 AM Description: It would be nice, if not only the ant version can be sliced, but also the complete build step. Project: Jenkins Priority: Major Reporter: Andreas Ebbert-Karroum 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-18671) Clock Difference broken on Manage Nodes page
Marcel Beister commented on JENKINS-18671 Clock Difference broken on Manage Nodes page @Andréas Berg: #10771 can have many reasons that lead to the same problem (remote-fs error) and differences in system time can lead to error in network communication. Maybe there is also an error if the system just thinks that the system time is different, but I'm also not really convinced regarding that theory 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-18671) Clock Difference broken on Manage Nodes page
Marcel Beister edited a comment on JENKINS-18671 Clock Difference broken on Manage Nodes page @Andréas Berg: #10771 can have multiple reasons that lead to the same problem (remote-fs error) and differences in system time can lead to errors in network communication. Maybe there is also an error if the system just thinks that the system time is different, but I'm also not really convinced regarding that theory 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] [tap] (JENKINS-18703) TAP Plugin Table of Contents
Ralph Bolton created JENKINS-18703 TAP Plugin Table of Contents Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: tap Created: 11/Jul/13 8:34 AM Description: Could the TAP Plugin (optionally?) have a table of contents on the page? We have some jobs with thousands of tests in a dozen .tap files; finding the file you want on the page is pretty tedious, so a table of contents at the top of the page (with hyperlinks to anchors on the page) would be super-useful. Project: Jenkins Priority: Minor Reporter: Ralph Bolton 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-18213) Copying an existing job to a new one gives an error woth Status Code: 500
Uwe Schneider commented on JENKINS-18213 Copying an existing job to a new one gives an error woth Status Code: 500 This problem also occurs, when "Build a maven 2/3 project" is selected. 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-18213) Copying an existing job to a new one gives an error woth Status Code: 500
kepa uriarte commented on JENKINS-18213 Copying an existing job to a new one gives an error woth Status Code: 500 I have this issue aswell at 1.511 when deleting a project. 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Marco Ambu commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process I can see that this is assigned to component dashboard-view which is a plugin. Are you using the dashboard-view plugin to display your default job page in Jenkins? If not, you need to choose another component to get this bug looked at. 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-18070) Unable to load http://localhost:8080 with fresh installation
Marco Ambu updated JENKINS-18070 Unable to load http://localhost:8080 with fresh installation If you loaded a fresh war file, probably you don't have the dashboard-view plugin installed... therefore I have changed the component to core, not sure if there is a better one. Change By: Marco Ambu (11/Jul/13 8:49 AM) Component/s: core Component/s: dashboard-view 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-18068) Cannot access the jenkins menue, no dashboard functionality!!!
Marco Ambu updated JENKINS-18068 Cannot access the jenkins menue, no dashboard functionality!!! It seems that this issue does not have anything to do with the dashboard-view plugin. Changing component to core... not sure if there is a better one. Change By: Marco Ambu (11/Jul/13 8:50 AM) Component/s: core Component/s: dashboard-view 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-17181) A list of all bugs/issues per project
Marco Ambu updated JENKINS-17181 A list of all bugs/issues per project Removed the dashboard-view plugin component Change By: Marco Ambu (11/Jul/13 8:51 AM) Component/s: core Component/s: dashboard-view 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] [job-dsl-plugin] (JENKINS-18704) Add support for port allocator plugin
Jens Hausherr created JENKINS-18704 Add support for port allocator plugin Issue Type: New Feature Affects Versions: current Assignee: Jens Hausherr Components: job-dsl-plugin Created: 11/Jul/13 9:01 AM Description: It would be nice if the DSL supported the port-allocator plugin to generate concurrently executable jobs that otherwise would have to compete for port numbers. Project: Jenkins Priority: Major Reporter: Jens Hausherr 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] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne created JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: teamconcert Created: 11/Jul/13 9:04 AM Description: I have a multi-configuration project that is configured to run a job with different JDK versions that is configured as shown below: - Source Code Management Rational Team Concert (RTC) RTC repository connection (julianpa...@fr.ibm.com@https://rtcdemeter.francelab.fr.ibm.com:9443/jazz) Just accept and fetch from a build workspace Build workspace Configuration Matrix JDK IBM-JDK-7 Oracle-JDK-7 IBM-JDK-6 The problem seems to come from the fact that the "top-level" build: --- Started by user julianpa...@fr.ibm.com Building on master in workspace /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace RTC : checkout... RTC Checkout : Source control setup RTC Checkout : Accepting changes into workspace "JenkinsRunAsfTests10" ... RTC Checkout : Fetching files to fetch destination "/data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace" ... RTC Checkout : Fetching Completed Triggering IBM-JDK-7 Triggering Oracle-JDK-7 IBM-JDK-7 completed with result FAILURE Oracle-JDK-7 completed with result FAILURE Finished: FAILURE Then the individual builds try to do a checkout in their private workspace: --- Started by upstream project "RunAsfTests10" build number 2 originally caused by: Started by user julianpa...@fr.ibm.com Building on master in workspace /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/jdk/IBM-JDK-7 RTC : checkout... RTC Checkout : Source control setup RTC Checkout : Accepting changes into workspace "JenkinsRunAsfTests10" ... FATAL: RTC : checkout failure: Cannot create sandbox at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/jdk/IBM-JDK-7 because one already exists at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace com.ibm.team.filesystem.client.FileSystemStatusException: Status ERROR: com.ibm.team.filesystem.client code=0 Cannot create sandbox at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/jdk/IBM-JDK-7 because one already exists at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace null at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileArea(CopyFileAreaManager.java:309) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileArea(CopyFileAreaManager.java:1) at com.ibm.team.filesystem.client.internal.SharingManager.register(SharingManager.java:1002) at com.ibm.team.build.internal.hjplugin.rtc.RepositoryConnection.checkout(RepositoryConnection.java:363) Due Date: 12/Jul/13 12:00 AM Fix Versions: current Project: Jenkins Priority: Major Reporter: Julian Payne 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
[JIRA] [email-ext] (JENKINS-18695) Provide a diagnostic if there are broken or malformed tokens in the email template
stephenconnolly commented on JENKINS-18695 Provide a diagnostic if there are broken or malformed tokens in the email template I have asked our customer which it was they encountered. 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] [ssh-slaves] (JENKINS-18706) ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel
ssbarnea created JENKINS-18706 ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 11/Jul/13 9:19 AM Description: Suddenly Jenkins and ssh-slaves stopped working completly. Log shows only Jul 11, 2013 10:16:13 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel pikachu java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1316) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) I checked and ssh connection works between master and slave, here is the proof, the auth.log from the slave: Jul 11 10:16:45 sorins sshd[29280]: reverse mapping checking getaddrinfo for dote-02.80.10.in-addr.arpa [10.80.225.152] failed - POSSIBLE BREAK-IN ATTEMPT! Jul 11 10:16:45 sorins sshd[29280]: Accepted publickey for xenbuild from 10.80.225.152 port 42968 ssh2 Jul 11 10:16:45 sorins sshd[29280]: pam_unix(sshd:session): session opened for user xenbuild by (uid=0) Jul 11 10:17:01 sorins CRON[29460]: pam_unix(cron:session): session opened for user root by (uid=0) Jul 11 10:17:02 sorins CRON[29460]: pam_unix(cron:session): session closed for user root Jul 11 10:18:27 sorins sshd[29426]: Received disconnect from 10.80.225.152: 11: disconnected by user Jul 11 10:18:27 sorins sshd[29280]: pam_unix(sshd:session): session closed for user xenbuild Environment: jenkins=1522 ssh-slaves=0.27 Project: Jenkins Priority: Blocker Reporter: ssbarnea 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] [job-dsl-plugin] (JENKINS-18462) Add support for URL trigger/Github Push trigger plugin
Jens Hausherr assigned JENKINS-18462 to Justin Ryan Add support for URL trigger/Github Push trigger plugin Change By: Jens Hausherr (11/Jul/13 9:27 AM) Assignee: JensHausherr JustinRyan 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] [job-dsl-plugin] (JENKINS-18491) Add support for advanced project configuration and timeouts to DSL
Jens Hausherr assigned JENKINS-18491 to Justin Ryan Add support for advanced project configuration and timeouts to DSL Change By: Jens Hausherr (11/Jul/13 9:27 AM) Assignee: JensHausherr JustinRyan 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] [job-dsl-plugin] (JENKINS-18491) Add support for advanced project configuration and timeouts to DSL
Jens Hausherr resolved JENKINS-18491 as Fixed Add support for advanced project configuration and timeouts to DSL Has been merged to master Change By: Jens Hausherr (11/Jul/13 9:29 AM) Status: InProgress 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18334) Add Build using SBT as build step
Jens Hausherr resolved JENKINS-18334 as Fixed Add Build using SBT as build step Implemented and merged to master Change By: Jens Hausherr (11/Jul/13 9:30 AM) 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18462) Add support for URL trigger/Github Push trigger plugin
Jens Hausherr resolved JENKINS-18462 as Fixed Add support for URL trigger/Github Push trigger plugin Implemented and merged to master Change By: Jens Hausherr (11/Jul/13 9:30 AM) 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18695) Provide a diagnostic if there are broken or malformed tokens in the email template
stephenconnolly updated JENKINS-18695 Provide a diagnostic if there are broken or malformed tokens in the email template Attached is the job config of a job that reproduces the issue Change By: stephenconnolly (11/Jul/13 9:41 AM) Attachment: James_FOO_5_config.xml 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] [job-dsl-plugin] (JENKINS-18492) Inception: Create DSL build step to add DSL Job execution as step
Jens Hausherr commented on JENKINS-18492 Inception: Create DSL build step to add DSL Job execution as step The queue() method executes jobs after they have been created if I am not wrong? The idea here is that I can generate a DSL job (usng the initial DSL that sets up the base jobs) that tracks and generates/deletes Jobs for feature branches or similar. 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] [clone-workspace] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Yinghua Wang commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel I had this problem when I witch my slave node with a low end system (an embedded system, 1GHz CPU, 1G RAM, Fedora OS). All things were well before I replaced it. So I'm sure this is caused by the java memory usage. After some searching from internet, I added one option to the salve node advanced "JVM Options" with "-Xmx256m". And this problem is gone. I don't think it is applied for others, it is depended on user's case, some one has this error because java can't get enough memory, and other may has this error because java exhaust system memory. 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-18671) Clock Difference broken on Manage Nodes page
Richard Mortimer commented on JENKINS-18671 Clock Difference broken on Manage Nodes page I'm seeing the same issue on 1.522. My master and slaves all run NTP and manual inspection of times shows that each slave computer is definitely within a second of the master. The web interface shows differences around 1 month 30 days ahead or behind. I have checked and confirmed that the slaves are running the slave.jar that is bundled with 1.522 but the problem still persists. I have both Linux and Windows slaves and each report the same problem. All of the Linux master/slave computers are running IcedTea6 1.12.5 (java 1.6.0_27). 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-18671) Clock Difference broken on Manage Nodes page
Richard Mortimer commented on JENKINS-18671 Clock Difference broken on Manage Nodes page Looks like this is caused by the fix for JENKINS-18438 https://github.com/jenkinsci/jenkins/commit/735713801b130fe247cf17bbca7b4561e41b1d13 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-18671) Clock Difference broken on Manage Nodes page
Richard Mortimer assigned JENKINS-18671 to Kohsuke Kawaguchi Clock Difference broken on Manage Nodes page Change By: Richard Mortimer (11/Jul/13 10:27 AM) Assignee: KohsukeKawaguchi 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] [xunit] (JENKINS-18575) xUnit failed to parse a JUnit .xml report without any debug in log
Piotr Kral commented on JENKINS-18575 xUnit failed to parse a JUnit .xml report without any debug in log it's duplicate off https://issues.jenkins-ci.org/browse/JENKINS-18095 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] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
Piotr Kral commented on JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 Rollback from 1.60 to 1.58 fixed it for me, but it would be nice to have it working 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-18641) People View does Not Populate (makeStaplerProxy)
Love Nyberg commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Same thing on Debian 7, Jenkins ver. 1.522 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] [custom-tools] (JENKINS-18707) CustomTools plugin doesn't work properly on Multi-configuration builds
Oleg Nenashev created JENKINS-18707 CustomTools plugin doesnt work properly on Multi-configuration builds Issue Type: Bug Assignee: Oleg Nenashev Components: custom-tools, customtools-plugin Created: 11/Jul/13 10:48 AM Description: Tool is being installed on the master-job, but there's no modification of environment variables in the configuration-jobs Project: Jenkins Priority: Major Reporter: Oleg Nenashev 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-18641) People View does Not Populate (makeStaplerProxy)
Love Nyberg updated JENKINS-18641 People View does Not Populate (makeStaplerProxy) Change By: Love Nyberg (11/Jul/13 10:50 AM) Labels: jenkins user Environment: WindowsServer2008 ,Debian7,Ubuntu12.04,CentOS6.4 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] [warnings] (JENKINS-18708) Warnings-Plugin could not distinguish multiple doxygen warning files.
Jens Bohrmann created JENKINS-18708 Warnings-Plugin could not distinguish multiple doxygen warning files. Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 11/Jul/13 10:59 AM Description: I have a project with 3 different doxygen documentations. Each of them has it's own warnings-file. For example Projects\Doxygen\warning.txt, Projects\Doxygen\ModuleTestsWarning.txt, Projects\Doxygen\IntegrationTestsWarning.txt. The Project page has several "Doxygen Warnings" links on the left side but they all link to the same page and the all link to the same page "jenkins/job/Hit1k-1_V01/warnings10" where it says that there are 15 new Warnings, but it is not posible to see in which file. If I click the link with these 15 new warnings i come to page "warnings10Result/new/?" where it says, that there are 0 new warnings. So it seem as if the plugin mixes the information of the three warning-files. Environment: Windows 2003 Server, Jenkins 1.522 Warnings 4.26 Project: Jenkins Priority: Major Reporter: Jens Bohrmann 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process If "dashboard-view" is the default Jenkins view (the "Standard Jenkins jobs list") then this is correct, assuming that's where the problem is (versus some other part of Jenkins that transacts with the dashboard-view plugin). 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic edited a comment on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process If "dashboard-view" is the default Jenkins view (appears so, looking at a snapshot of the "Standard Jenkins jobs list") then this is correct, assuming that's where the problem is (versus some other part of Jenkins that transacts with the dashboard-view plugin). 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] [job-dsl-plugin] (JENKINS-18709) Support rvm plugin for building Ruby projects in RVM controlled env
Jens Hausherr created JENKINS-18709 Support rvm plugin for building Ruby projects in RVM controlled env Issue Type: New Feature Affects Versions: current Assignee: Jens Hausherr Components: job-dsl-plugin Created: 11/Jul/13 11:40 AM Description: Please extend the DSL by a method rvm() to provide a rvm controlled environment for building Ruby projects Project: Jenkins Priority: Minor Reporter: Jens Hausherr 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-18641) People View does Not Populate (makeStaplerProxy)
sogabe commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) I created pull a request https://github.com/jenkinsci/jenkins/pull/844 . It'll fix this issue but may be workaround. I'm not expert of _javascript_. 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] [github] (JENKINS-18710) Let Jenkins auto-manage hook URLs - never adds webhook to enterprise github
Nathan McDonald created JENKINS-18710 Let Jenkins auto-manage hook URLs - never adds webhook to enterprise github Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: github Created: 11/Jul/13 12:06 PM Description: Have set up github in jenkins configuration, providing: Let Jenkins auto-manage hook URLs API URL: http://github.mydomain.com/api/v3/ username: jenkins Password: the jenkins user's git password OAuth token: the jenkins user's oauth token Clicking Test Credential says 'Verified' When I add a new job that connects to a repo on our github http://github.mydomain.com/MYORG/myproject.git and to only build: Build when a change is pushed to GitHub It doesn't get registered in the github enterprise hooks for that repository. Have ensured the jenkins user is in MYORG/owners team in github, which as full read/write/admin access. If I manually add the jenkins hook to the webhooks in github enterprise, it successfully kicks off builds when I push to github. Have tried turning on logging in jenkins to trace what is happening, but there doesn't seem to be any errors or warning anywhere in logs coming back: Have added logger with ALL on: com.cloudbees.jenkins.GitHubPushTrigger com.cloudbees.jenkins.GitHubRepositoryName org.kohsuke.github but the only output I get is: Jul 11, 2013 12:50:43 PM com.cloudbees.jenkins.GitHubRepositoryName create FINE: Object is GitHubRepositoryhost=github.mydomain.com,username=MYORG,repository=myproject Jul 11, 2013 12:50:43 PM com.cloudbees.jenkins.GitHubRepositoryName create FINE: URL matches java.util.regex.Matcher[pattern=https?://(^/+)/(^/+)/(^/+)\.git region=0,47 lastmatch=http://github.mydomain.com/MYORG/myproject.git] Jul 11, 2013 12:50:43 PM com.cloudbees.jenkins.GitHubRepositoryName create FINE: Constructing from URL http://github.mydomain.com/MYORG/myproject.git Jul 11, 2013 12:50:43 PM com.cloudbees.jenkins.GitHubRepositoryName create FINE: Object is GitHubRepositoryhost=github.mydomain.com,username=MYORG,repository=myproject Jul 11, 2013 12:50:43 PM com.cloudbees.jenkins.GitHubRepositoryName create FINE: URL matches java.util.regex.Matcher[pattern=https?://(^/+)/(^/+)/(^/+)\.git region=0,47 lastmatch=http://github.mydomain.com/MYORG/myproject.git] Jul 11, 2013 12:50:43 PM com.cloudbees.jenkins.GitHubRepositoryName create FINE: Constructing from URL http://github.mydomain.com/MYORG/myproject.git Environment: Targeting Github Enterprise Version 11.10.315 Jenkins version: 1.522 Git server plugin: 1.1 GitHub API Plugin: 1.42 GitHub plugin: 1.7 Jenkins GIT client plugin: 1.0.7 Jenkins GIT plugin: 1.4.0 Project: Jenkins Priority: Major Reporter: Nathan McDonald 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-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
Jesse Glick commented on JENKINS-18701 winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL Requesting backport to LTS since these messages tend to fill the log file with junk and flush out genuine errors, making support much harder. 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-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
Jesse Glick updated JENKINS-18701 winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL Change By: Jesse Glick (11/Jul/13 12:09 PM) Labels: lts-candidate 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] [subversion] (JENKINS-15249) Missing support for externals in 1.4.2 for subversion working copy version 1.7
Jan Linnenkohl resolved JENKINS-15249 as Fixed Missing support for externals in 1.4.2 for subversion working copy version 1.7 This has been fixed in JENKINS-13790 and works for 1.45+ version. Change By: Jan Linnenkohl (11/Jul/13 12:17 PM) Status: Open Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-15249) Missing support for externals in 1.4.2 for subversion working copy version 1.7
Jan Linnenkohl closed JENKINS-15249 as Fixed Missing support for externals in 1.4.2 for subversion working copy version 1.7 Ticket closed. Change By: Jan Linnenkohl (11/Jul/13 12:18 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/groups/opt_out.
[JIRA] [core] (JENKINS-18070) Unable to load http://localhost:8080 with fresh installation
sogabe commented on JENKINS-18070 Unable to load http://localhost:8080 with fresh installation java -jar jenkins.war --httpPort=your port 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] [warnings] (JENKINS-18711) Multiline warning should result in multiple warnings
Johannes Heger created JENKINS-18711 Multiline warning should result in multiple warnings Issue Type: Improvement Assignee: Ulli Hafner Components: warnings Created: 11/Jul/13 12:47 PM Description: The W3C CSS validator outputs multiline messages: One output per .css file - if at lest one error is present - and with all errors collected togehter. See log example. The regex is able to catch the whole block, thats good! We like to report each error separate. But the groovy snippet can only return one "new Warning(...)". It would be nice if the groovy snippet is able to return multipe warnings. E.g. per function "add(new Warning(...))" or a list, which prevents me from reformatting the log before parsing. Log example: Sorry! We found the following errors (6) URI : file:/jenkins/s7/workspace/CCF2FW/ccf/WebContent/common/tiny_mce/themes/advanced/skins/default/ui.css Line : 40 .defaultSkin .mceButtonDisabled .mceIcon Property -ms-filter doesn#39;t exist : #39;alpha(opacity=30)#39; Line : 40 .defaultSkin .mceButtonDisabled .mceIcon Parse Error opacity=30) Line : 70 .defaultSkin .mceSplitButtonDisabled .mceAction, .defaultSkin .mceSplitButtonDisabled a.mceOpen Property -ms-filter doesn#39;t exist : #39;alpha(opacity=30)#39; Line : 70 .defaultSkin .mceSplitButtonDisabled .mceAction, .defaultSkin .mceSplitButtonDisabled a.mceOpen Parse Error opacity=30) Line : 108 .defaultSkin .mceBlocker Property -ms-filter doesn#39;t exist : #39;alpha(opacity=50)#39; Line : 108 .defaultSkin .mceBlocker Parse Error opacity=50) Kind regards, Johannes Project: Jenkins Priority: Minor Reporter: Johannes Heger 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-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
Mike Hambidge edited a comment on JENKINS-12124 random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded I'm uploading zipped logs from my server that appears to demonstrate the issue. I went ahead and enabled "ALL" level for the top level "hudson" log, so be warned that there is a lot of cruft in the log files. tomcat7-stderr.2013-07-10-with-errors.zip - This log includes the "NoClassDefFoundError" for the hudson/plugins/analysis/core/AbstractProjectAction. I usually only see the error after restarting the actual server. My theory being that this causes a lot of churn (disk, cpu, etc.) when Tomcat comes up at this time and thus introduces different timing, allowing for the problem to occur (of course, there's always alternate explanations). Note that the problem is just easier to reproduce after a system reboot, but its not exclusive to it. tomcat7-stderr.2013-07-10-no-errors.zip - I then restarted Tomcat and all the Jobs loaded without error. 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] [job-dsl-plugin] (JENKINS-18709) Support rvm plugin for building Ruby projects in RVM controlled env
Jens Hausherr assigned JENKINS-18709 to Justin Ryan Support rvm plugin for building Ruby projects in RVM controlled env Implemented feature w/ tests. Pull request already there. Change By: Jens Hausherr (11/Jul/13 12:58 PM) Assignee: JensHausherr JustinRyan 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] [teamconcert] (JENKINS-18691) Team Concert plugin is adding components to a workspace
Scott Cowan resolved JENKINS-18691 as Not A Defect Team Concert plugin is adding components to a workspace Change By: Scott Cowan (11/Jul/13 1:21 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/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-18712) Adding feature to URLTrigger
sandy thomas created JENKINS-18712 Adding feature to URLTrigger Issue Type: New Feature Assignee: Gregory Boissinot Components: urltrigger Created: 11/Jul/13 1:39 PM Description: Currently URLTrigger only checks the content-type of the url specified, based on the result will trigger the build. Wish to add feature to check if workspace is out-of-date with the base scm repository before triggering the build. Any Pointers or documents are welcome. Project: Jenkins Priority: Minor Reporter: sandy thomas 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] [email-ext] (JENKINS-18695) Provide a diagnostic if there are broken or malformed tokens in the email template
Alex Earl commented on JENKINS-18695 Provide a diagnostic if there are broken or malformed tokens in the email template Actually, I'm pretty sure from the code that it will not replace anything in the email text. I think in that case, I should just make the body be an error message, since it won't be useful for the email to have no replaced tokens anyway, what do you think? 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Alex Earl commented on JENKINS-18686 Missing delete button for post build step Can you look at the Jenkins logs and see if there is any exception in there when you view the job config page? 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] [build-pipeline] (JENKINS-18510) JavaScript Compiles script Tag Inline
Jonathan Brecher commented on JENKINS-18510 _javascript_ Compiles script Tag Inline How do I get (and install) the 1.3.5 release? When I go to Jenkins Manage Jenkins Manage Plugins in my Jenkins installation, it still shows 1.3.4.1 as the latest available? 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Rolf Geuenich edited a comment on JENKINS-18686 Missing delete button for post build step Hi, I don't find any message in the log files when accessing or saving the configuration page of this job. Is there a way to activate some debug messages? 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Rolf Geuenich commented on JENKINS-18686 Missing delete button for post build step Hi, I don't find any message in the log files when accessing or saving the configuration. Is there a way to activate some debug messages? 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] [github] (JENKINS-18710) Selected Let Jenkins auto-manage hook URLs, but never adds webhook to enterprise github
Nathan McDonald updated JENKINS-18710 Selected Let Jenkins auto-manage hook URLs, but never adds webhook to enterprise github Change By: Nathan McDonald (11/Jul/13 2:11 PM) Summary: Selected LetJenkinsauto-managehookURLs - ,but neveraddswebhooktoenterprisegithub 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-18671) Clock Difference broken on Manage Nodes page
Richard Mortimer assigned JENKINS-18671 to Richard Mortimer Clock Difference broken on Manage Nodes page Change By: Richard Mortimer (11/Jul/13 2:13 PM) Assignee: KohsukeKawaguchi RichardMortimer 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Alex Earl commented on JENKINS-18686 Missing delete button for post build step If there are no exceptions, then debug messages won't really help. Can you open a _javascript_ console and see if there are any errors there? 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] [build-pipeline] (JENKINS-18510) JavaScript Compiles script Tag Inline
Marcell Jusztin commented on JENKINS-18510 _javascript_ Compiles script Tag Inline I had the same problem. Go to http://updates.jenkins-ci.org/download/plugins/build-pipeline-plugin/. Download the plugin, then go to the plugin manager and click on the advanced tab. There you can manually upload and install it in seconds. 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] [ccm] (JENKINS-13534) Clicking on the build number does not display the CCM result summary.
Bruno P. Kinoshita started work on JENKINS-13534 Clicking on the build number does not display the CCM result summary. Change By: Bruno P. Kinoshita (11/Jul/13 2:28 PM) Status: Open InProgress 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] [ccm] (JENKINS-13534) Clicking on the build number does not display the CCM result summary.
Bruno P. Kinoshita commented on JENKINS-13534 Clicking on the build number does not display the CCM result summary. Hi @Sridhar The 2.x version of the plug-in had custom screen, built based on other plug-ins. The 3.x version of the plug-in relies on analysis-pom (Static Code ... plug-in). It's using the same foundation as PMD, FindBugs and other static analysis plug-ins. By default, the information you're looking for is now displayed in the CCM Warnings page. Actually, there's even more information in that page now. Can you use that page to get the information you're looking for? 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] [ccm] (JENKINS-13592) Details part of each ccm warning always displays all file
Bruno P. Kinoshita commented on JENKINS-13592 Details part of each ccm warning always displays all file Quick note, just tested the alpha version in my Windows Box, with the latest CCM, and it seems to be working fine :o) Cutting a release on Friday if no one finds any blocker issue. 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] [ssh-slaves] (JENKINS-8856) StreamCorruptedException
Jesse Glick commented on JENKINS-8856 StreamCorruptedException Oops, did not consider that possibility! Thanks Kohsuke for fixing. 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Jesse Glick commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Note that dashboard-view 2.8 includes a fix for JENKINS-15858; it is unclear whether or not this bug is a duplicate. 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] [email-ext] (JENKINS-18695) Provide a diagnostic if there are broken or malformed tokens in the email template
stephenconnolly commented on JENKINS-18695 Provide a diagnostic if there are broken or malformed tokens in the email template +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.
[JIRA] [email-ext] (JENKINS-18686) Missing delete button for post build step
Rolf Geuenich commented on JENKINS-18686 Missing delete button for post build step 16:30:39.268 getAttributeNode() sollte nicht mehr verwendet werden. Verwenden Sie stattdessen getAttribute(). @ http://...:8083/static/fe06bd7c/scripts/yui/button/button-min.js:7 ...is the only waning/error I can see. 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] [build-pipeline] (JENKINS-18510) JavaScript Compiles script Tag Inline
Jonathan Brecher commented on JENKINS-18510 _javascript_ Compiles script Tag Inline Ah, ok. The manual upload link didn't help me because it wants a .hpi file and finding the .hpi file in the first place was exactly my problem. HOWEVER, underneath the manual upload section on that page was another button to Update Site, and clicking that button made the update appear as an option where I expected it. So I'm all set now. (And I see that the bug is indeed fixed.) 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] [build-pipeline] (JENKINS-18510) JavaScript Compiles script Tag Inline
Michael Chamberlain commented on JENKINS-18510 _javascript_ Compiles script Tag Inline Yes, it's fixed for us too. 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] [build-pipeline] (JENKINS-18553) configuration is lost, and no new configuration possible
Michael Chamberlain commented on JENKINS-18553 configuration is lost, and no new configuration possible Yes, it's fixed now. Thank you!! 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Alex Earl commented on JENKINS-18686 Missing delete button for post build step The delete button is actually provided by something in core for each publisher. So, I'm not sure how email-ext couldl stopit from being shown. I can't reproduce it. Can you try disabling other plugins?? 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] [www] (JENKINS-13125) HTTP Content-Range Header one byte past file length
James Ascroft-Leigh
commented on JENKINS-13125
HTTP Content-Range Header one byte past file length
I am using Jenkins 1.521 from the Jenkins APT repository on Ubuntu. I am getting a very similar symptom to the one described here i.e. when trying to view a PDF in the embedded Chrome viewer it is failing.
I have done a couple of experiments which lead me to believe that Jenkins is simply failing to include the units i.e. "bytes" in the content-range header. Is this possibly the problem?
I notice that the headers shown in previous comments don't have a unit so in my reading they don't match the production for content-range-spec in http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html section 14.16 and bytest-unit in http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html section 3.12.
My experiments:
1) Embedded Chrome viewer
Environment:
Ubuntu Raring
Chrome 28
Jenkins 1.521
PDF file: Not linearized, 49KB
Result:
PDF loading progress bar reaches 100% but no pages are shown
2) Embedded Firefox viewer (based on pdf.js)
Environment:
Ubuntu Raring
Firefox 22
Jenkins 1.521
PDF file: Not linearized, 49KB
Result:
PDF displays correctly
3) Standalone pdf.js
Environment:
Ubuntu Raring
Firefox 22
pdf.js mozilla-pdf.js-v0.5.5-1204-g81fa4a0
Jenkins 1.521
PDF file: Not linearized, 49KB
Result:
PDF progress bar reaches about 15% and no pages are ever displayed, _javascript_ exception
4) Patched standalone pdf.js
Environment:
Ubuntu Raring
Firefox 22
pdf.js mozilla-pdf.js-v0.5.5-1204-g81fa4a0 (patched, see below)
Jenkins 1.521
PDF file: Not linearized, 49KB
Result:
PDF displays correctly
Explanation:
After looking into the _javascript_ exception above, I tried a small patch to how pdf.js was parsing the header
diff -ru a/pdfjs/src/network.js b/pdfjs/src/network.js
a/pdfjs/src/network.js 2013-07-01 17:29:31.0 +0100
+++ b/pdfjs/src/network.js 2013-07-11 15:33:06.0 +0100
@@ -187,6 +187,9 @@
if (xhrStatus === PARTIAL_CONTENT_RESPONSE) {
var rangeHeader = xhr.getResponseHeader('Content-Range');
var matches = /bytes (\d+)-(\d+)\/(\d+)/.exec(rangeHeader);
+if (matches == null) {
+ var matches = /(\d+)-(\d+)\/(\d+)/.exec(rangeHeader);
+}
var begin = parseInt(matches1, 10);
pendingRequest.onDone({
begin: begin,
I also tried downloading the artifacts and serving them up from a simple Apache HTTPD. The embedded Chrome viewer, in fact every test, worked fine.
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] [www] (JENKINS-13125) HTTP Content-Range Header one byte past file length
James Ascroft-Leigh
edited a comment on JENKINS-13125
HTTP Content-Range Header one byte past file length
I am using Jenkins 1.521 from the Jenkins APT repository on Ubuntu. I am getting a very similar symptom to the one described here i.e. when trying to view a PDF in the embedded Chrome viewer it is failing.
I have done a couple of experiments which lead me to believe that Jenkins is simply failing to include the units i.e. "bytes" in the content-range header. Is this possibly the problem?
I notice that the headers shown in previous comments don't have a unit so in my reading they don't match the production for content-range-spec in http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html section 14.16 and bytest-unit in http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html section 3.12.
My experiments:
1) Embedded Chrome viewer
Environment:
Ubuntu Raring
Chrome 28
Jenkins 1.521
PDF file: Not linearized, 49KB
Result:
PDF loading progress bar reaches 100% but no pages are shown
2) Embedded Firefox viewer (based on pdf.js)
Environment:
Ubuntu Raring
Firefox 22
Jenkins 1.521
PDF file: Not linearized, 49KB
Result:
PDF displays correctly
3) Standalone pdf.js
Environment:
Ubuntu Raring
Firefox 22
pdf.js mozilla-pdf.js-v0.5.5-1204-g81fa4a0
Jenkins 1.521
PDF file: Not linearized, 49KB
Result:
PDF progress bar reaches about 15% and no pages are ever displayed, _javascript_ exception
4) Patched standalone pdf.js
Environment:
Ubuntu Raring
Firefox 22
pdf.js mozilla-pdf.js-v0.5.5-1204-g81fa4a0 (patched, see below)
Jenkins 1.521
PDF file: Not linearized, 49KB
Result:
PDF displays correctly
Explanation:
After looking into the _javascript_ exception above, I tried a small patch to how pdf.js was parsing the header
diff -ru a/pdfjs/src/network.js b/pdfjs/src/network.js
--- a/pdfjs/src/network.js 2013-07-01 17:29:31.0 +0100
+++ b/pdfjs/src/network.js 2013-07-11 15:33:06.0 +0100
@@ -187,6 +187,9 @@
if (xhrStatus === PARTIAL_CONTENT_RESPONSE) {
var rangeHeader = xhr.getResponseHeader('Content-Range');
var matches = /bytes (\d+)-(\d+)\/(\d+)/.exec(rangeHeader);
+if (matches == null) {
+ var matches = /(\d+)-(\d+)\/(\d+)/.exec(rangeHeader);
+}
var begin = parseInt(matches[1], 10);
pendingRequest.onDone({
begin: begin,
I also tried downloading the artifacts and serving them up from a simple Apache HTTPD. The embedded Chrome viewer, in fact every test, worked fine.
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] [ghprb] (JENKINS-18713) push --force loses build statuses
Iulian Dragos created JENKINS-18713 push --force loses build statuses Issue Type: Bug Affects Versions: current Assignee: Honza Brázdil Components: ghprb Created: 11/Jul/13 3:15 PM Description: I force-pushed to my branch for which I had an open pull request. The plugin didn't pick up my change. When I asked `retest this please`, the build was triggered but no status was added to my commits. It looks like the old shas were used. Here's the parameters I got: sha1:origin/pr/464/merge ghprbActualCommit: 285f72ae5b7b6c9460ccb6fc922789dba4cef2ad ghprbPullId: 464 ghprbTargetBranch: master The actual commit is the previous one (before my push --force). As a result, the pull request (and all its commits) has no build status. Project: Jenkins Priority: Major Reporter: Iulian Dragos 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-18689) slave unstable become online and offline
Alex Gnooshin commented on JENKINS-18689 slave unstable become online and offline Jul 11, 2013 7:16:31 PM jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed WARNING: Channel reader thread: 4appt for + 4appt terminated java.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) ... at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run SynchronousCommandTransport.java:48) 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] [slave-setup] (JENKINS-13869) [Unexpected termination of the channel] for Unix SSH slaves
ssbarnea commented on JENKINS-13869 [Unexpected termination of the channel] for Unix SSH slaves I was able to fix my problem, after spending many hours looking for a way to increase the log level of jenkins. In my case the cause was that the slave setup script was failing, that's added by an optional which runs some commands before starting the slave.jar Still, it seems that jenkins fails ugly when this happens. Another cause was that the slave was not able to run because the build directory was not writable (after swiching from using root to using a different account, obviously the existing files were owned by root). Still, same ugly behaviour and nothing useful in the console. Also, I still have the same problem regarding the clock, which is in sync but jenkins is reporting even 10 days behind on one of the slaves. 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] [msbuild] (JENKINS-18543) Update to newest MSBuild plugin breaks passing of release configurations with spaces in them
Jonathan Zimmerman commented on JENKINS-18543 Update to newest MSBuild plugin breaks passing of release configurations with spaces in them Can you paste the msbuild command line that you get with 1.17? 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] [envinject] (JENKINS-18714) SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable
Luiz Casey
created JENKINS-18714
SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
envinject, subversion
Created:
11/Jul/13 3:41 PM
Description:
When you use a repository url that contains a variable such as https://mysvn/apps/myapp/${SVN_MYAPP_BRANCH} it does not set the SVN_URL and SVN_REVISION variables. If it is set to a non variable https://mysvn/apps/myapp/trunk it works.
Environment:
RHEL5 using Jenkins ver. 1.522 with Subversion Plug-in 1.50
Project:
Jenkins
Priority:
Major
Reporter:
Luiz Casey
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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang created JENKINS-18715 scandir being triggered by FingerPrint.save Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 11/Jul/13 4:14 PM Description: We were experiencing extrem slow fingerprinting in post-build step. It turns out that the include pattern of scm sync configure plugin is triggered by FingerPrint.save() (details see discussion in mailing list1). So the include pattern may significantly impact the speed. Here is a thread dump: Executor #1 for comitdev16 : executing SD-2112 #3" Id=62 Group=main RUNNABLE at java.io.UnixFileSystem.list(Native Method) at java.io.File.list(File.java:973) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1257) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1211) at org.apache.tools.ant.DirectoryScanner.checkIncludePatterns(DirectoryScanner.java:1030) at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:909) - locked org.apache.tools.ant.DirectoryScanner@34cf6c49 at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matchingFilesFrom(PatternsEntityMatcher.java:41) at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matches(PatternsEntityMatcher.java:25) at hudson.plugins.scm_sync_configuration.strategies.AbstractScmSyncStrategy.isSaveableApplicable(AbstractScmSyncStrategy.java:53) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getStrategyForSaveable(ScmSyncConfigurationPlugin.java:277) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationSaveableListener.onChange(ScmSyncConfigurationSaveableListener.java:22) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) at hudson.model.Fingerprint.save(Fingerprint.java:862) - locked hudson.model.Fingerprint@281c2370 at hudson.model.Fingerprint.init(Fingerprint.java:597) at hudson.model.FingerprintMap.create(FingerprintMap.java:90) at hudson.model.FingerprintMap.create(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.get(KeyedDataStorage.java:156) at hudson.model.FingerprintMap.get(FingerprintMap.java:79) at hudson.model.FingerprintMap.get(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108) at hudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65) at hudson.tasks.Fingerprinter$1Record.addRecord(Fingerprinter.java:210) at hudson.tasks.Fingerprinter.record(Fingerprinter.java:254) at hudson.tasks.Fingerprinter.perform(Fingerprinter.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 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:726) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) I think reacting to all SaveableListener.fireOnChange might be too aggressive, since in this paticular case, no configuration changes are involved. 1 https://groups.google.com/forum/#!topic/jenkinsci-users/AftANOOYgt8 Environment: Jenkins 1.518 Project: Jenkins Labels: fingerprints Priority: Minor
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save Careful use of the include pattern may avoid huge negative performance impact. 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang
updated JENKINS-18715
scandir being triggered by FingerPrint.save
Change By:
Hua Zhang
(11/Jul/13 4:19 PM)
Description:
Wewereexperiencingextremslowfingerprintinginpost-buildstep.ItturnsoutthattheincludepatternofscmsyncconfigurepluginistriggeredbyFingerPrint.save()(detailsseediscussioninmailinglist[1]).
Sotheincludepatternmaysignificantlyimpactthespeed.
Hereisathreaddump:{code}Executor#1forcomitdev16:executingSD-2112#3Id=62Group=mainRUNNABLE atjava.io.UnixFileSystem.list(NativeMethod) atjava.io.File.list(File.java:973) atorg.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1257) atorg.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) atorg.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) atorg.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) atorg.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1211) atorg.apache.tools.ant.DirectoryScanner.checkIncludePatterns(DirectoryScanner.java:1030) atorg.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:909) -lockedorg.apache.tools.ant.DirectoryScanner@34cf6c49 athudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matchingFilesFrom(PatternsEntityMatcher.java:41) athudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matches(PatternsEntityMatcher.java:25) athudson.plugins.scm_sync_configuration.strategies.AbstractScmSyncStrategy.isSaveableApplicable(AbstractScmSyncStrategy.java:53) athudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getStrategyForSaveable(ScmSyncConfigurationPlugin.java:277) athudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationSaveableListener.onChange(ScmSyncConfigurationSaveableListener.java:22) athudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) athudson.model.Fingerprint.save(Fingerprint.java:862) -lockedhudson.model.Fingerprint@281c2370 athudson.model.Fingerprint.init(Fingerprint.java:597) athudson.model.FingerprintMap.create(FingerprintMap.java:90) athudson.model.FingerprintMap.create(FingerprintMap.java:45) athudson.util.KeyedDataStorage.get(KeyedDataStorage.java:156) athudson.model.FingerprintMap.get(FingerprintMap.java:79) athudson.model.FingerprintMap.get(FingerprintMap.java:45) athudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108) athudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65) athudson.tasks.Fingerprinter$1Record.addRecord(Fingerprinter.java:210) athudson.tasks.Fingerprinter.record(Fingerprinter.java:254) athudson.tasks.Fingerprinter.perform(Fingerprinter.java:133) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) athudson.model.Run.execute(Run.java:1601) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:241){code}IthinkreactingtoallSaveableListener.fireOnChangemightbetooaggressive,sinceinthispaticularcase,noconfigurationchangesareinvolved.[1]https://groups.google.com/forum/#!topic/jenkinsci-users/AftANOOYgt8
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] [github] (JENKINS-18710) Selected Let Jenkins auto-manage hook URLs, but never adds webhook to enterprise github
Nathan McDonald
commented on JENKINS-18710
Selected Let Jenkins auto-manage hook URLs, but never adds webhook to enterprise github
Have debugged through the plugin. The adder seems to get stuck with empty collection of connections when it hits following code due to enterprise git using different hostname. This would explain why nothing appears in the logs, as most logging appears to be inside the for loops:
com.cloudbees.jenkins.GitHubWebHook.java
//snippet
/**
* Logs in as the given user and returns the connection object.
*/
public IterableGitHub login(String host, String userName) {
if (host.equals("github.com")) {
//do a whole log of logic
} else {
return Collections.GitHub emptyList();
}
}
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] [join] (JENKINS-18717) Promoted build job hangs forever after promotion job finishes
Rick Stokoe created JENKINS-18717 Promoted build job hangs forever after promotion job finishes Issue Type: Bug Assignee: mdonohue Components: join, maven2, promoted-builds Created: 11/Jul/13 4:53 PM Description: Using promoted_builds plugin in build job with manual approval to trigger promotion process which triggers build on another job (deploy). Build (maven2) job triggers promotion job which finishes successfully. Build job hangs indefinitely with following last message to console: Waiting for the completion of deploy Following is logged when deploy job finishes: INFO: deploy #3 main build action completed: SUCCESS Jul 11, 2013 12:26:05 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.IllegalArgumentException: promotion at hudson.maven.ModuleName.fromString(ModuleName.java:97) at hudson.maven.MavenModuleSet.getItem(MavenModuleSet.java:352) at hudson.maven.MavenModuleSet.getItem(MavenModuleSet.java:115) at jenkins.model.Jenkins.getItem(Jenkins.java:2248) at jenkins.model.Jenkins.getItem(Jenkins.java:2271) at hudson.model.Items.fromNameList(Items.java:98) at join.JoinTrigger$DescriptorImpl$RunListenerImpl.notifyJob(JoinTrigger.java:405) at join.JoinTrigger$DescriptorImpl$RunListenerImpl.onCompleted(JoinTrigger.java:398) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178) at hudson.model.Run.execute(Run.java:1552) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) If (promoted) build job is a "free-style" job rather than a maven2 job, build job finishes after promotion job finishes. If join plugin is disabled, promoted build job finishes after promotion job finishes. Project: Jenkins Priority: Major Reporter: Rick Stokoe 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-18718) It isn't clear if you should restart Jenkins after installing a plugin
recampbell created JENKINS-18718 It isnt clear if you should restart Jenkins after installing a plugin Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Jul/13 5:29 PM Description: When you install a plugin, you are given two choices: "install without restart" or "Download and Install after restart"? However, it isn't clear what the right option is. It seems you must know something about Jenkins internals or the internals of plugin you're installing. Project: Jenkins Priority: Major Reporter: recampbell 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] [testlink] (JENKINS-8636) TestLink Plugin FATAL: Error creating test project
Bruno P. Kinoshita resolved JENKINS-8636 as Not A Defect TestLink Plugin FATAL: Error creating test project Closing since it's a problem with the TestLink installation, and not with the plug-in (nor we can hack a fix in the plug-in code, sorry) Change By: Bruno P. Kinoshita (11/Jul/13 5:33 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/groups/opt_out.
[JIRA] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category notes
Bruno P. Kinoshita commented on JENKINS-17608 Test Link plugin, show the test results in the category notes Hi Jeanjean! Fine, thanks, and you? Sure, I'm reviewing the open issues right now. Sorry for taking so long to work on the plug-in again. Let me try to reproduce the issue here. 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] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category notes
Bruno P. Kinoshita commented on JENKINS-17608 Test Link plugin, show the test results in the category notes Jeanjean, I think you can see whether a test passed or not with the test status. What you want is, if a test is failed/blocked, to include some information about the failure/abort cause in the test notes, is that right? 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] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category notes
Bruno P. Kinoshita started work on JENKINS-17608 Test Link plugin, show the test results in the category notes Change By: Bruno P. Kinoshita (11/Jul/13 5:38 PM) Status: Open InProgress 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-18718) It isn't clear if you should restart Jenkins after installing a plugin
Spike Washburn commented on JENKINS-18718 It isnt clear if you should restart Jenkins after installing a plugin This creates UX complexity for novice Jenkins users since they don't understand all the implications of this choice. Possible solutions: Allow plugins to express whether a restart is required and drive the install form based on this If Download and Install after restart will always work, make it the clear default choice (leaving the install without restart as an advance option for Jenkins admins who understand the implications). Once nice UI for this option might be a "pulldown button" which defaults to the safest option, but which allows you to select the other optionsor you can just color the buttons so that one is clearly the suggested choice. 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] [testlink] (JENKINS-13175) Testlink Job Configuration using dropdownlist instead static box
Bruno P. Kinoshita resolved JENKINS-13175 as Wont Fix Testlink Job Configuration using dropdownlist instead static box Hi Victor, unfortunately it would require a lot of _javascript_ hack, as well as handling multiple comboboxes. Feel free to submit a pull request if you are able to work on this feature, but you would have to update the test plans according to the test project selected, and update it if the user changed the project combobox. The issue will be archived, and can be reopen in the future, if anyone is willing to give it a try. Thanks! Change By: Bruno P. Kinoshita (11/Jul/13 5:42 PM) Status: Open Resolved Resolution: WontFix 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] [testlink] (JENKINS-18636) Testlink Plugin - XML RPC too many http requests on big tests plans
Bruno P. Kinoshita started work on JENKINS-18636 Testlink Plugin - XML RPC too many http requests on big tests plans Change By: Bruno P. Kinoshita (11/Jul/13 5:42 PM) Status: Open InProgress 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] [testlink] (JENKINS-18636) Testlink Plugin - XML RPC too many http requests on big tests plans
Bruno P. Kinoshita commented on JENKINS-18636 Testlink Plugin - XML RPC too many http requests on big tests plans Hi Stephane. Perfect issue analysis. Here's the current flow during that XML RPC startup phase. Retrieve project (a call to the XML RPC API that returns the project data) Retrieve test plan and test cases (I believe it's a single call, or maybe one for the test plan and another for the test cases) Filter only automated test cases (IIRC, it's done locally, since the API itself cannot handle it very well) For each test case, retrieve the list of custom fields given in the job configuration page (yuck! I know, but ATM there is no way of retrieving all the test cases plus its custom fields in a single call). Probably that's the reason why you're experiencing this problem. Someone would have to change the current XML RPC API implementation in TestLink, and then we could reduce the number of HTTP requests in the plug-in. Does that make sense? 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] [testlink] (JENKINS-18067) Jenkins Testlink integration broken in 1.9.6 1.9.7 version of testlink
Bruno P. Kinoshita started work on JENKINS-18067 Jenkins Testlink integration broken in 1.9.6 1.9.7 version of testlink Change By: Bruno P. Kinoshita (11/Jul/13 5:51 PM) Status: Open InProgress 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.
