[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: "FATAL: No remotes found!"
OHTAKE Tomohiro created JENKINS-21057 Cannot checkout git repository with submodules: "FATAL: No remotes found!" Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 18/Dec/13 7:49 AM Description: Steps to reproduce Create a free-style project. Set "Git Repository URL". The repository specified should use submodules. In "Additional Behaviours", add "Advanced sub-modules behaviours" and check "Recursively update submodules". Build it. Expected result Workspace should have git working tree and submodules. Actual console log Cloning the remote Git repository Cloning repository git://***/*.git Fetching upstream changes from git://***/*.git Fetching upstream changes from git://***/*.git Checking out Revision 0123456789abcdef0123456789abcdef01234567 (origin/master) FATAL: No remotes found! hudson.plugins.git.GitException: No remotes found! at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getDefaultRemote(CliGitAPIImpl.java:702) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.setupSubmoduleUrls(CliGitAPIImpl.java:863) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:69) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:882) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Actual .git/config [core] repositoryformatversion = 0 filemode = false logallrefupdates = true There is no [remote "origin"] nor [submodule "submodule-name"] sections. Workaround One of the followings: Downgrade git plugin to 1.5 Do not check "Recursively update submodules" Do not checkout git repository with submodules Environment: Master: Jenkins 1.544, Git Plugin 2.0, Ubuntu 13.10 64bit, OpenJDK 1.7.0_25-b30 Slave: CentOS 6.5 64bit, OpenJDK 1.7.0_45, Git 1.7.1 Project: Jenkins Priority: Major Reporter: OHTAKE Tomohiro 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-13538) Build hangs at SVN update occasionally
Shankar R commented on JENKINS-13538 Build hangs at SVN update occasionally If the Slave was invoked in older versions of Jenkins or Hudson, it would have created some (supporting) files in the node's workspace directory. In my setup, If i clear those files and invoke the slave agent again, it checks-out properly without hanging. 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.
scheduled time vs actual time
Hi, I am facing the problem with scheduled build with build periodically settings. I have scheduled the build at */1 * * * * for every minute (testing purpose). But job not executing after one min, its taking different time intervals to execute like this. Success > Console Output #14 Dec 17, 2013 4:10:40 PM Success > Console Output #13 Dec 17, 2013 4:09:44 PM Success > Console Output #12 Dec 17, 2013 4:06:34 PM Success > Console Output #11 Dec 17, 2013 4:03:25 PM Also if I schedule job at 30 10 * * *, It wont execute at 10.30.. Its executing around 11:30. Can anyone help.. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/scheduled-time-vs-actual-time-tp4684660.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- 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] [infrastructure] (JENKINS-21056) Ability to separate build build history of parameterized projects
Michael Rose created JENKINS-21056 Ability to separate build build history of parameterized projects Issue Type: Improvement Assignee: Unassigned Components: infrastructure Created: 18/Dec/13 2:16 AM Description: I'm not sure what component this would fall under so I just chose infrastructure. There are several plugins to generate jobs in Jenkins. The reason being users want to be able to quickly create jobs that follow a standard set of steps. I have taken a different approach. I have made completely parametrized "helper" jobs that my build flow jobs calls. This limits the number of places that configuration changes need to be made. The problem I have found with this approach is that if you have multiple projects calling the same "helper" job, the build history for the "helper" job becomes less useful (e.g. you can't quickly discern trend data). It would be nice if there was a way to separate builds into different buckets. A couple of approaches that came to mind were: A new job type "Link to existing job" This would be similar to copy existing job except the config file(s) would be a link(s). The configuration screen would probably need to display a warning showing the projects that would be affected if changes were made. Parameter based "bucketing" The user can choose the "bucket" they want the build to appear in. Enhance reporters Allow build reporting tools (e.g. the build history list on each project page, the build history list on each node page) filter results based on the build parameters. Thoughts? Project: Jenkins Priority: Minor Reporter: Michael Rose 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] [mail] (JENKINS-21039) NullPointerException in Jenkins Mail Sender
Imesh Gunaratne updated JENKINS-21039 NullPointerException in Jenkins Mail Sender Change By: Imesh Gunaratne (18/Dec/13 1:41 AM) Summary: NullPointerException in Jenkins Mail Sender 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] [clover] (JENKINS-21055) Allow parameter substitution in clover related fields
Michael Rose created JENKINS-21055 Allow parameter substitution in clover related fields Issue Type: Improvement Assignee: stephenconnolly Components: clover Created: 18/Dec/13 1:26 AM Description: Right now I get the following error: Publishing Clover coverage report... Clover xml file does not exist in: /usr/local/jenkins/jobs/Velocity-Alpha-UnitTestCoverage/workspace/x86_64-Linux-2.618/bcc/*/code_coverage called: clover.xml and will not be copied to: /usr/local/jenkins/jobs/Velocity-Alpha-UnitTestCoverage/builds/2013-12-17_10-23-02/clover.xml Could not find 'x86_64-Linux-2.618/bcc/*/code_coverage/clover.xml'. Did you generate the XML report for Clover? I would like to parametrize my project and limit the information that needs to be hard coded. It would be nice if the "Clover report directory" field was able to use parameter substitution and/or wildcards. Project: Jenkins Labels: clover plugin Priority: Minor Reporter: Michael Rose 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-20381) ResultSeeking Strategy "jUnit Suite Name" not working
Bruno P. Kinoshita commented on JENKINS-20381 ResultSeeking Strategy "jUnit Suite Name" not working Hi, not yet. I have to submit a pull request to Jenkins core, to get the suite name back and update the plug-in code as well. Unfortunately I don't think I can do that before holidays. Feel free to submit a pull request or update this issue with other suggestions. Thanks Florian Bruno 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-20381) ResultSeeking Strategy "jUnit Suite Name" not working
Bruno P. Kinoshita stopped work on JENKINS-20381 ResultSeeking Strategy "jUnit Suite Name" not working Change By: Bruno P. Kinoshita (18/Dec/13 1:05 AM) Status: In Progress Open 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-20624) TAP result seeker's include test notes adds poor values
Bruno P. Kinoshita commented on JENKINS-20624 TAP result seeker's include test notes adds poor values It now dumps the Test Set content [1]. What do you think? [1] https://github.com/jenkinsci/testlink-plugin/commit/e1e3eecde910931b3e8523197874ada6764db7a4#diff-9301f7af9923097b10fc0b8b1ed5841cR297 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] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters commented on JENKINS-20891 Websphere Deployer fails to deploy to remote server Reza, that is the correct configuration path syntax. Is there not a "lastSuccessful" directory under the "test" job specified in your file system? What's the path of the test.ear that's built? 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-20599) Handle several testpoints TAP result file
Bruno P. Kinoshita closed JENKINS-20599 as Fixed Handle several testpoints TAP result file Fixed in 3.10 Change By: Bruno P. Kinoshita (18/Dec/13 1:01 AM) 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] [testlink] (JENKINS-20752) TestLink is unable to get the devKey
Bruno P. Kinoshita closed JENKINS-20752 as Fixed TestLink is unable to get the devKey Change By: Bruno P. Kinoshita (18/Dec/13 1:01 AM) 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] [testlink] (JENKINS-20711) Request for a TestLink / plug-in compatibility matrix update
Bruno P. Kinoshita closed JENKINS-20711 as Fixed Request for a TestLink / plug-in compatibility matrix update Fixed Change By: Bruno P. Kinoshita (18/Dec/13 1:00 AM) 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] [git] (JENKINS-21054) IllegalArgumentException related to mavenHome on Git polling
Curtis Kline created JENKINS-21054 IllegalArgumentException related to mavenHome on Git polling Issue Type: Bug Assignee: Nicolas De Loof Attachments: git-polling-error Components: git Created: 18/Dec/13 12:50 AM Description: We have several Maven jobs, and on a new one we set up in the past few days we are seeing some strange errors in the Git polling log. Much of the time the Git polling works fine, but several times per day we get this error (see attached from Git polling log). The "mavenHome" path mentioned in the error message is a valid path on the master, but not on the slaves where this job is actually running (the slave has a significantly different directory structure than the master). I have set the "tool location" for Maven on the slaves to the correct location. Environment: Git plugin 1.5.0 on Jenkins 1.509.4 Project: Jenkins Priority: Major Reporter: Curtis Kline This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters assigned JENKINS-20891 to Greg Peters Websphere Deployer fails to deploy to remote server Change By: Greg Peters (18/Dec/13 12:46 AM) Assignee: Greg Peters 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] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters started work on JENKINS-20891 Websphere Deployer fails to deploy to remote server Change By: Greg Peters (18/Dec/13 12:46 AM) Status: Open In Progress 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] [websphere-deployer] (JENKINS-20875) Jenkins Plugin for WebSphere Deployer ( Remote deployment)
Greg Peters assigned JENKINS-20875 to Greg Peters Jenkins Plugin for WebSphere Deployer ( Remote deployment) Change By: Greg Peters (18/Dec/13 12:43 AM) Assignee: Greg Peters 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] [websphere-deployer] (JENKINS-20875) Jenkins Plugin for WebSphere Deployer ( Remote deployment)
Greg Peters resolved JENKINS-20875 as Not A Defect Jenkins Plugin for WebSphere Deployer ( Remote deployment) This error is related to not having the admin client jar in the jenkins classpath. Change By: Greg Peters (18/Dec/13 12:44 AM) Status: Open Resolved Fix Version/s: current Resolution: Not A Defect 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] [ant] (JENKINS-21053) Incorrect passing of arguments
Edgar Anderson created JENKINS-21053 Incorrect passing of arguments Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: ant Created: 18/Dec/13 12:13 AM Description: One of our builds uses this command within Jenkins: SVN_SRC="svn://svn.usdataworks.com/Repository/$location"; DATE_STR=`date +%Y%m%d-%H%M%S`; SVN_DST="$DATE_STR-$label"; mkdir /usdataworks/dev/$DATE_STR; PATH=.:$PATH udwBuild.sh -c $SVN_SRC -p -r -v $label -t $SVN_DST -j $JAVA_HOME -D "-DkeyStore=../../../../../../../../var/lib/jenkins/.jks/myclearingworks.jks -DkeyAlias=\"key from secure.instantssl.com\" -Dstorepass= -Dkeypass=" /usdataworks/dev/$DATE_STR; rm -rf /usdataworks/dev/$DATE_STR However, an strace shows that by the time ant is called, "-DkeyStore..." has been stripped of the -D, so that ant interprets the remaining "keyStore..." as an ant target and the build fails because that target isn't defined. The ant command ends up being: 5590 execve("/opt/apache-ant-1.8.3/bin/ant", ["ant", "-Dversion.label.core=3.7.1_rc12", "keyStore=../../../../var/lib/jenkins/.jks/myclearingworks.jks", "-DkeyAlias=\\\"key", "from", "secure.instantssl.com\\\"", "-Dstorepass=", "-Dkeypass=", "clean", "build"], [/* 39 vars */]) = 0 We also noticed that, in Jenkins' console output, the command line was shown as: udwBuildApp.sh -p svn://svn.usdataworks.com/Repository/tags/3.6.2.FP1 -a svn://svn.usdataworks.com/Applications/ConfigurationReplicator/trunk -v 0.0.9 -j svn://svn.usdataworks.com/Applications/ConfigurationReplicator/branches/ReleaseCandidates -D '-DkeyStore=../../../../../../../../var/lib/jenkins/.jks/myclearingworks.jks -DkeyAlias="key from secure.instantssl.com" -Dstorepass= -Dkeypass=' In addition to losing the -D in front of keyStore, it looks like Jenkins converted the double quotes we actually typed into single quotes? Environment: CentOS 6.5 x86_64 Oracle Java jdk 1.6.0_31 Ant 1.8.3 Jenkins installed from RPM Project: Jenkins Priority: Blocker Reporter: Edgar Anderson 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] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Sylvain Avril commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Hello, Same issue on Debian Linux Wheezy with a git repository hosted by SCM Manager. This was the first time I set up a job with git. My home config (~/.git/config) was blank. May be making this command fail safe would be enough ? 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-21017) Jenkins CLI update-job misses custom workspace deletion
Jesse Glick updated JENKINS-21017 Jenkins CLI update-job misses custom workspace deletion Change By: Jesse Glick (17/Dec/13 11:24 PM) Labels: gui jenkins cli custom-workspace Component/s: core Component/s: cli 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-21052) l:copyButton does not work
Jesse Glick commented on JENKINS-21052 l:copyButton does not work Note that when I use the minimal sample, the load event is fired, but no other events are. I confirmed that the moviePath is sensible. 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-21052) l:copyButton does not work
Jesse Glick commented on JENKINS-21052 l:copyButton does not work My experiments so far: https://github.com/jglick/jenkins/compare/copyButton-JENKINS-21052 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Jesse Glick commented on JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue BTW the actual thread dump shows an issue in WeakHashMap.HashIterator.hasNext, such as an endless loop. The keySet method does not copy any data, and there is no indication that the array copy overhead is relevant. If I am right, iterating the map directly would not make any difference. What JRE is being used to run Jenkins? If not the most recent Java 7, try updating and see if the issue remains. 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-21052) l:copyButton does not work
Jesse Glick assigned JENKINS-21052 to Kohsuke Kawaguchi l:copyButton does not work Cannot get it to work. While the demo at http://zeroclipboard.org/ is working for me, when I try to load ZC from a Jenkins page, the button simply does nothing when clicked—even when I copy the minimal sample from their site rather than trying to use the more complicated stuff in copyButton.js. Tried upgrading to 1.2.3 without success. Change By: Jesse Glick (17/Dec/13 10:36 PM) Assignee: Jesse Glick Kohsuke Kawaguchi 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] [vsphere-cloud] (JENKINS-20793) add "delete snapshot" build step
Eric Lordahl resolved JENKINS-20793 as Fixed add "delete snapshot" build step Change By: Eric Lordahl (17/Dec/13 10:23 PM) Status: In Progress 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] [vsphere-cloud] (JENKINS-20793) add "delete snapshot" build step
Eric Lordahl stopped work on JENKINS-20793 add "delete snapshot" build step Change By: Eric Lordahl (17/Dec/13 10:17 PM) Status: In Progress Open 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] [vsphere-cloud] (JENKINS-20793) add "delete snapshot" build step
Eric Lordahl started work on JENKINS-20793 add "delete snapshot" build step Change By: Eric Lordahl (17/Dec/13 10:17 PM) Status: Open In Progress 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] [vsphere-cloud] (JENKINS-20793) add "delete snapshot" build step
Eric Lordahl started work on JENKINS-20793 add "delete snapshot" build step Change By: Eric Lordahl (17/Dec/13 10:06 PM) Status: Open In Progress 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] [vsphere-cloud] (JENKINS-19879) Add new build steps
Eric Lordahl closed JENKINS-19879 as Not A Defect Add new build steps Change By: Eric Lordahl (17/Dec/13 10:05 PM) Status: Open Closed Resolution: Not A Defect 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-20769) Failed to execute command Pipe.EOF
SCM/JIRA link daemon commented on JENKINS-20769 Failed to execute command Pipe.EOF Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/remoting/ProxyInputStream.java src/main/java/hudson/remoting/ProxyOutputStream.java http://jenkins-ci.org/commit/remoting/eb3a4c380e695580174ce381a8330e8e2b8a9b2e Log: JENKINS-20769 Trying to fix/suppress some related observed or actual NPEs. java.lang.NullPointerException at hudson.remoting.ProxyOutputStream$Flush$1.run(ProxyOutputStream.java:305) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) 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] [credentials] (JENKINS-21051) Add new credential plugin displays help text in Japanese characters
jasonrobinson created JENKINS-21051 Add new credential plugin displays help text in Japanese characters Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Attachments: jenkins-add_credential_help_text.png Components: credentials Created: 17/Dec/13 9:33 PM Description: Steps To reproduce: From the jenkins home page 1) Click the "Credentials" link on the left or: Manage Jenkins -> Credentials 2) Click "Global Credentials" 3) Click "Add Credentials 4) Choose "Kind: Certificate" 5) Choose the radio button for "Certificate: From a PKCS#12 file on Jenkins master" 6) Click the help icon for the "File" text entry box. Notice that the blue highlighted help text is in Japanese characters, when the rest of the help on this page is in English characters. Jenkinsのマスターノード上でのファイルのパスです。 Environment: Server: ubuntu: 13.04 Tomcat7 Jenkins.war ver. 1.543 Credentials Plugin ver 1.9.4 Client system: Windows8.1 Pro browser: Firefox ver 26.0 Project: Jenkins Labels: credentials help localization Priority: Minor Reporter: jasonrobinson 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-21052) l:copyButton does not work
Jesse Glick created JENKINS-21052 l:copyButton does not work Issue Type: Bug Assignee: Jesse Glick Components: core Created: 17/Dec/13 9:37 PM Description: Prior to 33c8ac4 in 1.514, copyButton.js had extraneous quotes, so the ZeroClipboard Stapler adjunct could not be loaded at all. After that, it is loaded, but (I think as a regression from SECURITY-71) just throws a _javascript_ error when the button is clicked, as can be seen e.g. from the UI Samples plugin: Uncaught TypeError: Cannot call method 'getAttribute' of undefined ZeroClipboard.ready ZeroClipboard.js:245 ZeroClipboard.setHandCursor ZeroClipboard.js:181 (anonymous function) copyButton.js:11 (anonymous function) behavior.js:111 (anonymous function) behavior.js:107 Behaviour.applySubtree behavior.js:93 Behaviour.apply behavior.js:76 (anonymous function) behavior.js:71 window.onload behavior.js:125 Project: Jenkins Labels: stapler _javascript_ regression lts-candidate Priority: Major Reporter: Jesse Glick 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-21052) l:copyButton does not work
Jesse Glick started work on JENKINS-21052 l:copyButton does not work Change By: Jesse Glick (17/Dec/13 9:38 PM) Status: Open In Progress 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] [cli] (JENKINS-21017) Jenkins CLI update-job misses custom workspace deletion
Sagi Sinai-Glazer updated JENKINS-21017 Jenkins CLI update-job misses custom workspace deletion additional-identities plugins has nothing to do with the ticket. It's a CLI issue. And a bit of a GUI issue since it's not being updated properly. Change By: Sagi Sinai-Glazer (17/Dec/13 8:42 PM) Labels: gui jenkins Component/s: cli Component/s: additional-identities 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] [downstream-buildview] (JENKINS-17837) slow startup and rename caused by loading all build.xml history
SCM/JIRA link daemon commented on JENKINS-17837 slow startup and rename caused by loading all build.xml history Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jvnet/hudson/plugins/DownStreamProjectActionFactory.java http://jenkins-ci.org/commit/downstream-buildview-plugin/47801c278f000b34eae5bd9d674029cf470cd8b2 Log: [FIXED JENKINS-17837] Deleting DownStreamProjectActionFactory. It cannot be done efficiently in modern versions of Jenkins. Anyway it has no clear purpose, since DownstreamBuildViewRunListener already adds the action to each new build. Its only purpose seems to have been to retroactively modify builds started before this plugin was installed, which seems both ill-advised and unnecessary. 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] [graphiteintegrator] (JENKINS-21050) "publish to graphite" option missing
Ryan Davis commented on JENKINS-21050 "publish to graphite" option missing I can also successfully test my connection between jenkins and my graphite server using the "Test Connection" button in the "Graphite server" settings block in jenkins config. 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-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Rob van Oostrum commented on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Ran into this as well. Seems unrelated to the upgrade. It's simply that the queue that's persisted when the Jenkins service shuts down causes a deadlock when Jenkins re-initializes. The quick fix for me was to rename the file (this is on Ubuntu) from queue.xml into something like queue.keep (or you could just remove it altogether) 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-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Rob van Oostrum edited a comment on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Ran into this as well. Seems unrelated to the upgrade. It's simply that the queue that's persisted when the Jenkins service shuts down causes a deadlock when Jenkins re-initializes. The quick fix for me was to rename the file (this is on Ubuntu) from queue.xml into something like queue.xml.keep (or you could just remove it altogether). I've had this happen both at Jenkins upgrades, and simply restarting Jenkins after plugin updates, since 1.542 or so. Once in this deadlock, downgrading as far as 1.540 didn't do the trick. Ended up upgrading back to 1.544 and removing queue.xml before restarting. 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-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Rob van Oostrum edited a comment on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Ran into this as well. Seems unrelated to the upgrade. It's simply that the queue that's persisted when the Jenkins service shuts down causes a deadlock when Jenkins re-initializes. The quick fix for me was to rename the file (this is on Ubuntu) from queue.xml into something like queue.keep (or you could just remove it altogether). I've had this happen both at Jenkins upgrades, and simply restarting Jenkins after plugin updates, since 1.542 or so. Once in this deadlock, downgrading as far as 1.540 didn't do the trick. Ended up upgrading back to 1.544 and removing queue.xml before restarting. 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-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Rob van Oostrum edited a comment on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Ran into this as well. Seems unrelated to the upgrade. It's simply that the queue that's persisted when the Jenkins service shuts down causes a deadlock when Jenkins re-initializes. The quick fix for me was to rename the file (this is on Ubuntu) from queue.xml into something like queue.keep (or you could just remove it altogether). I've had this happen both at Jenkins upgrades, and simply restarting Jenkins after plugin updates, since 1.542 or so. 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] [graphiteintegrator] (JENKINS-21050) "publish to graphite" option missing
Ryan Davis created JENKINS-21050 "publish to graphite" option missing Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: graphiteintegrator Created: 17/Dec/13 8:46 PM Description: Installed the plugin, configured the server in the main jenkins config, but none of my jobs have a "publish to graphite" option. My jobs are free-style software projects. Environment: jenkins on linux w/ SDK7 Project: Jenkins Priority: Major Reporter: Ryan Davis 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-21049) Failed tests mark build as failure option resets when changing the configuration
Franck Derunes created JENKINS-21049 Failed tests mark build as failure option resets when changing the configuration Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: testlink Created: 17/Dec/13 7:01 PM Description: I checked the option "Failed tests mark build as failure" and saved. Whenever I open the job configuration again the option becomes unchecked. Project: Jenkins Priority: Major Reporter: Franck Derunes 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] [downstream-buildview] (JENKINS-17837) slow startup and rename caused by loading all build.xml history
SCM/JIRA link daemon resolved JENKINS-17837 as Fixed slow startup and rename caused by loading all build.xml history Change By: SCM/JIRA link daemon (17/Dec/13 7:03 PM) Status: In Progress 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] [git-client] (JENKINS-21015) NullPointerException in Jenkins Git Plugin
Simon Tremblay commented on JENKINS-21015 NullPointerException in Jenkins Git Plugin Only to confirm that the Ignacio Albors workaround is working on my side. If you're running a Ubuntu server: sudo -i su jenkins (default user that is running Jenkins) cd (it will bring you directly in the $HOME folder, by default on my side it is /var/lib/jenkins touch .netrc 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-20993) org.apache.commons.jelly.JellyTagException when Logging in
Scott MacDonald commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I have "Unix user/group database" authentication with Service "sshd". The "test" button reports success, and changing the service to ssh or sshd makes no difference. We use "Project-based Matrix Authorization Strategy" and do not provide "anonymous" users any access, provide "authenticated" users read acess, and typically a few select users get "admin". At the moment, we have resorted to giving everyone full admin, as that appears to o be the the only way to allow folks to use the system (a very temporary workaround) 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Jesse Glick assigned JENKINS-21044 to Oleg Nenashev Throttle Concurrent Builds blocking Jenkins queue I do not actually run this plugin anywhere so I have no real way of confirming whether a given change improves or degrades performance on a large installation. Extending the scope of the lock on propertiesByCategory may avoid overhead, but runs the risk of deadlocks, if foreign calls such as getItem are included. Change By: Jesse Glick (17/Dec/13 6:17 PM) Assignee: Jesse Glick 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Jesse Glick updated JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue Change By: Jesse Glick (17/Dec/13 6:15 PM) Labels: performance 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] [rebuild] (JENKINS-20596) Support rebuilding jobs using promoted builds parameter
steven armstrong commented on JENKINS-20596 Support rebuilding jobs using promoted builds parameter When will this be in the new release really need it... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5452) Whitespace in the user ID
SCM/JIRA link daemon resolved JENKINS-5452 as Fixed Whitespace in the user ID Change By: SCM/JIRA link daemon (17/Dec/13 5:52 PM) Status: In Progress 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] [mercurial] (JENKINS-5452) Whitespace in the user ID
SCM/JIRA link daemon commented on JENKINS-5452 Whitespace in the user ID Code changed in jenkins User: Jesse Glick Path: src/main/resources/hudson/plugins/mercurial/MercurialChangeSetList/index.jelly http://jenkins-ci.org/commit/mercurial-plugin/89f9e5fd842595ed8e0afc1196e53c8690436c63 Log: [FIXED JENKINS-5452] Lack of proper escaping broke display of user names in changelog. 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-21048) Image portlet not collapsible
Kyle Paice created JENKINS-21048 Image portlet not collapsible Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Components: dashboard-view Created: 17/Dec/13 5:51 PM Description: The image portlet is not collapsible. Looking at the page source, the image is placed between the header and content tables for the portlet. Moving the image into the content table fixes the problem. Environment: Windows 7, viewed in Google Chrome Project: Jenkins Priority: Minor Reporter: Kyle Paice 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] [downstream-buildview] (JENKINS-17837) slow startup and rename caused by loading all build.xml history
Jesse Glick assigned JENKINS-17837 to Jesse Glick slow startup and rename caused by loading all build.xml history Change By: Jesse Glick (17/Dec/13 5:42 PM) Assignee: Jesse Glick 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] [downstream-buildview] (JENKINS-17837) slow startup and rename caused by loading all build.xml history
Jesse Glick started work on JENKINS-17837 slow startup and rename caused by loading all build.xml history Change By: Jesse Glick (17/Dec/13 5:42 PM) Status: Open In Progress 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Oleg Nenashev assigned JENKINS-21044 to Jesse Glick Throttle Concurrent Builds blocking Jenkins queue BTW, I confirm that the current implementation may cause huge calculation efforts in the case of big number of jobs with a same category: keySet() causes a useless copy of the data copy to a new array leads to an additional copy of items It makes sense to extend a the cache's lock time, but to iterate the HashMap directly. I'll reassign issue to Jesse Glick, who is an author of https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/10 Jesse, do you have some time to fix the issue? If no, I can do it on my own Change By: Oleg Nenashev (17/Dec/13 5:39 PM) Assignee: Oleg Nenashev Jesse Glick 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] [downstream-buildview] (JENKINS-20890) Saving jobs with huge build history takes a very long time due to unnecessary logging
Jesse Glick resolved JENKINS-20890 as Duplicate Saving jobs with huge build history takes a very long time due to unnecessary logging Change By: Jesse Glick (17/Dec/13 5:36 PM) Status: Open Resolved Resolution: 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] [downstream-buildview] (JENKINS-17837) slow startup and rename caused by loading all build.xml history
Jesse Glick updated JENKINS-17837 slow startup and rename caused by loading all build.xml history Change By: Jesse Glick (17/Dec/13 5:33 PM) Labels: lazy-loading performance 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] [mercurial] (JENKINS-5452) Whitespace in the user ID
Jesse Glick started work on JENKINS-5452 Whitespace in the user ID Change By: Jesse Glick (17/Dec/13 5:30 PM) Status: Open In Progress 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] [downstream-buildview] (JENKINS-20890) Saving jobs with huge build history takes a very long time due to unnecessary logging
Jesse Glick updated JENKINS-20890 Saving jobs with huge build history takes a very long time due to unnecessary logging Change By: Jesse Glick (17/Dec/13 5:31 PM) Labels: performance 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] [mercurial] (JENKINS-5452) Whitespace in the user ID
Jesse Glick assigned JENKINS-5452 to Jesse Glick Whitespace in the user ID Change By: Jesse Glick (17/Dec/13 5:30 PM) Assignee: Kohsuke Kawaguchi Jesse Glick 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] [mercurial] (JENKINS-19481) Add uncompressed option to Mercurial
Jesse Glick resolved JENKINS-19481 as Duplicate Add uncompressed option to Mercurial Change By: Jesse Glick (17/Dec/13 5:23 PM) Status: Open Resolved Resolution: 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Oleg Nenashev commented on JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue Could you briefly describe your case (number of projects, categories structure, frequency of job submissions, etc.)? 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-20599) Handle several testpoints TAP result file
SCM/JIRA link daemon commented on JENKINS-20599 Handle several testpoints TAP result file Code changed in jenkins User: Bruno P. Kinoshita Path: pom.xml src/main/java/hudson/plugins/testlink/result/AbstractTAPFileNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/AbstractTAPResultSeeker.java src/main/java/hudson/plugins/testlink/result/TAPFileNameMultiTestPointsResultSeeker.java src/main/java/hudson/plugins/testlink/result/TAPFileNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/TAPMultiTestpointsFileNameResultSeeker.java src/main/resources/hudson/plugins/testlink/result/TAPFileNameMultiTestPointsResultSeeker/config.jelly http://jenkins-ci.org/commit/testlink-plugin/e1e3eecde910931b3e8523197874ada6764db7a4 Log: JENKINS-20599 Massaging the code and bumping tap4j dep version 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-21038) Improve security in team-concert plugin
Gabriel Lopez commented on JENKINS-21038 Improve security in team-concert plugin I see. In a way, it makes sense, but it would be nice to have the option. I suppose there are much better solutions though, so I don't consider reading password files from slaves a must. About credentials-plugin, I think it is the one that is filling the functionality gap in jenkins for centralizing password management. Until it, all plugins implemented its own password fields in their own way. Ideally this plugin can fill this gap and allow plugins to collaborate in terms of password management, in a secured way. See http://blog.cloudbees.com/2012/02/open-sourcing-credentials-plugin.html Recently, the Git plugin added support to it: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin Sadly, only a bunch supports it, but I think it will get better. The most common use case is using https://wiki.jenkins-ci.org/display/JENKINS/SSH+Credentials+Plugin That was just an idea though. In our case, either putting the password on jobs (that are shown in the html and are duplicated across jobs) and using password files (that are not that safe and we don't have OS access to the jenkins master [think like we are using it as a service]) is inconvenient. Thanks for the reply. 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Oleg Nenashev assigned JENKINS-21044 to Oleg Nenashev Throttle Concurrent Builds blocking Jenkins queue Change By: Oleg Nenashev (17/Dec/13 5:13 PM) Assignee: abayer 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
Alex Earl commented on JENKINS-17742 Pick Up Committer from Upstream Job Feel free to implement it and issue a pull request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
Jonathan Brecher commented on JENKINS-17742 Pick Up Committer from Upstream Job Sorry, I meant Groovy. I've edited my previous comment. I also have a way of reducing the need for each person to know Groovy: Provide a checkbox that offers this functionality natively. 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-17742) Pick Up Committer from Upstream Job
Jonathan Brecher edited a comment on JENKINS-17742 Pick Up Committer from Upstream Job We have hundreds of developers maintaining their own Jenkins jobs on a central server. We can reasonably expect them to choose whether to hit a checkbox. We cannot expect them to learn Groovy on top of their other responsibilities. How could it not be a good idea for the plugin to handle this natively? If the plugin handles it natively, with a checkbox as suggested by Christian, then admins have a choice of using the native implementation if it works for them. They also still have the option of using Groovy if they love lots of repeated code in each of their Jenkins jobs. Without native support in the plugin, there are no options. 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-17742) Pick Up Committer from Upstream Job
Alex Earl commented on JENKINS-17742 Pick Up Committer from Upstream Job Why would they need Gradle? The script is pure Groovy. There are plenty of ways to reduce the need for each person to know Groovy. You can create template jobs (plugin), when new jobs are created you create them based on a template (if you don't want a 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] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
Alex Earl commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build I'll think about this, but I don't really want to change the behavior as it is now. 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-20690) Subversion changes using Assembla
Cameron Horn commented on JENKINS-20690 Subversion changes using Assembla It seems that we did, although I don't know why. Removing that configuration from all projects fixed things. 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-20690) Subversion changes using Assembla
Cameron Horn resolved JENKINS-20690 as Not A Defect Subversion changes using Assembla Change By: Cameron Horn (17/Dec/13 3:26 PM) Status: Open Resolved Resolution: Not A Defect 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] [mailer] (JENKINS-21045) maven 2/3 projects cannot store emailaddress
Jesse Glick assigned JENKINS-21045 to Jesse Glick maven 2/3 projects cannot store emailaddress Change By: Jesse Glick (17/Dec/13 3:19 PM) Assignee: Jesse Glick 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-17742) Pick Up Committer from Upstream Job
Jonathan Brecher commented on JENKINS-17742 Pick Up Committer from Upstream Job We have hundreds of developers maintaining their own Jenkins jobs on a central server. We can reasonably expect them to choose whether to hit a checkbox. We cannot expect them to learn Gradle on top of their other responsibilities. How could it not be a good idea for the plugin to handle this natively? If the plugin handles it natively, with a checkbox as suggested by Christian, then admins have a choice of using the native implementation if it works for them. They also still have the option of using Gradle if they love lots of repeated code in each of their Jenkins jobs. Without native support in the plugin, there are no options. 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] [mailer] (JENKINS-21045) maven 2/3 projects cannot store emailaddress
Jesse Glick started work on JENKINS-21045 maven 2/3 projects cannot store emailaddress Change By: Jesse Glick (17/Dec/13 3:19 PM) Status: Open In Progress 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Thank you for all your help. I attached a document to show how I am accessing the Jenkins API with .net (C#). It works for some calls but anytime I try to get "job" data, I get a 404 error. I'm not sure I need the call-remote-jenkins-job plugin but I will try anything to make this work. Thanks again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams updated JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Change By: Bill Williams (17/Dec/13 3:13 PM) Attachment: JenkinsApiCallsCsharp.doc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams updated JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Change By: Bill Williams (17/Dec/13 3:11 PM) Attachment: JenkinsApiCallsC#.doc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21047) Update XStream 1.4.4. to 1.4.6
Michael Stengel created JENKINS-21047 Update XStream 1.4.4. to 1.4.6 Issue Type: Improvement Assignee: Unassigned Components: core Created: 17/Dec/13 3:01 PM Description: Update to XStream 1.4.6 needed, because of JENKINS-19031. Users with IBM-JAVA cannot update Jenkins with versions higher 1.503 Project: Jenkins Priority: Major Reporter: Michael Stengel 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] [mailer] (JENKINS-20954) NPE from MailSender.createEmptyMail
Joern Muehlencord commented on JENKINS-20954 NPE from MailSender.createEmptyMail NPE is fixed, not be able to save is still open (even it was the orinal header of the bug) With 1.7 sending emails is still broken but at least you do not receive an ugly error because of the blank email list. 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-19031) com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1
Michael Stengel edited a comment on JENKINS-19031 com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1 The problem seems to be the xstream library 1.4.4. We use IBM JAVA and have the same problem. The bug in XStream is fixed in XStream Version 1.4.6: See ChangeLog •XSTR-739 and XSTR-746: OrderRetainingMap fails if HashMap.putAll(Map) of Java Runtime is not implemented calling put for every element within the map. 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] [mailer] (JENKINS-21045) maven 2/3 projects cannot store emailaddress
Jesse Glick updated JENKINS-21045 maven 2/3 projects cannot store emailaddress Change By: Jesse Glick (17/Dec/13 2:52 PM) Labels: plugin regression 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] [mailer] (JENKINS-20954) NPE from MailSender.createEmptyMail
Joern Muehlencord commented on JENKINS-20954 NPE from MailSender.createEmptyMail done - see https://issues.jenkins-ci.org/browse/JENKINS-21045 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] [cloverphp-plugin] (JENKINS-21046) option to generate clover report regardless of build status
Antoine Musso created JENKINS-21046 option to generate clover report regardless of build status Issue Type: Bug Assignee: sogabe Components: cloverphp-plugin Created: 17/Dec/13 2:45 PM Description: I got a fairly large PHPUnit test suite that takes up to 40 minutes to run. Due to some weird bug in PHP or Xdebug, it ends segfaulting when PHP shutdown. Regardless, the clover.xml is properly generated and could be made a report. Alas, the plugin does not generate the clover report because of the build failure (added URL to console log, copied relevant part below): /tmp/hudson2299744543392632448.sh: line 8: 6928 Segmentation fault nice -n 19 php tests/phpunit/phpunit.php --with-phpunitdir /srv/deployment/integration/phpunit/vendor/phpunit/phpunit --exclude-group Dump,Broken,ParserFuzz,Stub --coverage-clover log/clover.xml --coverage-html /srv/org/wikimedia/integration/cover/mediawiki-core/master/php Build step 'Execute shell' marked build as failure Publishing Clover coverage report... No Clover report will be published due to a Build Failure Finished: FAILURE It would be very nice to have an option detecting whether the clover.xml is non empty and fresh and generate the coverage report regardless of the build status. Environment: Plugin version 0.3.3 Jenkins 1.509.4 (LTS) Project: Jenkins Priority: Major Reporter: Antoine Musso 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] [mailer] (JENKINS-20954) NPE from MailSender.createEmptyMail
Joern Muehlencord edited a comment on JENKINS-20954 NPE from MailSender.createEmptyMail new issue created - see https://issues.jenkins-ci.org/browse/JENKINS-21045 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] [mailer] (JENKINS-20954) NPE from MailSender.createEmptyMail
Greg Huber commented on JENKINS-20954 NPE from MailSender.createEmptyMail Sorry, I am a bit confused, the original issue was that the email recipient would not save, and as a result there was a npe. What has been fixed now on this, the email recipient not saving or the npe? Cheers Greg. 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-20989) PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Jesse Glick commented on JENKINS-20989 PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered Makes sense, file a pull request with a test. 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] [mailer] (JENKINS-21045) maven 2/3 projects cannot store emailaddress
Joern Muehlencord created JENKINS-21045 maven 2/3 projects cannot store emailaddress Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: mailer, maven Created: 17/Dec/13 2:35 PM Description: After upgrade from mailer 1.5 to 1.6/1.7 it is no longer possible to edit email address for notification. Reproduceable by: select project edit configuration add email address edit configuration (again) --> emailaddress is gone See also https://issues.jenkins-ci.org/browse/JENKINS-20954 Environment: SLES 10.4, Tomcat 7.0.42, Jenkins 1.544, mailer 1.7 Project: Jenkins Labels: plugin Priority: Critical Reporter: Joern Muehlencord 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Geoff Cummings created JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue Issue Type: Bug Affects Versions: current Assignee: abayer Components: throttle-concurrents Created: 17/Dec/13 2:34 PM Description: Jenkins had stopped responding to browser requests for Jenkins pages and I think it may be caused by the recent upgrade to Throttle Concurrent Builds 1.8.1 Requests were getting blocked waiting on 0x0004181e4520 "Handling GET /jenkins/ : RequestHandlerThread[#171]" daemon prio=10 tid=0x168ee800 nid=0x193b waiting for monitor entry [0x4335b000] java.lang.Thread.State: BLOCKED (on object monitor) at hudson.model.Queue.getItems(Queue.java:687) - waiting to lock <0x0004181e4520> (a hudson.model.Queue) at hudson.model.Queue$CachedItemList.get(Queue.java:216) at hudson.model.Queue.getApproximateItemsQuickly(Queue.java:717) at hudson.model.View.getApproximateQueueItemsQuickly(View.java:483) at sun.reflect.GeneratedMethodAccessor355.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) This seems to be waiting on Throttle Concurrent Builds code. Further dumps after 10 minutes, 20 minutes and 30 minutes showed this same stack trace. "Thread-126" daemon prio=10 tid=0x2aaae0529800 nid=0x1785 runnable [0x4659] java.lang.Thread.State: RUNNABLE at java.util.WeakHashMap$HashIterator.hasNext(WeakHashMap.java:875) at java.util.AbstractCollection.toArray(AbstractCollection.java:139) at java.util.ArrayList.(ArrayList.java:164) at hudson.plugins.throttleconcurrents.ThrottleJobProperty.getCategoryProjects(ThrottleJobProperty.java:141) - locked <0x00041a79b778> (a java.util.HashMap) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRun(ThrottleQueueTaskDispatcher.java:118) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRun(ThrottleQueueTaskDispatcher.java:90) at hudson.model.Queue.isBuildBlocked(Queue.java:937) at hudson.model.Queue.maintain(Queue.java:1006) - locked <0x0004181e4520> (a hudson.model.Queue) at hudson.model.Queue$1.call(Queue.java:303) at hudson.model.Queue$1.call(Queue.java:300) at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:69) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:724) Locked ownable synchronizers: - None CPU usage was at ~100% for this thread for the 30 minutes that I was watching it before I restarted Jenkins. (6021 = 0x1785) PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 6021 rcbuild_ 35 10 18.0g 6.2g 32m R 99.7 19.7 30:45.97 java I have rolled back to Throttle Concurrent Builds 1.8 for now. Still learning how to investigate thread dumps but please let me know if there is anything I can do to help. Environment: Jenkins 1.544 Project: Jenkins Priority: Critical Reporter: Geoff Cummings 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 m
[JIRA] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly
Jesse Glick assigned JENKINS-15163 to Jesse Glick Mercurial plugin cloning not resolving environment variables correctly Change By: Jesse Glick (17/Dec/13 2:32 PM) Assignee: Kohsuke Kawaguchi Jesse Glick 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-19031) com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1
Michael Stengel commented on JENKINS-19031 com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1 The problem seem to be the xstream library 1.4.4. We use IBM JAVA and have the same problem. The bug in XStream is fixed in XStream Version 1.4.6: See ChangeLog •XSTR-739 and XSTR-746: OrderRetainingMap fails if HashMap.putAll(Map) of Java Runtime is not implemented calling put for every element within the map. 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] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly
Jesse Glick commented on JENKINS-15163 Mercurial plugin cloning not resolving environment variables correctly https://github.com/jenkinsci/mercurial-plugin/pull/37 claims to be “related”; unclear to me if it intends to fix this 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] [mailer] (JENKINS-20954) NPE from MailSender.createEmptyMail
Jesse Glick updated JENKINS-20954 NPE from MailSender.createEmptyMail Change By: Jesse Glick (17/Dec/13 2:27 PM) Summary: Cannot save email recipients NPE from MailSender.createEmptyMail 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] [mailer] (JENKINS-20954) NPE from MailSender.createEmptyMail
Jesse Glick resolved JENKINS-20954 as Fixed NPE from MailSender.createEmptyMail One bug at a time please. Please file a separate bug in the maven-plugin component and link it to this one. Change By: Jesse Glick (17/Dec/13 2:28 PM) Status: Reopened 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] [teamconcert] (JENKINS-21038) Improve security in team-concert plugin
Heather Fraser-Dube edited a comment on JENKINS-21038 Improve security in team-concert plugin Thanks for the report and the suggestions. We had figured that access to the password file would be secured. We chose to have the password file only on the master because it felt like having it on the slaves would require a lot coordination when a password had to be updated. Does your organization make use of the credentials plugin? Are there other plugins that you use that also retrieve the passwords from it? I have raised a work item for this 295009: Improve security in Jenkins Team Concert 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] [teamconcert] (JENKINS-21038) Improve security in team-concert plugin
Heather Fraser-Dube commented on JENKINS-21038 Improve security in team-concert plugin Thanks for the report and the suggestions. We had figured that access to the password file would be secured. I have raised a work item for this 295009: Improve security in Jenkins Team Concert 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] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
rggjan commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build I think this would be impossible by the plugin to determine. In this case, A will keep getting emails, and A has to tell B or C to fix the code. However, I think this would be a good incentive for people to fix their broken builds fast, before other people introduce new bugs on top The problem with the current approach is that people start ignoring jenkins mails if the build is broken for too long even though they didn't do anything wrong. With the suggested approach, only people that really broke jenkins (at least once) will get annoying mails, until they managed to get it green again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-20937) SCM password should not be recorded in build.xml in job's builds storage
Anders Hammar commented on JENKINS-20937 SCM password should not be recorded in build.xml in job's builds storage This issue has been fixed with the merge of pull request #13. 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-timeout] (JENKINS-21043) Notify but Don't Cancel a long running build
Walter Kacynski created JENKINS-21043 Notify but Don't Cancel a long running build Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: build-timeout Created: 17/Dec/13 1:23 PM Description: I would like to send notification that a build has been running for a longer than normal time but I don't want to actually cancel the build. Maybe this plug-in can have this option added. Project: Jenkins Priority: Major Reporter: Walter Kacynski 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-21042) Allow exclusions from SVN polling for certain repository URLs
S Daigle created JENKINS-21042 Allow exclusions from SVN polling for certain repository URLs Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: subversion Created: 17/Dec/13 1:23 PM Description: Many jobs require multiple Subversion repositories. For jobs that poll SVN to start execution, it would be good to allow exemptions for certain repository URLs. For example if I have a "main codebase" URL and a "Tools" URL specified and would only like changes made in the "main codebase" to execute a build, this would be helpful. A simple checkbox to "enable" or "disable" polling. This would stop many jobs from running when they really don't have to and hopefully would also keep these commit operations out of the "SCM files changed" Environment: All Project: Jenkins Priority: Major Reporter: S Daigle 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.