[JIRA] [jenkins-jira-issue-updater] (JENKINS-21514) Add fixed version support to jira issue updater plugin
Hua Zhang assigned JENKINS-21514 to Laszlo Miklosik Add fixed version support to jira issue updater plugin Change By: Hua Zhang (11/Feb/14 8:43 AM) Assignee: LaszloMiklosik 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-21648) subversion no longer working on OSX build slave after update from 1.54 to 2.0
stephenconnolly commented on JENKINS-21648 subversion no longer working on OSX build slave after update from 1.54 to 2.0 If you see at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) in the exception trace, then that indicates that the plugin was unable to determine which of the random credentials to use for your build job. The fix is to select the correct credentials and save the build job. Note that the credentials from the .subversion directory may be being ignored with the new credentials model, so it may be the case that your OS-X slave had the credentials stored locally If, on the other hand, you see at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getNextAuthentication(DefaultSVNAuthenticationManager.java:223) then that is a different problem, i.e. the one David Aldrich is seeing From your stack trace it I see getFirstAuthentication 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-21738) Project-base Matrix Authorization Strategy Option is not exists
Ramkumar Yoganathan updated JENKINS-21738 Project-base Matrix Authorization Strategy Option is not exists Change By: Ramkumar Yoganathan (11/Feb/14 9:30 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21656) Credential issues when using externals after upgrade to subversion plugin 2.0
stephenconnolly commented on JENKINS-21656 Credential issues when using externals after upgrade to subversion plugin 2.0 Hmmm... what that would require is to capture the realm from the primary checkout and then if the realm on the external matches to reuse the credentials from the matching realm... rather complex code path... sadly if the complex code path is not followed then there is a drive-by credential stealing attack from anyone with commit access to any part of the svn repo... and I think with revprop mutation you can even hide your tracks... but I have not checked that part This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Thomas Bosch created JENKINS-21750 Promoted Builds Plugin Issue Type: New Feature Assignee: Justin Ryan Attachments: config-job.xml, config-promotion.xml Components: job-dsl-plugin Created: 11/Feb/14 9:41 AM Description: Include the possibility to generate configs to use the "Promoted Builds Plugin". Add new DSL components and generators for creating XML files in the place where the plugin expects it to be. Project: Jenkins Priority: Major Reporter: Thomas Bosch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21751) Jenkins Release Plugin
Thomas Bosch created JENKINS-21751 Jenkins Release Plugin Issue Type: New Feature Assignee: Justin Ryan Attachments: config.xml Components: job-dsl-plugin Created: 11/Feb/14 9:46 AM Description: Add support to use the "Jenkins Release Plugin". Add DSL components to create the config for it. Project: Jenkins Priority: Major Reporter: Thomas Bosch 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] [utplsql] (JENKINS-21752) Test result graph is not always displayed
kusemuckl created JENKINS-21752 Test result graph is not always displayed Issue Type: Bug Affects Versions: current Assignee: kusemuckl Components: utplsql Created: 11/Feb/14 9:47 AM Description: Looks like the utplsql-plugin has the same bug as the NUnit-plugin (JENKINS-9965) Project: Jenkins Priority: Major Reporter: kusemuckl 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] [maven] (JENKINS-21753) mvn --version does not work with maven 3
Ashley Mercer created JENKINS-21753 mvn --version does not work with maven 3 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 11/Feb/14 10:27 AM Description: Jenkins: 1.544 (installed as RPM) maven-integration-plugin: 2.1 Steps to reproduce: configure a simple maven build (the size of the project doesn't seem to matter, we see this with both single module, and multi-module reactor) set Build - Maven Version to a maven 3 installation set Build Goals and options to "-version" We see the following output (the version information is correctly printed, but jenkins then errors): maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [ashley-test-maven] $ java -Xmx1g -XX:MaxPermSize=256m -cp /var/lib/jenkins_slave/maven31-agent.jar:/var/lib/jenkins_slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/boot/plexus-classworlds-2.5.1.jar:/var/lib/jenkins_slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/conf/logging jenkins.maven3.agent.Maven31Main /var/lib/jenkins_slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1 /var/lib/jenkins_slave/slave.jar /var/lib/jenkins_slave/maven31-interceptor.jar /var/lib/jenkins_slave/maven3-interceptor-commons.jar 35328 ===[JENKINS REMOTING CAPACITY]===channel started log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. Executing Maven: -B -f /var/lib/jenkins_slave/workspace/ashley-test-maven/pom.xml --version Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 16:22:22+0100) Maven home: /var/lib/jenkins_slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1 Java version: 1.6.0_25, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-1.6.0-sun-1.6.0.25.x86_64/jre Default locale: en_GB, platform encoding: ISO-8859-1 OS name: "linux", version: "2.6.18-308.8.2.el5", arch: "amd64", family: "unix" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.cli.MavenExecutionRequestsBuilderException at org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.getMavenExecutionRequest(DefaultMavenExecutionRequestBuilder.java:192) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.getMavenExecutionRequest(Maven31Launcher.java:153) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:130) ... 22 more Caused by:
[JIRA] [maven] (JENKINS-21753) mvn --version does not work with maven 3
Ashley Mercer
updated JENKINS-21753
mvn --version does not work with maven 3
Change By:
Ashley Mercer
(11/Feb/14 10:29 AM)
Description:
Jenkins:1.544(installedasRPM)maven-integration-plugin:2.1
WeareusingthemaveninstallationsdownloadedautomaticallyfromApache.
Stepstoreproduce:-configureasimplemavenbuild(thesizeoftheprojectdoesntseemtomatter,weseethiswithbothsinglemodule,andmulti-modulereactor)-setBuild
-
MavenVersiontoamaven3installation-setBuild
-
Goalsandoptionsto--versionWeseethefollowingoutput(theversioninformationiscorrectlyprinted,butjenkinsthenerrors):{code}maven31-agent.jaralreadyuptodatemaven31-interceptor.jaralreadyuptodatemaven3-interceptor-commons.jaralreadyuptodate[ashley-test-maven]$java-Xmx1g-XX:MaxPermSize=256m-cp/var/lib/jenkins_slave/maven31-agent.jar:/var/lib/jenkins_slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/boot/plexus-classworlds-2.5.1.jar:/var/lib/jenkins_slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/conf/loggingjenkins.maven3.agent.Maven31Main/var/lib/jenkins_slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/var/lib/jenkins_slave/slave.jar/var/lib/jenkins_slave/maven31-interceptor.jar/var/lib/jenkins_slave/maven3-interceptor-commons.jar35328===[JENKINSREMOTINGCAPACITY]===channelstartedlog4j:WARNNoappenderscouldbefoundforlogger(org.apache.commons.beanutils.converters.BooleanConverter).log4j:WARNPleaseinitializethelog4jsystemproperly.ExecutingMaven:-B-f/var/lib/jenkins_slave/workspace/ashley-test-maven/pom.xml--versionApacheMaven3.1.1(0728685237757ffbf44136acec0402957f723d9a;2013-09-1716:22:22+0100)Mavenhome:/var/lib/jenkins_slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1Javaversion:1.6.0_25,vendor:SunMicrosystemsInc.Javahome:/usr/lib/jvm/java-1.6.0-sun-1.6.0.25.x86_64/jreDefaultlocale:en_GB,platformencoding:ISO-8859-1OSname:linux,version:2.6.18-308.8.2.el5,arch:amd64,family:unixjava.lang.reflect.InvocationTargetException atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) atjava.lang.reflect.Method.invoke(Method.java:597) atorg.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) atorg.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) atjenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) atjava.lang.reflect.Method.invoke(Method.java:597) athudson.maven.Maven3Builder.call(Maven3Builder.java:134) athudson.maven.Maven3Builder.call(Maven3Builder.java:69) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:328) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) atjava.util.concurrent.FutureTask.run(FutureTask.java:138) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) atjava.lang.Thread.run(Thread.java:662)Causedby:org.apache.maven.cli.MavenExecutionRequestsBuilderException atorg.apache.maven.cli.DefaultMavenExecutionRequestBuilder.getMavenExecutionRequest(DefaultMavenExecutionRequestBuilder.java:192) atorg.jvnet.hudson.maven3.launcher.Maven31Launcher.getMavenExecutionRequest(Maven31Launcher.java:153) atorg.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:130) ...22moreCausedby:org.apache.maven.cli.DefaultMavenExecutionRequestBuilder$ExitException atorg.apache.maven.cli.DefaultMavenExecutionRequestBuilder.cli(DefaultMavenExecutionRequestBuilder.java:247) atorg.apache.maven.cli.DefaultMavenExecutionRequestBuilder.getMavenExecutionRequest(DefaultMavenExecutionRequestBuilder.java:164)
[JIRA] [subversion] (JENKINS-21712) Jenkins Update breaks Subversion credential configuration
SCM/JIRA link daemon resolved JENKINS-21712 as Fixed Jenkins Update breaks Subversion credential configuration Change By: SCM/JIRA link daemon (11/Feb/14 10:47 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21712) Jenkins Update breaks Subversion credential configuration
SCM/JIRA link daemon commented on JENKINS-21712 Jenkins Update breaks Subversion credential configuration Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/hudson/scm/SubversionSCM.java src/main/resources/hudson/scm/SubversionSCM/AdditionalCredentials/config.jelly src/main/resources/hudson/scm/SubversionSCM/ModuleLocation/config.jelly src/main/resources/hudson/scm/SubversionSCM/config.jelly http://jenkins-ci.org/commit/subversion-plugin/208f10ba16f8317f64060262fa82477db18be299 Log: FIXED JENKINS-21712 The merge lost the switch to c:select/ Refactored the UI to a more modern jelly structure as this made the form validation and updating easier Compare: https://github.com/jenkinsci/subversion-plugin/compare/2107e714114e...208f10ba16f8 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] [maven] (JENKINS-19095) Jenkins suppressing errors in output log
Cristian Vasile Mocanu commented on JENKINS-19095 Jenkins suppressing errors in output log For people having this problem: I had success in creating a freestyle project type. When executing that, I saw what was the actual error - out of PermGen memory. Once I could thus identify the issue, I changed the original project to have more memory and the build didn't break anymore. So it's something in the maven project type that causes the errors not to be displayed in the console. 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-20279) Unable to manage job SVN credentials when deployed along Sonar on Tomcat.
stephenconnolly commented on JENKINS-20279 Unable to manage job SVN credentials when deployed along Sonar on Tomcat. Can you confirm whether this issue is still present with the subversion plugin 2.x versions 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-19243) subversion polling externals runs a build when no changes are made.
stephenconnolly closed JENKINS-19243 as Duplicate subversion polling externals runs a build when no changes are made. Change By: stephenconnolly (11/Feb/14 11:49 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] [subversion] (JENKINS-19175) HTTPS with Client Certificates gives 'handshake_failure' with hidden NPE
stephenconnolly closed JENKINS-19175 as Fixed HTTPS with Client Certificates gives handshake_failure with hidden NPE Change By: stephenconnolly (11/Feb/14 11:48 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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
stephenconnolly closed JENKINS-18312 as Fixed changelog browsing uses the wrong path to Redmine Change By: stephenconnolly (11/Feb/14 11:49 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] [subversion] (JENKINS-17448) System setting http.nonProxyHosts not handled properly
stephenconnolly closed JENKINS-17448 as Not A Defect System setting http.nonProxyHosts not handled properly Change By: stephenconnolly (11/Feb/14 11:52 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] [subversion] (JENKINS-14242) Jenkins 1.467 with Subversion plugin 1.42 won't allow you to update certificate
stephenconnolly resolved JENKINS-14242 as Fixed Jenkins 1.467 with Subversion plugin 1.42 wont allow you to update certificate Should be fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 11:55 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21754) Update https://updates.jenkins-ci.org/download/plugins/warnings/
Pierre-Yves Chibon created JENKINS-21754 Update https://updates.jenkins-ci.org/download/plugins/warnings/ Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 11/Feb/14 12:00 PM Description: While the wiki page 1 says the latest version is 4.39, the download folder 2 stops at 4.28. Could you look at updating the download folder? Thanks 1 https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin 2 https://updates.jenkins-ci.org/download/plugins/warnings/ Project: Jenkins Priority: Major Reporter: Pierre-Yves Chibon 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-7478) Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command
Andrey Rogozhnikov commented on JENKINS-7478 Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command I vote this issue up because chaining commands with '' looks at least strange and results in batch scripts nearly as readable as a base64-encoded RSA public key block. 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] [findbugs] (JENKINS-21155) swarm 1.10 incompatibility with findbugs 4.51
Mark Waite closed JENKINS-21155 as Fixed swarm 1.10 incompatibility with findbugs 4.51 Confirmed fixed with swarm-plugin 1.15 Change By: Mark Waite (11/Feb/14 1:12 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
When performing maven writing to POM file fails
Hi When building a project everything seems to be OK as building a maven project without releasing it does not require files ( at least the POM file ) to be checked out. But when trying to perform a maven release I get the error below: */[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project risk-position-library-testing: Error writing POM: /data/risktech-local/services/jenkins/workspace/risk-mtm-testing/risk/risk-position-library-testing/pom.xml (Permission denied) - [Help 1] /* I am assuming this is due to the fact that the maven release:prepare step fails because the files under the workspace cannot be checked out through perforce plugin. Checking the files udner the workspace we can see that the pom.xml is read-only. *-r--r- 1 riskrun software 1313 Feb 11 10:34 pom.xml* Release gols and options in the Jenkins project: *-Dresume=false -DignoreSnapshots=true release:prepare release:perform* I need to emphsize that the workspace gets downloaded from our SCM and all the files are there but checking them out fails during the maven release build. So could anyone tell me what that problem is? *Additional information:* == *Jenkins version: 1.540 Perforce Plugin vesion: 1.3.27 Jenkins maven relase Plugin version: 0.13.0* == Your help is appreciated. Thanks -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/When-performing-maven-writing-to-POM-file-fails-tp4690172.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] [subversion] (JENKINS-21701) ListSubversionTagsParameterDefinition is not integrated with Credentials
stephenconnolly commented on JENKINS-21701 ListSubversionTagsParameterDefinition is not integrated with Credentials Fixed towards 2.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sectioned-view] (JENKINS-21755) Create HTML anchors for sections
Sebastian Schuberth created JENKINS-21755 Create HTML anchors for sections Issue Type: Improvement Assignee: Timothy Bingaman Components: sectioned-view Created: 11/Feb/14 1:14 PM Description: It would be nice if each section was associated with an HTML anchor so one could create bookmarks that directly jump to a specific section. For example, if a Jenkins URL ending in "/view/Nightly/" would show a view with 10 sections and the last one being called "Tests", a URL like "/view/Nightly/#Tests" would jump directly to that section. Each section header should be a link to itself to one could click on it to easily get the URL including the anchor form the browser's address bar. Project: Jenkins Priority: Minor Reporter: Sebastian Schuberth 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-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
stephenconnolly resolved JENKINS-21617 as Fixed List Subversion Tags job parameter wants svn credentials but there is no way to fill it 2.1 Change By: stephenconnolly (11/Feb/14 1:14 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21701) ListSubversionTagsParameterDefinition is not integrated with Credentials
stephenconnolly resolved JENKINS-21701 as Fixed ListSubversionTagsParameterDefinition is not integrated with Credentials 2.1 Change By: stephenconnolly (11/Feb/14 1:13 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-server] (JENKINS-21163) Git server plugin blocks Jenkins startup
Mark Waite closed JENKINS-21163 as Fixed Git server plugin blocks Jenkins startup This bug is fixed by the release of git-server 1.3. A new release of the git-userContent plugin will be required in order to reconnect it with the base git-server plugin. Change By: Mark Waite (11/Feb/14 1:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-19355) subversion: Cannot use both https and username/password for authentication
stephenconnolly resolved JENKINS-19355 as Fixed subversion: Cannot use both https and username/password for authentication 2.0+ allows you to specify additional credentials. The first credentials will need to be for the first realm to authenticate against. The credentials for the second realm should be provided via the additional credentials section. UI form validation may report an error, but the checkout and polling should work Change By: stephenconnolly (11/Feb/14 1:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-19133) [SVN] Credentials shouldn't be changed by users
stephenconnolly resolved JENKINS-19133 as Fixed [SVN] Credentials shouldnt be changed by users Fixed in 2.0+ with the migration to the credentials plugin based store Change By: stephenconnolly (11/Feb/14 1:17 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17900) subversion credentials are not stored in hudson.scm.SubversionSCM.xml
stephenconnolly resolved JENKINS-17900 as Fixed subversion credentials are not stored in hudson.scm.SubversionSCM.xml 2.0+ Change By: stephenconnolly (11/Feb/14 1:20 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-18250) A user with configure permission for a project cannot add SVN+SSH credentials without having global config permissions
stephenconnolly resolved JENKINS-18250 as Wont Fix A user with configure permission for a project cannot add SVN+SSH credentials without having global config permissions issue is irrelevant on 2.0+ codebase Change By: stephenconnolly (11/Feb/14 1:19 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-usercontent] (JENKINS-21756) git userContent plugin is broken, reports class not found exception in log
Mark Waite created JENKINS-21756 git userContent plugin is broken, reports class not found exception in log Issue Type: Bug Assignee: Unassigned Components: git-usercontent Created: 11/Feb/14 1:20 PM Description: The JENKINS-21163 fix has allowed the Jenkins server to start and run when the git-server plugin is installed. However, attempting to use the git-userContent plugin fails with a 404 error when opening http://localhost:8080/userContent.git . A class not found exception is reported in the Jenkins log, noting that a jar file may need to be rebuilt. Feb 10, 2014 9:04:45 PM hudson.ExtensionFinder$Sezpoz _find WARNING: Failed to load org.jenkinsci.plugins.gitUserContent.GitUserContentRepositorySSHAccess java.lang.InstantiationException: /var/lib/jenkins/plugins/git-userContent/WEB-INF/lib/classes.jar might need to be rebuilt: java.lang.ClassNotFoundException: org.jenkinsci.plugins.gitUserContent.GitUserContentRepositorySSHAccess at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:628) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:617) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:316) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:309) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1187) at hudson.plugins.git.GitSCM.onLoaded(GitSCM.java:1404) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ClassNotFoundException: org.jenkinsci.plugins.gitUserContent.GitUserContentRepositorySSHAccess at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:985) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 26 more Environment: Debian Wheezy Jenkins 1.532.1 git-server plugin 1.3 git-userContent plugin Project: Jenkins Priority: Major Reporter: Mark Waite This message is automatically generated by JIRA. If you think it was sent
[JIRA] [git-usercontent] (JENKINS-21756) git userContent plugin is broken, reports class not found exception in log
Mark Waite updated JENKINS-21756 git userContent plugin is broken, reports class not found exception in log Change By: Mark Waite (11/Feb/14 1:21 PM) Environment: DebianWheezyJenkins1.532.1git-serverplugin1.3git-userContentplugin 1.4-SNAPSHOT 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-14735) Cannot ovveride Subversion credentials to authenticate to server
stephenconnolly resolved JENKINS-14735 as Fixed Cannot ovveride Subversion credentials to authenticate to server Fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 1:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-12472) Older subversion credentials used after given new credentials
stephenconnolly resolved JENKINS-12472 as Fixed Older subversion credentials used after given new credentials Fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 1:22 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-usercontent] (JENKINS-21756) git userContent plugin is broken, reports class not found exception in log
Mark Waite
updated JENKINS-21756
git userContent plugin is broken, reports class not found exception in log
Change By:
Mark Waite
(11/Feb/14 1:23 PM)
Description:
TheJENKINS-21163fixhasallowedtheJenkinsservertostartandrunwhenthegit-serverpluginisinstalled.However,attemptingtousethegit-userContentpluginfailswitha404errorwhenopeninghttp://localhost:8080/userContent.git.AclassnotfoundexceptionisreportedintheJenkinslog,notingthatajarfilemayneedtoberebuilt.
{noformat}Feb10,20149:04:45PMhudson.ExtensionFinder$Sezpoz_findWARNING:Failedtoloadorg.jenkinsci.plugins.gitUserContent.GitUserContentRepositorySSHAccessjava.lang.InstantiationException:/var/lib/jenkins/plugins/git-userContent/WEB-INF/lib/classes.jarmightneedtoberebuilt:java.lang.ClassNotFoundException:org.jenkinsci.plugins.gitUserContent.GitUserContentRepositorySSHAccessatnet.java.sezpoz.IndexItem.element(IndexItem.java:144)athudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:628)athudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:617)athudson.ExtensionFinder._find(ExtensionFinder.java:151)athudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:316)athudson.ExtensionList.load(ExtensionList.java:295)athudson.ExtensionList.ensureLoaded(ExtensionList.java:248)athudson.ExtensionList.iterator(ExtensionList.java:138)athudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:309)athudson.ExtensionList.load(ExtensionList.java:295)athudson.ExtensionList.ensureLoaded(ExtensionList.java:248)athudson.ExtensionList.iterator(ExtensionList.java:138)atjenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1187)athudson.plugins.git.GitSCM.onLoaded(GitSCM.java:1404)atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)atjava.lang.reflect.Method.invoke(Method.java:606)athudson.init.InitializerFinder.invoke(InitializerFinder.java:120)athudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)atjenkins.model.Jenkins$7.runTask(Jenkins.java:899)atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)atjava.lang.Thread.run(Thread.java:744)Causedby:java.lang.ClassNotFoundException:org.jenkinsci.plugins.gitUserContent.GitUserContentRepositorySSHAccessathudson.PluginManager$UberClassLoader.findClass(PluginManager.java:985)atjava.lang.ClassLoader.loadClass(ClassLoader.java:425)atjava.lang.ClassLoader.loadClass(ClassLoader.java:358)atnet.java.sezpoz.IndexItem.element(IndexItem.java:134)...26more{noformat}
Iwasusingasnapshotbuildofthegit-userContentpluginsothatIcouldupdateitsdependenciestomatchthegit-serverplugindependencies.
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-20279) Unable to manage job SVN credentials when deployed along Sonar on Tomcat.
Alan Aguerreberre commented on JENKINS-20279 Unable to manage job SVN credentials when deployed along Sonar on Tomcat. Hello Stephen, Yes, I made an installation with the latest version of the plugin and was able to reproduce it in the said environment. Thanks for your response. Regards. 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-10479) After-the-fact tagging of Subversion repository doesn't use specified credential
stephenconnolly resolved JENKINS-10479 as Fixed After-the-fact tagging of Subversion repository doesnt use specified credential Fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 1:25 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-10866) NullPointerException for SVN authentication using username+password and client certificate
stephenconnolly resolved JENKINS-10866 as Fixed NullPointerException for SVN authentication using username+password and client certificate Should be fixed in 2.0+ The UI validation of the credentials may warn issues. The credentials to select from the drop down should be the first realm that is required to authenticate against. Then in the Additional credentials section provide the second realm credentials and checkout + polling should work correctly Change By: stephenconnolly (11/Feb/14 1:24 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21757) Make use of Maven dependencies inside DC plugin when executing a maven job
Henri Gomez created JENKINS-21757 Make use of Maven dependencies inside DC plugin when executing a maven job Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 11/Feb/14 1:26 PM Description: Dependency Check Plugin run Dependency Check core and scan all workspace contents, including local maven repositories. This raise many false positive about vulnerabilities in artifacts not bundled in product but used in scope test, provided, runtime and even Maven plugins (ie Maven site using vulnerable Struts). Maven support is allready available in Dependency Check core and Jenkins integration in Dependency Check Plugin, this one should be able to use Jenkins/Maven integration fluently Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [dependency-check-jenkins] (JENKINS-21758) Extra extensions should be scanned
Henri Gomez created JENKINS-21758 Extra extensions should be scanned Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 11/Feb/14 1:29 PM Description: Dependency Check support a known set of file extensions to be scanner (zip, jar, war, ear, ...) For internal projects, customs extensions could be used and should be provided to DC via DC Jenkins Plugin. See https://github.com/jeremylong/DependencyCheck/issues/65 Project: Jenkins Priority: Major Reporter: Henri Gomez 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-21759) Central configuration of repository user tear open a serious security leak
Steffen Mork created JENKINS-21759 Central configuration of repository user tear open a serious security leak Issue Type: Bug Assignee: Unassigned Components: subversion Created: 11/Feb/14 1:38 PM Description: Everybody who has job configuration access rights (a so called job configurator) can select any subversion repository user configured centrally in jenkins. In past versions the job configurator must knew the user and password combination of the used subversion repository. Now it is possible that the job configurator can configure a subversion repository without having access rights but only knowing the URL and the user login but not knowing the password. So the job configurator can bypass subversion repository access restrictions to gain access to that repository content. We have about 200 jobs configured and using project specific authorization. Lots of jobs have active NDAs. So this is a serious security issue for us. Project: Jenkins Labels: subversion Priority: Critical Reporter: Steffen Mork 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] [dependency-check-jenkins] (JENKINS-21757) Make use of Maven dependencies inside DC plugin when executing a maven job
Steve Springett assigned JENKINS-21757 to Steve Springett Make use of Maven dependencies inside DC plugin when executing a maven job Change By: Steve Springett (11/Feb/14 1:38 PM) Assignee: SteveSpringett 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] [dependency-check-jenkins] (JENKINS-21758) Extra extensions should be scanned
Steve Springett assigned JENKINS-21758 to Steve Springett Extra extensions should be scanned Change By: Steve Springett (11/Feb/14 1:40 PM) Assignee: SteveSpringett 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-9271) AdjunctManager is not installed for this application upon failed boot
Philip Rosenberg reopened JENKINS-9271 AdjunctManager is not installed for this application upon failed boot This issue came up again. We got it with a clean installation of Jenkins 1.550 on SUSE Linux Enterprise 11 SP3. The only thing we changed is that we added a proxy on the plugins-configuration site. Change By: Philip Rosenberg (11/Feb/14 1:48 PM) Resolution: Fixed Status: Resolved Reopened Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15355) AdjunctManager: exception upon startup
Philip Rosenberg edited a comment on JENKINS-15355 AdjunctManager: exception upon startup We got this issue with a clean installation of Jenkins 1.550 on SUSE Linux Enterprise 11 SP3. The only thing we changed is that we added a proxy on the plugins-configuration site. 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-8654) manage SVN Credential
stephenconnolly resolved JENKINS-8654 as Fixed manage SVN Credential Should be fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 1:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-9252) Jenkins should warn you if it's stored svn credentials fail to authenticate
stephenconnolly resolved JENKINS-9252 as Fixed Jenkins should warn you if its stored svn credentials fail to authenticate Should be fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 1:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-8145) Unable to store/handle new credentials with subversion plugin 1.2x
stephenconnolly resolved JENKINS-8145 as Fixed Unable to store/handle new credentials with subversion plugin 1.2x Should be fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 1:53 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-9657) SVN plugin uses credentials of person who runs slave, not credentials configured on master.
stephenconnolly resolved JENKINS-9657 as Fixed SVN plugin uses credentials of person who runs slave, not credentials configured on master. should be fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 1:51 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-2445) SVN credentials are not read on Reload from disk
stephenconnolly resolved JENKINS-2445 as Fixed SVN credentials are not read on Reload from disk No longer an issue with 2.0+ Change By: stephenconnolly (11/Feb/14 1:54 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-2073) SVN - Change credential does not work in project
stephenconnolly resolved JENKINS-2073 as Fixed SVN - Change credential does not work in project Should be fixed in 2.0+ Change By: stephenconnolly (11/Feb/14 1:54 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-3276) Wrong username used for login to SVN
stephenconnolly resolved JENKINS-3276 as Fixed Wrong username used for login to SVN The change in credentials management in 2.0+ should have fixed this issue Change By: stephenconnolly (11/Feb/14 1:55 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-19133) [SVN] Credentials shouldn't be changed by users
Steffen Breitbach commented on JENKINS-19133 [SVN] Credentials shouldnt be changed by users Very nice, thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachemnt in email-ext plugin
Anand Raja
created JENKINS-21760
Unable to attach pdf as an attachemnt in email-ext plugin
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext
Created:
11/Feb/14 1:56 PM
Description:
Hi,
I have tried various thing to attach pdf as attachment in email-ext but unable to do so..
Tried the below scenarios
in Attachments section
${FILE, path="/path file.pdf"}
Nothing happens.
Tried the same in Default Content section.
Special characters are displayed in the body of the mail.
Project:
Jenkins
Labels:
email-ext
Priority:
Critical
Reporter:
Anand Raja
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] [dependency-check-jenkins] (JENKINS-21758) Extra extensions should be scanned
Henri Gomez commented on JENKINS-21758 Extra extensions should be scanned In PR : https://github.com/jeremylong/DependencyCheck/pull/63 Sadly GitHub merged both PR ;( 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-21761) Not saved new emails
Eduardo Murillo created JENKINS-21761 Not saved new emails Issue Type: Bug Assignee: Unassigned Components: mailer Created: 11/Feb/14 2:34 PM Description: Since I updated to the version 1.549 of Jenkins I cant modify the send of email. I have the plugin Jenkins Mailer Plugin in the last version (1.8). When I write one email and save the config job, this new email is not saved in Jenkins. I attached the trace error when the job compile ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at java.util.StringTokenizer.init(StringTokenizer.java:182) at java.util.StringTokenizer.init(StringTokenizer.java:219) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:326) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:175) at hudson.tasks.MailSender.getMail(MailSender.java:166) at hudson.tasks.MailSender.execute(MailSender.java:100) at hudson.maven.reporters.MavenMailer.end(MavenMailer.java:55) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:760) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) project=hudson.maven.MavenModuleSet@b4aae68[a.juridica - deploy] project.getModules()=[hudson.maven.MavenModule@785b7615[a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos][a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos][relativePath:], hudson.maven.MavenModule@6300a770[a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-common][a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-common][relativePath:asuntos-juridicos-common], hudson.maven.MavenModule@47ae0dd[a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-dto][a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-dto][relativePath:asuntos-juridicos-dto], hudson.maven.MavenModule@57464ad4[a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-logica][a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-logica][relativePath:asuntos-juridicos-logica], hudson.maven.MavenModule@4b3343fa[a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-presentacion][a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-presentacion][relativePath:asuntos-juridicos-presentacion], hudson.maven.MavenModule@25537674[a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-rpc][a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos-rpc][relativePath:asuntos-juridicos-rpc]] project.getRootModule()=hudson.maven.MavenModule@785b7615[a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos][a.juridica - deploy/com.abengoa.simosait.asuntos-juridicos:asuntos-juridicos][relativePath:] FATAL: null java.lang.NullPointerException at java.util.StringTokenizer.init(StringTokenizer.java:182) at java.util.StringTokenizer.init(StringTokenizer.java:219) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:326) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:175) at hudson.tasks.MailSender.getMail(MailSender.java:166) at hudson.tasks.MailSender.execute(MailSender.java:100) at hudson.maven.reporters.MavenMailer.end(MavenMailer.java:55) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:760) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at
[JIRA] [elastic-axis] (JENKINS-21305) elastic axis definition help says separator spaces are used, commas are required
Mark Waite closed JENKINS-21305 as Fixed elastic axis definition help says separator spaces are used, commas are required Rather than wait for the next release to close this issue, I've marked the issue as closed now so that I don't have to see this in my list of open issues. Change By: Mark Waite (11/Feb/14 3:06 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-16627) Fail to parse jmeter report
John Murray commented on JENKINS-16627 Fail to parse jmeter report Reinier Boon or Simon Schlachter, could you please provide a sample file that can be used to reproduce? 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] [dependency-check-jenkins] (JENKINS-21762) OWASP DependencyChecker cve.2.9.h2.db still in use after successful build
Allen Vyvyan created JENKINS-21762 OWASP DependencyChecker cve.2.9.h2.db still in use after successful build Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 11/Feb/14 3:15 PM Description: We received notice of the OWASP Dependency-Check Plugin and it sounded interesting, so we installed it and gave it a try on a model job. In my first attempt at running the plugin, I ran it against an EAR that had no dependencies, just to see what it would do. After completion I updated the configuration to scan a project that actually had dependencies. However, the build could not delete the workspace because one of the files was still in use. 07:49:17 Deleting project workspace... Cannot delete workspace: java.nio.file.FileSystemException: E:\Jenkins\workspace\Build\Model_Build_JEE_developerIntegration\dependency-check-data\cve.2.9.h2.db: The process cannot access the file because it is being used by another process. 07:49:23 07:49:23 ERROR: Cannot delete workspace: java.nio.file.FileSystemException: E:\Jenkins\workspace\Build\Model_Build_JEE_developerIntegration\dependency-check-data\cve.2.9.h2.db: The process cannot access the file because it is being used by another process. 07:49:23 07:49:23 Files match condition: Matched [0] files 07:49:23 Run condition [Files match] preventing perform for step [Publish JUnit test result report] Our server admin took a look at things behind the scenes and has additional debugging information that he will attach shortly. Project: Jenkins Priority: Major Reporter: Allen Vyvyan 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] [dependency-check-jenkins] (JENKINS-21762) OWASP DependencyChecker cve.2.9.h2.db still in use after successful build
Walter Kacynski edited a comment on JENKINS-21762 OWASP DependencyChecker cve.2.9.h2.db still in use after successful build In our Java-002 Slave, the following threads are active: H2 File Lock Watchdog E:/Jenkins/workspace/Build/Model_Build_JEE_developerIntegration/dependency-check-data/cve.2.9.lock.db id=4613 (0x1205) state=TIMED_WAITING cpu=0% at java.lang.Thread.sleep(Native Method) at org.h2.store.FileLock.run(FileLock.java:493) at java.lang.Thread.run(Thread.java:724) H2 TCP Server (tcp://10.7.64.161:57006) id=4615 (0x1207) state=RUNNABLE cpu=0% (running in native) at java.net.DualStackPlainSocketImpl.accept0(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept(DualStackPlainSocketImpl.java:131) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:198) at java.net.ServerSocket.implAccept(ServerSocket.java:530) at java.net.ServerSocket.accept(ServerSocket.java:498) at org.h2.server.TcpServer.listen(TcpServer.java:244) at org.h2.tools.Server.run(Server.java:549) at java.lang.Thread.run(Thread.java:724) This also causes a huge amount of java heap usage in the Slave. It appears that this plug-in causes the logic to run in the slave instead of an external process. 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] [dependency-check-jenkins] (JENKINS-21762) OWASP DependencyChecker cve.2.9.h2.db still in use after successful build
Walter Kacynski updated JENKINS-21762 OWASP DependencyChecker cve.2.9.h2.db still in use after successful build Change By: Walter Kacynski (11/Feb/14 3:21 PM) Attachment: cloudbees-support.zip 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-21763) Subversion doesn't create working links on master machine
Slawomir Skrzyniarz updated JENKINS-21763 Subversion doesnt create working links on master machine Change By: Slawomir Skrzyniarz (11/Feb/14 3:22 PM) Summary: Subversiondoesntcreate working links fromexternals onmastermachine 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-21763) Subversion doesn't create links from externals on master machine
Slawomir Skrzyniarz created JENKINS-21763 Subversion doesnt create links from externals on master machine Issue Type: Bug Assignee: Unassigned Components: subversion Created: 11/Feb/14 3:20 PM Description: Subversion during fresh checkout of code from svn on master machine (the same as Jenkins) doesn't download links properly from main repository and from externals resources. In place of link Subversion create normal file with string: "link /pleace/where/link/indicate" without new line. Could you look on it? Due Date: 04/Feb/14 12:00 AM Environment: Jenkins 1.550/java version 1.6.0_22 with Jenkins Subversion Plug-in 2.0 on RedHat 6.2 x86_64 - svn, version 1.6.11 (r934486) Project: Jenkins Labels: subversion Priority: Critical Reporter: Slawomir Skrzyniarz 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] [dependency-check-jenkins] (JENKINS-21762) OWASP DependencyChecker cve.2.9.h2.db still in use after successful build
Walter Kacynski commented on JENKINS-21762 OWASP DependencyChecker cve.2.9.h2.db still in use after successful build In our Java-002 Slave, the following threads are active: H2 File Lock Watchdog E:/Jenkins/workspace/Build/Model_Build_JEE_developerIntegration/dependency-check-data/cve.2.9.lock.db id=4613 (0x1205) state=TIMED_WAITING cpu=0% at java.lang.Thread.sleep(Native Method) at org.h2.store.FileLock.run(FileLock.java:493) at java.lang.Thread.run(Thread.java:724) H2 TCP Server (tcp://10.7.64.161:57006) id=4615 (0x1207) state=RUNNABLE cpu=0% (running in native) at java.net.DualStackPlainSocketImpl.accept0(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept(DualStackPlainSocketImpl.java:131) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:198) at java.net.ServerSocket.implAccept(ServerSocket.java:530) at java.net.ServerSocket.accept(ServerSocket.java:498) at org.h2.server.TcpServer.listen(TcpServer.java:244) at org.h2.tools.Server.run(Server.java:549) at java.lang.Thread.run(Thread.java:724) This also causes a huge amount of java heap usage in the Slave. It appears that this plug-in causes the logic to run in the slave instead of an external process. 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] [sectioned-view] (JENKINS-21764) Add hability to load checkstyle, ccpcheck and nsiqcolletor trends
euro giciel created JENKINS-21764 Add hability to load checkstyle, ccpcheck and nsiqcolletor trends Issue Type: New Feature Assignee: Timothy Bingaman Components: sectioned-view Created: 11/Feb/14 3:52 PM Description: thak you to add these trends : cppcheck nsiqcollecotr checkstyle Project: Jenkins Priority: Major Reporter: euro giciel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21754) Update https://updates.jenkins-ci.org/download/plugins/warnings/
Ulli Hafner resolved JENKINS-21754 as Not A Defect Update https://updates.jenkins-ci.org/download/plugins/warnings/ Please use our maven repository: http://maven.jenkins-ci.org/content/repositories/releases/org/jvnet/hudson/plugins/warnings/ Change By: Ulli Hafner (11/Feb/14 3:56 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21763) Subversion doesn't create working links on master machine
Slawomir Skrzyniarz updated JENKINS-21763 Subversion doesnt create working links on master machine Change By: Slawomir Skrzyniarz (11/Feb/14 4:02 PM) Due Date: 4 18 /Feb/14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21754) Update https://updates.jenkins-ci.org/download/plugins/warnings/
Pierre-Yves Chibon commented on JENKINS-21754 Update https://updates.jenkins-ci.org/download/plugins/warnings/ Thanks the .hpi file there is indeed up to date, but looking at all the other plugins which I have, none of them seems to be up to date on that maven instance. Is there a reason why some project/plugin choose one over the other? Thanks for your quick feedbac anyway 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-21701) ListSubversionTagsParameterDefinition is not integrated with Credentials
Jesse Glick assigned JENKINS-21701 to stephenconnolly ListSubversionTagsParameterDefinition is not integrated with Credentials Change By: Jesse Glick (11/Feb/14 4:48 PM) Assignee: stephenconnolly 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-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Thomas Keller commented on JENKINS-21745 [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL I think this issue is related to JENKINS-19927: I cloned the git-client repository, went to org.jenkinsci.plugins.gitclient.GitClient and commented out the unused CREDENTIALS_MATCHER member of the interface. After rebuilding via mvn clean install I installed the hpi on Jenkins and now got java.lang.NoClassDefFoundError: com/cloudbees/plugins/credentials/common/StandardCredentials at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:63) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:54) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:66) at hudson.plugins.git.UserRemoteConfig$DescriptorImpl.doCheckUrl(UserRemoteConfig.java:147) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) ... 67 more Caused by: java.lang.ClassNotFoundException: com.cloudbees.plugins.credentials.common.StandardCredentials at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 81 more I'll fumble with my local installation of the credentials plugin now like said in JENKINS-19927 to see if this fixes my 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] [jenkins-multijob-plugin] (JENKINS-21649) High CPU Usage on master while slaves working (multijob)
Ralf Menzi commented on JENKINS-21649 High CPU Usage on master while slaves working (multijob) I have made the same observation using: Jenkins: 1.549 Multijob Plugin: 1.11 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-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Thomas Keller
updated JENKINS-21745
[git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Change By:
Thomas Keller
(11/Feb/14 5:05 PM)
Description:
Iwanttoconfigureabuildjobwithgitconnectivity.AssoonasIenteranythingintotheRepositoryURLfieldandleavethefocus,theabovementionedexceptionpopsup(seefullstacktracebelow).WhatItriedsofar:-switchedbetweenopenjdkandoraclejdk(thestacktraceisfromthelatter)-downgradedtoolderversionsoftheplugin(withnosuccessdownto1.4.5)-checkedthecontentsofthegit-client.hpi/extractedplugin,whichhasthefilethattheclassloadermoansabout(Sidenote:whileIcouldfindGitClient.classinplugins/git-client/WEB-INF/lib/classes.jar,Icouldnotfindorg.kohsuke.stapler.*thereorintheotherjarsoftheplugin,isthispackagedsomewhereelse?)Isthereanyworkaround/anythingIcouldtrytoremedythisproblem?Jenkinswithoutevenbasicgitsupportisamajorblockerforus...Manythanks!Thomas.---Gitversion:1.7.9.5Pluginversion:1.6.2Jenkinsversion:1.549(runningstandaloneinJetty)$uname-aLinuxOdin3.8.0-35-generic#52~precise1-UbuntuSMPThuJan3017:24:40UTC2014x86_64x86_64x86_64GNU/Linux$java-versionjavaversion1.7.0_51Java(TM)SERuntimeEnvironment(build1.7.0_51-b13)JavaHotSpot(TM)64-BitServerVM(build24.51-b03,mixedmode)FullStacktrace:
{code}
javax.servlet.ServletException:java.lang.NoClassDefFoundError:org.jenkinsci.plugins.gitclient.GitClient atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Justin Ryan assigned JENKINS-21750 to Thomas Bosch Promoted Builds Plugin Change By: Justin Ryan (11/Feb/14 5:13 PM) Assignee: JustinRyan ThomasBosch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Justin Ryan commented on JENKINS-21750 Promoted Builds Plugin This'll definitely need some special support for something like this. Since this is a common problem, saving files alongside the config.xml, please take a little extra time to make it a re-usable feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione created JENKINS-21766 Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: jira Created: 11/Feb/14 5:24 PM Description: Need the Jenkins 'Create Issue type' plugin to be more dynamic / configurable to allow for different default jira issue type. Utilizing Jenkins Jira plugin version 1.39 Currently, jenkins project will only create an issue typoe of 'Bug'. We need the default configurable to align with the issue types created in jira for the project. Ideally an Issue Type drop-down box. Also, a nice feature is makeing the new issue 'Summary' be configurable with the same plugin. Due Date: 21/Feb/14 12:00 AM Environment: Linux Project: Jenkins Priority: Major Reporter: chris vecchione This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21754) Update https://updates.jenkins-ci.org/download/plugins/warnings/
Ulli Hafner commented on JENKINS-21754 Update https://updates.jenkins-ci.org/download/plugins/warnings/ As developer you have no choice, the upload is done automatically. Maybe the upload script is broken somehow. Can you please report that problem on the dev mailing list, so that someone can have a look into 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] [subversion] (JENKINS-21701) ListSubversionTagsParameterDefinition is not integrated with Credentials
SCM/JIRA link daemon commented on JENKINS-21701 ListSubversionTagsParameterDefinition is not integrated with Credentials Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/scm/listtagsparameter/ListSubversionTagsParameterDefinition.java http://jenkins-ci.org/commit/subversion-plugin/2aad79bc2e7004107b418e7789c1708b594798df Log: Removing comment which is better filed as JENKINS-21701. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21754) Update https://updates.jenkins-ci.org/download/plugins/warnings/
Pierre-Yves Chibon commented on JENKINS-21754 Update https://updates.jenkins-ci.org/download/plugins/warnings/ I am unfortunately not on the mailing list, would you mind doing 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] [build-failure-analyzer] (JENKINS-21767) Add alert configuration for identified causes
bbonn created JENKINS-21767 Add alert configuration for identified causes Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer Created: 11/Feb/14 6:45 PM Description: Hi, It would be cool if you could configure this plugin to e-mail a group when a certain error line is recognized. We have a recent use case where we want to know whenever a certain failure occurs in our build environment. We have a pretty big Jenkins environment so an automated solution would be great. Let me know if this doesn't make sense. Thanks for the consideration! Environment: Windows Server 2008 Project: Jenkins Priority: Minor Reporter: bbonn 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-21768) @QueryParameter with doFillxyxItems is broken
Hugo Ares
created JENKINS-21768
@QueryParameter with doFillxyxItems is broken
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
11/Feb/14 7:24 PM
Description:
In the gerrit-trigger plugin, we have a DescribableGerritServer. In the form, there is a select that gets populated using the doFillDefaultSlaveIdItems method but it requires the name of server so I used @QueryParameter("name"). I tested this new section against jenkins 1.480.3 since the plugin is compiling against that version and it works fine.
When I tested against the latest lts (1.532.1) the serverName parameter of the doFillDefaultSlaveIdItems is always null. In the _javascript_ console, there is the following error:
"Unable to find nearby name" in hudson-behavior.js.
I isolated that the problem was introduced by this commit(1.526):
commit bbaeade5231ca4116047fbd32b2f909a16a59b8d
Author: Kohsuke Kawaguchi k...@kohsuke.org
Date: Tue Jul 16 12:30:14 2013 -0700
this needs to happen at least after the rowset name/nameRef fixup happens.
Since I don't think any other scripts depend on this one, I'm just giving it a low enough priority.
The code is not in the gerrit-trigger master yet so but let me know if you need it, I could push it to my fork.
Here is a sample of its jelly file:
f:form method="post" action="" class="code-quote">"configSubmit" name="config"
...
f:entry title="${%Name}"
f:textbox name="name" value="${it.name}"/
/f:entry
...
f:section title="${%Replication Events}"
f:optionalBlock name="enableReplication" title="${%Enable Triggering On Replication}" checked="${it.config.replicationConfig.enableReplication}"
...
f:optionalBlock name="enableSlaveSelectionInJobs" title="${%Allow Slave Selection in Job Configurations}" checked="${it.config.replicationConfig.enableSlaveSelectionInJobs}"
f:entry title="${%Choose a default slave}" field="defaultSlaveId"
f:select/
/f:entry
/f:optionalBlock
/f:optionalBlock
/f:section
/form
Here the method defined in the Descriptor:
public ListBoxModel doFillDefaultSlaveIdItems(@QueryParameter("name") final String serverName) {
ListBoxModel items = new ListBoxModel();
...
}
Project:
Jenkins
Labels:
regression
Priority:
Major
Reporter:
Hugo Ares
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] [utplsql] (JENKINS-21752) Test result graph is not always displayed
kusemuckl started work on JENKINS-21752 Test result graph is not always displayed Change By: kusemuckl (11/Feb/14 7:39 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Andrew Kujtan created JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-core Created: 11/Feb/14 7:49 PM Description: The latest update of the static analysis plugins seems to expect more plugins than I have installed. I only have findbugs,compiler warnings and task scanner insalled along with thier deps, however when viewing any Job page now I get the following exception appended to the page after each scanners graph. Don't know which plugin is at fault here. I tried to disable the graphs on the page by selecting "No trend graph" to see if the code is there but it seems none of the graph configuration options work either? Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/eng/AppData/Local/Temp/jetty-0.0.0.0-80-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.550.jar!/hudson/model/AbstractProject/main.jelly:79:66: st:include hudson/plugins/checkstyle/CheckStyleProjectAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [copy-to-slave] (JENKINS-21770) Copy to slave injects erroneous drive letter (e.g. E:) to full cygwin workspace path /e/.hudson/jobs/job1/workspace
Gemini A created JENKINS-21770 Copy to slave injects erroneous drive letter (e.g. E:) to full cygwin workspace path /e/.hudson/jobs/job1/workspace Issue Type: Bug Affects Versions: current Assignee: Vivekanand SV Components: copy-to-slave Created: 11/Feb/14 7:57 PM Description: Please note the windows drive letter format "E:" injected in the full workspace path (cygwin format): copy-to-slave Copying '*.dll', from 'file:/E:/e/.hudson/workspace/MSBuild_On_Windows/' on 'hudson.slaves.DumbSlave@506fa283' to 'file:/var/lib/jenkins/jobs/MSBuild_On_Windows/workspace/' on the master. Environment: Linux master windows slave connected via cygwin/ssh Project: Jenkins Priority: Major Reporter: Gemini A 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-19622) PeriodicWork can block timer thread; use ScheduledExecutorService instead
Jesse Glick assigned JENKINS-19622 to recampbell PeriodicWork can block timer thread; use ScheduledExecutorService instead Change By: Jesse Glick (11/Feb/14 7:59 PM) Assignee: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-21771) Apparent increase in thread usage for slave nodes
Greg horvath created JENKINS-21771 Apparent increase in thread usage for slave nodes Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 11/Feb/14 8:02 PM Description: After upgrading to Jenkins v1.549, ssh-slaves v1.6, git plugin v2.0.1, git-client plugin v1.6.2, we began observing many errors and job failures when running builds on our slave nodes. The errors were typically of the form: In general, we saw these errors mainly during two stages of the build process: during SCM step (git checkout), and during transfer of a file specified as a job parameter to the slave node. Some examples of these errors are below; however, it is worth noting that we did observe errors at other phases of the build as well (i.e. was not limited to these two phases). These errors were not dependably reproducible, and were nearly impossible to duplicate in isolation (i.e. could not reproduce when just running jobs on a single slave node). After some time debugging and ruling out some things, we determined that perhaps the user nproc limit (ulimit -u) might be too low, based on the errors that w were seeing and what we were able to rule out after debugging. We increased this limit on our slave nodes and...things went back to normal. None of our build and test jobs changed across the update, meaning that any changes we observed were introduced as a result of the upgrade. My question is then: what has changed recently with slave management that has increased the number of per node threads required? We don't yet have solid watermark data on how high it was actually going, but it was high enough to hit the ceiling for system default (1024). Environment: CentOS 6 Project: Jenkins Labels: slave jenkins performance Priority: Major Reporter: Greg horvath This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-21771) Apparent increase in thread usage for slave nodes
Greg horvath
updated JENKINS-21771
Apparent increase in thread usage for slave nodes
Change By:
Greg horvath
(11/Feb/14 8:07 PM)
Description:
AfterupgradingtoJenkinsv1.549,ssh-slavesv1.6,gitpluginv2.0.1,git-clientpluginv1.6.2,webeganobservingmanyerrorsandjobfailureswhenrunningbuildsonourslavenodes.Theerrorsweretypicallyoftheform:{code}
Causedby:java.lang.OutOfMemoryError:unabletocreatenewnativethread
{code}Ingeneral,wesawtheseerrorsmainlyduringtwostagesofthebuildprocess:duringSCMstep(gitcheckout),andduringtransferofafilespecifiedasajobparametertotheslavenode.Someexamplesoftheseerrorsarebelow;however,itisworthnotingthatwedidobserveerrorsatotherphasesofthebuildaswell(i.e.wasnotlimitedtothesetwophases).
{code}00:00:45.338ERROR:Workspacehasa.gitrepository,butitappearstobecorrupt.00:00:45.972FATAL:java.io.IOException:Remotecallonbob0024failed00:00:45.972hudson.remoting.RemotingSystemException:java.io.IOException:Remotecallonbob0024failed00:00:45.973 athudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:183)00:00:45.973 at$Proxy65.hasGitRepo(UnknownSource)00:00:45.973 atorg.jenkinsci.plugins.gitclient.RemoteGitImpl.hasGitRepo(RemoteGitImpl.java:250)00:00:45.973 athudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:824)00:00:45.973 athudson.plugins.git.GitSCM.checkout(GitSCM.java:872)00:00:45.973 atorg.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118)00:00:45.973 athudson.model.AbstractProject.checkout(AbstractProject.java:1411)00:00:45.973 athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651)00:00:45.973 atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)00:00:45.973 athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560)00:00:45.973 athudson.model.Run.execute(Run.java:1670)00:00:45.973 athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)00:00:45.973 athudson.model.ResourceController.execute(ResourceController.java:88)00:00:45.973 athudson.model.Executor.run(Executor.java:231)00:00:45.973Causedby:java.io.IOException:Remotecallonbob0024failed00:00:45.973 athudson.remoting.Channel.call(Channel.java:731)00:00:45.973 athudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167)00:00:45.973 ...13more00:00:45.973Causedby:java.lang.OutOfMemoryError:unabletocreatenewnativethread00:00:45.973 atjava.lang.Thread.start0(NativeMethod)00:00:45.973 atjava.lang.Thread.start(Thread.java:597)00:00:45.973 athudson.remoting.AtmostOneThreadExecutor.execute(AtmostOneThreadExecutor.java:88)00:00:45.973 atjava.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:78)00:00:45.973 athudson.remoting.JarCacheSupport.resolve(JarCacheSupport.java:59)00:00:45.973 athudson.remoting.ResourceImageBoth.initiateJarRetrieval(ResourceImageBoth.java:40)00:00:45.973 athudson.remoting.ResourceImageBoth.resolve(ResourceImageBoth.java:22)00:00:45.973 athudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:233)00:00:45.973 atjava.lang.ClassLoader.loadClass(ClassLoader.java:307)00:00:45.973 atjava.lang.ClassLoader.loadClass(ClassLoader.java:248)00:00:45.973 athudson.util.StreamTaskListener._error(StreamTaskListener.java:132)00:00:45.973 athudson.util.StreamTaskListener.error(StreamTaskListener.java:141)00:00:45.973 atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.hasGitRepo(CliGitAPIImpl.java:126)00:00:45.973 athudson.plugins.git.GitAPI.hasGitRepo(GitAPI.java:186)00:00:45.973 atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)00:00:45.973 atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)00:00:45.973 atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)00:00:45.973 atjava.lang.reflect.Method.invoke(Method.java:597)00:00:45.973 athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)00:00:45.973 athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)00:00:45.973 athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)00:00:45.973 athudson.remoting.UserRequest.perform(UserRequest.java:118)00:00:45.973
[JIRA] [cli] (JENKINS-21772) Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
Daniel Beck
updated JENKINS-21772
Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
Change By:
Daniel Beck
(11/Feb/14 8:43 PM)
Description:
Stepstoreproduce:1.
`
{{
java-jarjenkins.war
`
}}
withnoexplicitlydefined
`
{{
JENKINS_HOME
`
}}
hasthedefault
`
{{
~/.jenkins
`
}}
(unless
`
{{
~/.hudson
`
}}
exists)2.Run
`
{{
java-jarjenkins-cli.jar…login
`
}}
,creating
`
{{
~/.hudson/cli-credentials
`
}}
ontheserver3.RestartJenkins,anditllinitwithanemptyhome,asnow
`
{{
~/.hudson
`
}}
existsandispreferredto
`
{{
~/.jenkins
`
}}
!
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] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione updated JENKINS-21766 Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug Change By: chris vecchione (11/Feb/14 8:55 PM) Description: NeedtheJenkinsCreateIssuetypeplugintobemoredynamic/configurabletoallowfordifferentdefaultjiraissuetype.UtilizingJenkinsJirapluginversion1.39Currently,jenkinsprojectwillonlycreateanissue typoe type ofBug.Weneedthedefaultconfigurabletoalignwiththeissuetypescreatedinjirafortheproject.IdeallyanIssueTypedrop-downbox. Also,anicefeatureismakeingthenewissueSummarybeconfigurablewiththesameplugin. 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] [utplsql] (JENKINS-21752) Test result graph is not always displayed
kusemuckl stopped work on JENKINS-21752 Test result graph is not always displayed Change By: kusemuckl (11/Feb/14 8:42 PM) Status: InProgress 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] [cli] (JENKINS-21772) Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
Daniel Beck created JENKINS-21772 Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME Issue Type: Bug Assignee: Unassigned Components: cli, core Created: 11/Feb/14 8:30 PM Description: Steps to reproduce: 1. `java -jar jenkins.war` with no explicitly defined `JENKINS_HOME` has the default `/.jenkins` (unless `/.hudson` exists) 2. Run `java -jar jenkins-cli.jar … login`, creating `~/.hudson/cli-credentials` on the server 3. Restart Jenkins, and it'll init with an empty home, as now `/.hudson` exists and is preferred to `/.jenkins`! Environment: 1.552-SNAPSHOT Project: Jenkins Priority: Major Reporter: Daniel Beck 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-21772) Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
Daniel Beck
updated JENKINS-21772
Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
Change By:
Daniel Beck
(11/Feb/14 8:45 PM)
Description:
Stepstoreproduce:1.{{java-jarjenkins.war}}withnoexplicitlydefined{{JENKINS_HOME}}hasthedefault{{
~
$HOME
/.jenkins}}(unless{{
~
$HOME
/.hudson}}exists)2.Run{{java-jarjenkins-cli.jar…login}},creating{{
~
$HOME
/.hudson/cli-credentials}}ontheserver3.RestartJenkins,anditllinitwithanemptyhome,asnow{{
~
$HOME
/.hudson}}existsandispreferredto{{
~
$HOME
/.jenkins}}!
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] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione
commented on JENKINS-21766
Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug
To be more exact we would like the "issue.setType("1") call be configurable like the other fields: Project Key | description | summary | assignee within the following code:
https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraSession.java
public RemoteIssue createIssue(String projectKey, String description, String assignee, RemoteComponent[] components, String summary) throws RemoteException {
RemoteIssue issue = new RemoteIssue();
issue.setProject(projectKey.toUpperCase());
issue.setDescription(description);
issue.setSummary(summary);
issue.setAssignee(assignee);
issue.setType("1");
issue.setComponents(components);
RemoteIssue createdIssue;
createdIssue = service.createIssue(token, issue);
return createdIssue;
}
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-21561) GIT Plugin 2.0.1 doesn't work with Jenkins Multiple SCM .3
Paul Bakker commented on JENKINS-21561 GIT Plugin 2.0.1 doesnt work with Jenkins Multiple SCM .3 Seeing the same thing on Windows, running in Google Chrome. Seeing some _javascript_ exceptions in the log when I try to add a Git SCM. Running Jenkins 1.550, GitHub plugin 1.8, Jenkins Multiple SCMs plugin 0.3 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-21773) Up link from an axis of a matrix job shows Error 404 Not Found
Jacob Keller created JENKINS-21773 Up link from an axis of a matrix job shows Error 404 Not Found Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, matrix Created: 11/Feb/14 9:36 PM Description: When clicking the "Up" link from a child (build axis) of a matrix job, the link leads to an Error 404 Not Found. Instead of loading the parent job it tries to load just the "/job" without the job name. Environment: Fedora 19 package. Matrix build configuration. Project: Jenkins Priority: Major Reporter: Jacob Keller 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-environment] (JENKINS-20132) ERROR: [JENKINS-18403] JDK 5 not supported to run Maven; ERROR: Could not find local repository for 2.2.1
chris vecchione resolved JENKINS-20132 as Not A Defect ERROR: [JENKINS-18403] JDK 5 not supported to run Maven; ERROR: Could not find local repository for 2.2.1 Yorxdan wsa correct = not a jenkins build plugin issue. Pelase close Change By: chris vecchione (11/Feb/14 9:53 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21774) Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit
Anil Chintapatla created JENKINS-21774 Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 11/Feb/14 9:58 PM Description: We noticed that in some cases, Jenkins is reporting wrong set of files in a commit - usually a very long list with hundreds of files in the repo. This has happened in a small percentage of the commits. Any pointers would be appreciated. thanks/Anil Environment: Jenkins - 1.509.4 Jenkins Git Plugin - 2.0.1 Jenkins GIT client plugin - 1.6.1 Project: Jenkins Labels: plugin Priority: Major Reporter: Anil Chintapatla 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-21581) NPE from sidepanel.jelly on changing to a different display page after upgrade to 1.549
wbauer commented on JENKINS-21581 NPE from sidepanel.jelly on changing to a different display page after upgrade to 1.549 I had the same issue with three views but found a fix. check the view config by calling it and adding /configuration.xml in the URL, this will show you the config spec. My non-working views had those two set: filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue Once I edited the stored view configs in the JENKINS_HOME/config.xml and reloaded the config from disk, the views worked! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-21775) Parameter Configuration Slicing exception
M W created JENKINS-21775 Parameter Configuration Slicing exception Issue Type: Bug Assignee: mdonohue Components: configurationslicing Created: 11/Feb/14 10:18 PM Description: I get the following exception whenever I try to use the configuration slicer to edit job parameters: 2014-02-11_21:05:50.75242 java.lang.reflect.InvocationTargetException 2014-02-11_21:05:50.75243 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2014-02-11_21:05:50.75246 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 2014-02-11_21:05:50.75247 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2014-02-11_21:05:50.75247 at java.lang.reflect.Method.invoke(Method.java:616) 2014-02-11_21:05:50.75248 at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297) 2014-02-11_21:05:50.75248 at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) 2014-02-11_21:05:50.75249 at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:95) 2014-02-11_21:05:50.75249 at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) 2014-02-11_21:05:50.75250 at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 2014-02-11_21:05:50.75250 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) 2014-02-11_21:05:50.75250 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) 2014-02-11_21:05:50.75251 at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) 2014-02-11_21:05:50.75252 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) 2014-02-11_21:05:50.75253 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) 2014-02-11_21:05:50.75253 at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) 2014-02-11_21:05:50.75254 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) 2014-02-11_21:05:50.75254 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) 2014-02-11_21:05:50.75255 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:587) 2014-02-11_21:05:50.75255 at org.kohsuke.stapler.Stapler.service(Stapler.java:218) 2014-02-11_21:05:50.75256 at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) 2014-02-11_21:05:50.75256 at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) 2014-02-11_21:05:50.75256 at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) 2014-02-11_21:05:50.75257 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) 2014-02-11_21:05:50.75257 at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) 2014-02-11_21:05:50.75258 at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) 2014-02-11_21:05:50.75258 at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) 2014-02-11_21:05:50.75259 at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) 2014-02-11_21:05:50.75259 at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) 2014-02-11_21:05:50.75263 at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 2014-02-11_21:05:50.75265 at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) 2014-02-11_21:05:50.75267 at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 2014-02-11_21:05:50.75269 at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) 2014-02-11_21:05:50.75271 at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) 2014-02-11_21:05:50.75273 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 2014-02-11_21:05:50.75275 at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 2014-02-11_21:05:50.75277 at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) 2014-02-11_21:05:50.75279 at
[JIRA] [jira] (JENKINS-21776) Jenkins jira comment text typo
chris vecchione created JENKINS-21776 Jenkins jira comment text typo Issue Type: Bug Assignee: Unassigned Attachments: CommentIssue_typo_Feb2014.png Components: jira Created: 11/Feb/14 10:30 PM Description: Jenkins jira issue update plugin has a text error in spelling when adding a comment to an existing issue: typo on the word "failing" (should not be "falling") "Job is not falling but the issue is still open." The correct English should be: "Job is not failing but the issue is still open." Due Date: 14/Feb/14 12:00 AM Project: Jenkins Priority: Major Reporter: chris vecchione 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.
