[JIRA] (JENKINS-13777) Minor spelling errors.
Mads Nielsen created JENKINS-13777: -- Summary: Minor spelling errors. Key: JENKINS-13777 URL: https://issues.jenkins-ci.org/browse/JENKINS-13777 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Windows, Unix Reporter: Mads Nielsen Assignee: Mads Nielsen Priority: Trivial There are a few spelling errors in the plugin. These include that 'atleast' must be in two words. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13778) Icon file with low resolution - needs to be replaced
Mads Nielsen created JENKINS-13778: -- Summary: Icon file with low resolution - needs to be replaced Key: JENKINS-13778 URL: https://issues.jenkins-ci.org/browse/JENKINS-13778 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Reporter: Mads Nielsen Assignee: Mads Nielsen Priority: Trivial The current icon has too low resolution, add a better icon image. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13611) Misleading error leads to slave disconnecting from master
[ https://issues.jenkins-ci.org/browse/JENKINS-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13611 started by Mads Nielsen. Misleading error leads to slave disconnecting from master - Key: JENKINS-13611 URL: https://issues.jenkins-ci.org/browse/JENKINS-13611 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Jenkins 1.441, Windows 7, QAC-7.2F Reporter: Julian Requejo Assignee: Mads Nielsen I'm having some issues running the PQRA Plugin. The [documentation|https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin] is a bit strange. To start with, the screenshot shows a report type quality, even though it says that currently only compliance is available. Then it also says that a tool qaw must be installed, which I don't have anywhere in my installation files. In any case, here is the problem: the plugin seems to not find this qaw tool, and it produces an error that disconnects my slave agent from the master. Started by user X X, xx.xx...@xxx.xx Building remotely on Legoland Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build This job will try to create a report with the following selected parameters: QAR selected project file:Sources//QAC.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources//QAC.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\x\ QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:772) at hudson.FilePath.act(FilePath.java:765) at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:203) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:273) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1139) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) Notifying upstream projects of job completion Finished: FAILURE After this, my slave gets disconnected from the master. So my questions: - Where do I find this qaw tool? It is not installed with QAC-7.2F - Why does the absence of such tool end up in such a brutal way? Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact
[JIRA] (JENKINS-13631) Can't manually promote build with approval parameter
[ https://issues.jenkins-ci.org/browse/JENKINS-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Lehmann updated JENKINS-13631: - Attachment: fix-missing-slash-in-job-name.user.js Updated Patch: fix all forms on the current page Can't manually promote build with approval parameter Key: JENKINS-13631 URL: https://issues.jenkins-ci.org/browse/JENKINS-13631 Project: Jenkins Issue Type: Bug Components: promoted-builds Affects Versions: current Environment: debian 5 Oracle JDK 1.6.0_12 Jenkins 1.461 Reporter: Aurélien Pelletier Labels: plugin Attachments: fix-missing-slash-in-job-name.user.js, fix-missing-slash-in-job-name.user.js Promoted build plugin version 2.5, it works with version 2.4 I have a job configured with a manually approved + approval parameter promotion. When I try to promoted the build using the Approve button to pass the parameters I get an error 500 with this stack trace: java.lang.IllegalArgumentException: THE_NAME_OF_THE_JENKINS_JOB at hudson.maven.ModuleName.fromString(ModuleName.java:97) at hudson.maven.MavenModuleSet.getItem(MavenModuleSet.java:354) at hudson.maven.MavenModuleSet.getItem(MavenModuleSet.java:117) at jenkins.model.Jenkins.getItem(Jenkins.java:2159) at jenkins.model.Jenkins.getItem(Jenkins.java:2180) at hudson.plugins.promoted_builds.conditions.ManualCondition.doApprove(ManualCondition.java:148) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13631) Can't manually promote build with approval parameter
[ https://issues.jenkins-ci.org/browse/JENKINS-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162785#comment-162785 ] Thomas Lehmann commented on JENKINS-13631: -- Works in Firefox 12 too: just install and activate Greasemonkey and klick the attached Script link and answer Yes on the install dialog. (Deactivate Greasemonkey to open the script wihtout installing it to what it does :) Can't manually promote build with approval parameter Key: JENKINS-13631 URL: https://issues.jenkins-ci.org/browse/JENKINS-13631 Project: Jenkins Issue Type: Bug Components: promoted-builds Affects Versions: current Environment: debian 5 Oracle JDK 1.6.0_12 Jenkins 1.461 Reporter: Aurélien Pelletier Labels: plugin Attachments: fix-missing-slash-in-job-name.user.js, fix-missing-slash-in-job-name.user.js Promoted build plugin version 2.5, it works with version 2.4 I have a job configured with a manually approved + approval parameter promotion. When I try to promoted the build using the Approve button to pass the parameters I get an error 500 with this stack trace: java.lang.IllegalArgumentException: THE_NAME_OF_THE_JENKINS_JOB at hudson.maven.ModuleName.fromString(ModuleName.java:97) at hudson.maven.MavenModuleSet.getItem(MavenModuleSet.java:354) at hudson.maven.MavenModuleSet.getItem(MavenModuleSet.java:117) at jenkins.model.Jenkins.getItem(Jenkins.java:2159) at jenkins.model.Jenkins.getItem(Jenkins.java:2180) at hudson.plugins.promoted_builds.conditions.ManualCondition.doApprove(ManualCondition.java:148) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13779) Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM)
Stanislav Jursky created JENKINS-13779: -- Summary: Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM) Key: JENKINS-13779 URL: https://issues.jenkins-ci.org/browse/JENKINS-13779 Project: Jenkins Issue Type: Bug Components: git, multiple-scms Affects Versions: current Environment: Jenkins ver. 1.464 Jenkins GIT plugin 1.1.18 Jenkins Multiple SCMs plugin 0.2 Reporter: Stanislav Jursky Assignee: Nicolas De Loof Priority: Blocker when using multiple SCM plugin together with Git Publisher the git publisher shows and ERROR message: (can we use for Target remote name the name specified in SCM? Status Code: 500 Exception: Stacktrace: java.lang.ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM at hudson.plugins.git.GitPublisher$DescriptorImpl.doCheckRemote(GitPublisher.java:424) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) 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
[JIRA] (JENKINS-13779) Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM)
[
https://issues.jenkins-ci.org/browse/JENKINS-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanislav Jursky updated JENKINS-13779:
---
Environment:
Jenkins ver. 1.464
Jenkins GIT plugin 1.1.15 - 1.1.18
Jenkins Multiple SCMs plugin 0.2
was:
Jenkins ver. 1.464
Jenkins GIT plugin 1.1.18
Jenkins Multiple SCMs plugin 0.2
Priority: Major (was: Blocker)
Description:
when using multiple SCM plugin together with Git Publisher the git publisher
shows and ERROR message:
(can we use for Target remote name the name specified in SCM?
{quote}
Status Code: 500
Exception:
Stacktrace:
java.lang.ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM
cannot be cast to hudson.plugins.git.GitSCM
at
hudson.plugins.git.GitPublisher$DescriptorImpl.doCheckRemote(GitPublisher.java:424)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
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
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
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:173)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63)
at
[JIRA] (JENKINS-13435) Auto Install jdk from oracle downloads html instead of bin
[
https://issues.jenkins-ci.org/browse/JENKINS-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162788#comment-162788
]
Andreas Schilling commented on JENKINS-13435:
-
Same problem here, still not fixed in 1.464
Is more action needed than just upgrading to 1.464? Refreshing credentials for
Oracle Account or whatever?
This is becoming a serious problem for us.
Auto Install jdk from oracle downloads html instead of bin
--
Key: JENKINS-13435
URL: https://issues.jenkins-ci.org/browse/JENKINS-13435
Project: Jenkins
Issue Type: Bug
Components: core
Reporter: Jenni Syed
On version 1.455 (saw on 1.459 as well), choosing to auto-install the jdk
from oracle results in an html page being downloaded and the message below.
When I look at the jdk.sh, it's the html page from oracle complaining about
not accepting the license terms. Also see:
https://groups.google.com/group/jenkinsci-users/browse_thread/thread/1d510fae9816f086
{quote}
Installing JDK jdk-1.5.0_22-oth-JPR
Downloading JDK from
http://download.oracle.com/otn/java/jdk/1.5.0_22/jdk-1_5_0_22-linux-amd64.bin
Downloading 5307bytes
Installing /home/exodus/jenkins/tools/jdk1.5_22/jdk.sh
[jdk1.5_22] $ /home/exodus/jenkins/tools/jdk1.5_22/jdk.sh -noregister
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 1: html: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 2: head: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 3: title: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 4: META: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 5: link: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 6: link: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 7:
: command not found
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 8: body: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 9: div: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 10: table: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 11: tr: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 12: syntax error near
unexpected token `'
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 12: ` td rowspan=2
valign=middle nowrapa href=http://www.oracle.com;img
src=/errors/us/assets/oralogo-small.gif width=154 height=19 hspace=10
vspace=25 border=0 /a/td
'
[EnvInject] - [ERROR] - SEVERE ERROR occurs: hudson.AbortException: Failed to
install JDK. Exit code=2
Finished: FAILURE
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13264) fail checkout 2 modules with different path
[ https://issues.jenkins-ci.org/browse/JENKINS-13264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162789#comment-162789 ] Michael Clarke commented on JENKINS-13264: -- James: could you give some details as to what environment you're running in - is it Windows? fail checkout 2 modules with different path --- Key: JENKINS-13264 URL: https://issues.jenkins-ci.org/browse/JENKINS-13264 Project: Jenkins Issue Type: Bug Components: cvs Environment: linux Reporter: Eric Co Assignee: Michael Clarke Fix For: current I create two cvs modules with the path lib/flac-1.2.1 drv/linux/fuse when it check out, got the error: cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib/flac-1.2.1 lib/flac-1.2.1 cvs [checkout aborted]: could not change directory to requested checkout directory `lib': No such file or directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13780) Rake module uses master RVM path for all nodes
Matt Massicotte created JENKINS-13780: - Summary: Rake module uses master RVM path for all nodes Key: JENKINS-13780 URL: https://issues.jenkins-ci.org/browse/JENKINS-13780 Project: Jenkins Issue Type: Bug Components: rake Affects Versions: current Environment: Ubuntu, Mac OS X Reporter: Matt Massicotte Assignee: david_calavera I'm currently trying to use the rake plugin with Mac OS X and Linux. I have RVM installed on both machines, and need to use it to run rake successfully, as the system rake will not work on Mac OS X. It seems that the rake plugin chooses an RVM path from the master node, and then attempts to use it for all other nodes. This results in a valid path for only the master. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13771) Jenkins not being triggered on a change to an external with new 1.4 SVN plugin.
[ https://issues.jenkins-ci.org/browse/JENKINS-13771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162791#comment-162791 ] Martin Petzsch commented on JENKINS-13771: -- I get the same behaviour. Having reverted the plugin back to 1.34 it appears ok (running 1.464) Jenkins not being triggered on a change to an external with new 1.4 SVN plugin. --- Key: JENKINS-13771 URL: https://issues.jenkins-ci.org/browse/JENKINS-13771 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows Server 2008, 32 bit. Reporter: Jay Beeckman Priority: Blocker Previously, external commits would trigger a build. This is no longer working after the 1.4 update to the Subversion Plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Ohlemacher resolved JENKINS-13745. --- Fix Version/s: current Resolution: Fixed instantiate ValgrindPublisher via databound constructor and not via newInstance method from ValgrindPublisherDescriptor Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception Key: JENKINS-13745 URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 Project: Jenkins Issue Type: Bug Components: plugin Affects Versions: current Environment: Ubuntu 12.04 Jenkins 1.463 Reporter: Georg Hofmann Assignee: Johannes Ohlemacher Labels: exception, plugin Fix For: current Attachments: hudson_valgrind_plugin_excpetion.txt I have tested the Valgrind plugin, but I cannot configure it. The build configuration part is working find, but when I try to configure the publish valgrind results part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8617) cannot customize security group to launch slaves into
[ https://issues.jenkins-ci.org/browse/JENKINS-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162793#comment-162793 ] Yuu Yamashita commented on JENKINS-8617: Thanks for comment. umm... I perfer EC2 instance tag to count matching instances. EC2's DescribeInstances API has capability to find instances with specified tags. Now I'm planning to write new patch to apply instance tags to provisioned instances and then count them later. cannot customize security group to launch slaves into - Key: JENKINS-8617 URL: https://issues.jenkins-ci.org/browse/JENKINS-8617 Project: Jenkins Issue Type: Improvement Components: ec2 Reporter: mwhudson Assignee: mwhudson Priority: Minor It's slightly inconvenient to have to use the 'default' security group for our slaves. It's only slightly inconvenient, but it seems that this should be pretty easy to fix, too. I may even try myself! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13782) It should be possible to reorder publishers on Ivy projects
Benoît Dufourd created JENKINS-13782: Summary: It should be possible to reorder publishers on Ivy projects Key: JENKINS-13782 URL: https://issues.jenkins-ci.org/browse/JENKINS-13782 Project: Jenkins Issue Type: Improvement Components: ivy Affects Versions: current Environment: Jenkins: 1.463 Ivy plugin: 1.21 Reporter: Benoît Dufourd Assignee: Timothy Bingaman Priority: Minor Since Jenkins 1.463, publishers can now be reordered by user. https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/UQLvxQclyb4 Ivy projects can't benefit from that improvement for the moment, it would be great if they could. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162794#comment-162794 ] Ido Ran commented on JENKINS-13007: --- I've work around the problem by installing previous version 1.1.15 of the plugin. You can download it from here http://updates.jenkins-ci.org/download/plugins/git/ Git plugin cannot find revision to build on Windows --- Key: JENKINS-13007 URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 Project: Jenkins Issue Type: Bug Components: git Environment: Windows 2008 Server 64 Bit NTFS Reporter: ritzmann Assignee: Nicolas De Loof Priority: Critical After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on Windows build slaves started failing like this: Started by user anonymous Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.Channel@95ff886:win-slave1 Using strategy: Default Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 (origin/master) Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.LocalChannel@470a4b80 Fetching changes from 1 remote Git repository Fetching upstream changes from d:\hudson\shared\repo.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The builds on our Linux slaves are not affected. Wiping the workspaces on the Windows slaves did not help. Both clones and checkouts/updates seem to fail with the same error. Downgrading back to 1.1.14 made the Windows builds work again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13435) Auto Install jdk from oracle downloads html instead of bin
[
https://issues.jenkins-ci.org/browse/JENKINS-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162795#comment-162795
]
sogabe commented on JENKINS-13435:
--
You should remove cache file under $JENKINS_HOME/cache/.
Auto Install jdk from oracle downloads html instead of bin
--
Key: JENKINS-13435
URL: https://issues.jenkins-ci.org/browse/JENKINS-13435
Project: Jenkins
Issue Type: Bug
Components: core
Reporter: Jenni Syed
On version 1.455 (saw on 1.459 as well), choosing to auto-install the jdk
from oracle results in an html page being downloaded and the message below.
When I look at the jdk.sh, it's the html page from oracle complaining about
not accepting the license terms. Also see:
https://groups.google.com/group/jenkinsci-users/browse_thread/thread/1d510fae9816f086
{quote}
Installing JDK jdk-1.5.0_22-oth-JPR
Downloading JDK from
http://download.oracle.com/otn/java/jdk/1.5.0_22/jdk-1_5_0_22-linux-amd64.bin
Downloading 5307bytes
Installing /home/exodus/jenkins/tools/jdk1.5_22/jdk.sh
[jdk1.5_22] $ /home/exodus/jenkins/tools/jdk1.5_22/jdk.sh -noregister
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 1: html: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 2: head: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 3: title: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 4: META: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 5: link: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 6: link: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 7:
: command not found
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 8: body: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 9: div: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 10: table: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 11: tr: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 12: syntax error near
unexpected token `'
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 12: ` td rowspan=2
valign=middle nowrapa href=http://www.oracle.com;img
src=/errors/us/assets/oralogo-small.gif width=154 height=19 hspace=10
vspace=25 border=0 /a/td
'
[EnvInject] - [ERROR] - SEVERE ERROR occurs: hudson.AbortException: Failed to
install JDK. Exit code=2
Finished: FAILURE
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13783) Unable to add 'EEN' post-build action since jenkins-1.464
Alexander Shusherov created JENKINS-13783: - Summary: Unable to add 'EEN' post-build action since jenkins-1.464 Key: JENKINS-13783 URL: https://issues.jenkins-ci.org/browse/JENKINS-13783 Project: Jenkins Issue Type: Bug Components: email-ext Reporter: Alexander Shusherov Priority: Critical Attachments: editable-email-notification.jpg After upgrading Jenkins to 1.464 adding Editable Email Notification via the 'Add post-build action' button (see snapshot attached) is impossible for new jobs. Selecting 'EEN' from the list and clicking simply does nothing. For pre-existing jobs with 'EEN' enabled deleting the 'EEN' action and creating it again succeeds. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
[ https://issues.jenkins-ci.org/browse/JENKINS-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Karl updated JENKINS-12235: Attachment: stacktrace.txt I get this problem even so often on Windows machines. I run Jenkins ver. 1.463 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel -- Key: JENKINS-12235 URL: https://issues.jenkins-ci.org/browse/JENKINS-12235 Project: Jenkins Issue Type: Bug Components: core, master-slave Reporter: Ghenadie Dumitru Attachments: jenkins_fatal_io_exception.txt, stacktrace.txt Below is the stacktrace. It happened when I ran two jobs on a master. After running a while, both jobs crashed with this exception. I think this might be caused by a small flip-flop connectivity of the network, but I didn't noticed any disconnection. Another cause may be the huge load of jenkins: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 25942 hudson15 0 6902m 5.8g 5720 S 0.3 74.3 401:22.30 java Does the jenkins runs its own garbage collector at some specified time? We have to restart every few days because it's getting slower and slower until hangs out. FATAL: Unable to delete script file /tmp/hudson8303731085225956739.sh hudson.util.IOException2: remote file operation failed: /tmp/hudson8303731085225956739.sh at hudson.remoting.Channel@30e472f4:build@autom-1 at hudson.FilePath.act(FilePath.java:781) at hudson.FilePath.act(FilePath.java:767) at hudson.FilePath.delete(FilePath.java:1022) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:461) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:499) at hudson.remoting.Request.call(Request.java:110) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:774) ... 13 more Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy29.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:859) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:461) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at
[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
[ https://issues.jenkins-ci.org/browse/JENKINS-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162797#comment-162797 ] Kristian Karl edited comment on JENKINS-12235 at 5/15/12 1:42 PM: -- I get this problem even so often on Windows machines. I run Jenkins ver. 1.463 See attached stacktrace.txt was (Author: krikar): I get this problem even so often on Windows machines. I run Jenkins ver. 1.463 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel -- Key: JENKINS-12235 URL: https://issues.jenkins-ci.org/browse/JENKINS-12235 Project: Jenkins Issue Type: Bug Components: core, master-slave Reporter: Ghenadie Dumitru Attachments: jenkins_fatal_io_exception.txt, stacktrace.txt Below is the stacktrace. It happened when I ran two jobs on a master. After running a while, both jobs crashed with this exception. I think this might be caused by a small flip-flop connectivity of the network, but I didn't noticed any disconnection. Another cause may be the huge load of jenkins: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 25942 hudson15 0 6902m 5.8g 5720 S 0.3 74.3 401:22.30 java Does the jenkins runs its own garbage collector at some specified time? We have to restart every few days because it's getting slower and slower until hangs out. FATAL: Unable to delete script file /tmp/hudson8303731085225956739.sh hudson.util.IOException2: remote file operation failed: /tmp/hudson8303731085225956739.sh at hudson.remoting.Channel@30e472f4:build@autom-1 at hudson.FilePath.act(FilePath.java:781) at hudson.FilePath.act(FilePath.java:767) at hudson.FilePath.delete(FilePath.java:1022) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:461) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:499) at hudson.remoting.Request.call(Request.java:110) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:774) ... 13 more Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy29.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:859) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at
[JIRA] (JENKINS-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
[ https://issues.jenkins-ci.org/browse/JENKINS-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162798#comment-162798 ] ebann commented on JENKINS-12124: - Same kind of issue here. I can't open some dashboardviews, Firefox says The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. Starting hudson with java -jar. All plugins up2date Jenkins ver. 1.464 WARNING: Untrapped Error in Servlet javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file: ### hudson_home/plugins/analysis-collector/WEB-INF/classes/hudson/plugins/analysis/collector/dashboard/WarningsTablePortlet/portlet.jelly:58:77: j:forEach hudson/plugins/tasks/TasksProjectAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:197) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:171) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) 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:135) 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:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] (JENKINS-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
[ https://issues.jenkins-ci.org/browse/JENKINS-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162798#comment-162798 ] ebann edited comment on JENKINS-12124 at 5/15/12 2:50 PM: -- Same kind of issue here. I can't open some dashboardviews, Firefox says The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. All plugins up2date Jenkins ver. 1.464 WARNING: Untrapped Error in Servlet javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file: ### hudson_home/plugins/analysis-collector/WEB-INF/classes/hudson/plugins/analysis/collector/dashboard/WarningsTablePortlet/portlet.jelly:58:77: j:forEach hudson/plugins/tasks/TasksProjectAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) [...] at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.commons.jelly.JellyTagException: file: ### hudson_home/plugins/analysis-collector/WEB-INF/classes/hudson/plugins/analysis/collector/dashboard/WarningsTablePortlet/portlet.jelly:58:77: j:forEach hudson/plugins/tasks/TasksProjectAction at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:735) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:290) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) [...] at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107) ... 66 more Caused by: java.lang.NoClassDefFoundError: hudson/plugins/tasks/TasksProjectAction at hudson.plugins.analysis.collector.dashboard.WarningsTablePortlet.getTasks(WarningsTablePortlet.java:255) 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.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) ... 140 more was (Author: ebann): Same kind of issue here. I can't open some dashboardviews, Firefox says The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. Starting hudson with java -jar. All plugins up2date Jenkins ver. 1.464 WARNING: Untrapped Error in Servlet javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file: ###
[JIRA] (JENKINS-13742) Field validation does not pass required query parameters when some fields are specified in a nested Describable
[ https://issues.jenkins-ci.org/browse/JENKINS-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162799#comment-162799 ] John McNally commented on JENKINS-13742: In case the short presentation of the plugin code is not clear, here is the entire commit: https://github.com/jenkinsci/collabnet-plugin/commit/4c7b516a7975ffc126ddf717476cefe4e0a84081 Field validation does not pass required query parameters when some fields are specified in a nested Describable --- Key: JENKINS-13742 URL: https://issues.jenkins-ci.org/browse/JENKINS-13742 Project: Jenkins Issue Type: Bug Components: collabnet, core, validating-string-parameter Affects Versions: current Environment: Problem is not environment dependent, but testing was on Ubuntu 10.04 using Firefox 11 as client. Reporter: John McNally Assignee: whsu Labels: jenkins Attachments: findNearBy.patch The collabnet plugin was updated/modernized a couple years ago to include code like the following: CNDocumentUploader.java DescriptorImpl /** * Form validation for upload path. */ public FormValidation doCheckUploadPath(CollabNetApp app, @QueryParameter String project, @QueryParameter String value) CollabNetApp.java public static CollabNetApp fromStapler(@QueryParameter boolean overrideAuth, @QueryParameter String url, @QueryParameter String username, @QueryParameter String password) config.jelly f:property field=connectionFactory / ... f:entry title=Upload Folder Path field=uploadPath f:textbox / /f:entry ConnectionFactory has url, username, and password properties The generated field validation javascript then uses the 'nearBy' function when passing query parameters to the checkUploadPath backend in order to find values of url, username, and password. However uploadPath has a parent element with name 'publisher', while the direct parent of url, username, and password is a div has name 'connectionFactory'. 'publisher' is then a grandparent of url, username, and password and because of this, the needed query parameters are not included. One might argue that the collabnet plugin should avoid this design, since it does not work, but the changes came from Kohsuke, so attempting find a fix which preserves the current design. A patch to the findNearBy function in hudson-behavior.js is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162800#comment-162800 ] Amir Isfy commented on JENKINS-13227: - Would this prohibit the 'change detection' stuff? I have not been able to detect the changes on the branch with the new one. CVS plugin 2.1 does not detect changes -- Key: JENKINS-13227 URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Guillaume Bilodeau Assignee: Michael Clarke Priority: Critical Labels: cvs Attachments: rlog.txt As presented in the user group: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS repository for a few weeks now, without any problems. The CVS plugin (v1.6) was using the local cvsnt install. We've since upgraded the CVS plugin to version 2.1 (by manually pinning the plugin) and since then, CVS changes are not detected. The CVS polling log is triggered properly, tons of cvs rlog instructions are sent, but at the end No changes is displayed. Using CVS plugin 1.6 the cvs polling command looked like this (executed at 5:26:21 PM EDT): cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D Thursday, March 22, 2012 9:26:21 PM UTC Using CVS plugin 2.1, the last cvs checkout command looked like this (executed at 11:56:16 AM EDT): cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 11:56:16 EDT -d portailInt portailInt We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13784) Environment Variables do not replace in shell scripts
Brian Booyah created JENKINS-13784:
--
Summary: Environment Variables do not replace in shell scripts
Key: JENKINS-13784
URL: https://issues.jenkins-ci.org/browse/JENKINS-13784
Project: Jenkins
Issue Type: Bug
Components: shell-script-scm
Affects Versions: current
Reporter: Brian Booyah
Assignee: Richard Sczepczenski
Priority: Blocker
Here is my shell script:
echo ${BUILD_NUMBER};
echo ${SERVER};
sed -e 's/NSString \*SERVER = @[A-Z0-9]*;/NSString \*SERVER = @${SERVER};/g'
Here is the output when the build runs. Notice the second ${SERVER} is not
replaced.
+ echo 98
98
+ echo CI1
CI1
+ sed -e 's/NSString \*SERVER = @[A-Z0-9]*;/NSString \*SERVER =
@${SERVER};/g'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13785) Use Google Apis SDK Add-on via Target ID fails
David Müller created JENKINS-13785:
--
Summary: Use Google Apis SDK Add-on via Target ID fails
Key: JENKINS-13785
URL: https://issues.jenkins-ci.org/browse/JENKINS-13785
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Affects Versions: current
Environment: Ubuntu Server x64, Running Jenkins stand-alone, Matrix
build, using maven.
Reporter: David Müller
Assignee: Christopher Orr
I want to run a Matrix Job with Google Apis for instrumentation tests
Simply using the name from the android list target command like Google
Inc.:Google APIs:7 leads to problems in the build because of the spaces in the
name.
When trying to use the target id it gives me mixed results, the plugin seems
not to recognize the id.
For example, from the Konsole output:
First, using id 27, which stands for Google Inc.:Google APIs:15 in my
environment
{noformat}
$ /opt/android-sdk-linux/tools/android list target
[android] The configured Android platform needs to be installed: 27
[android] Installing the '27' SDK component(s)...
$ /opt/android-sdk-linux/tools/android update sdk -o -u -t 27
Error: Flag '-o' is not valid for 'update sdk'.
[...]
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_27.avd
[android] Setting hardware properties:
{noformat}
This build ultimately succeeds, although no sdk can be installed.
Second, using id 6, which stands for Google Inc.:Google APIs:7 in my
environment
{noformat}
[android] The configured Android platform needs to be installed: android-6
[android] Installing the 'android-6' SDK component(s)...
Error: Flag '-o' is not valid for 'update sdk'.
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_android-6.avd
[android] Failed to run AVD creation command
Error: Target id is not valid. Use 'android list targets' to get the
target ids.
{noformat}
This build fails, because no Android 6 is not available locally.
Now, the use of ids would only be a workaround, as the ids are dependent on the
sdk installation.
But failing a way to replace the whitespaces in the name, it would be nice if
the plugin would use the ids in the correct way when calling the android cli
tools.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13785) Use Google Apis SDK Add-on via Target ID fails
[
https://issues.jenkins-ci.org/browse/JENKINS-13785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Müller updated JENKINS-13785:
---
Description:
I want to run a Matrix Job with Google Apis for instrumentation tests
Simply using the name from the android list target command like Google
Inc.:Google APIs:7 leads to problems in the build because of the spaces in the
name.
When trying to use the target id it gives me mixed results, the plugin seems
not to recognize the id.
For example, from the Konsole output:
First, using id 27, which stands for Google Inc.:Google APIs:15 in my
environment
{noformat}
$ /opt/android-sdk-linux/tools/android list target
[android] The configured Android platform needs to be installed: 27
[android] Installing the '27' SDK component(s)...
$ /opt/android-sdk-linux/tools/android update sdk -o -u -t 27
Error: Flag '-o' is not valid for 'update sdk'.
[...]
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_27.avd
[android] Setting hardware properties:
{noformat}
This build ultimately succeeds, although no sdk can be installed.
Second, using id 6, which stands for Google Inc.:Google APIs:7 in my
environment
{noformat}
[android] The configured Android platform needs to be installed: android-6
[android] Installing the 'android-6' SDK component(s)...
Error: Flag '-o' is not valid for 'update sdk'.
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_android-6.avd
[android] Failed to run AVD creation command
Error: Target id is not valid. Use 'android list targets' to get the
target ids.
{noformat}
This build fails, because no Android 6 is not available locally.
Now, the use of ids would only be a workaround, as the ids are dependent on the
sdk installation.
But failing a way to replace the whitespaces in the name, it would be nice if
the plugin would use the ids in the correct way when calling the android cli
tools.
When parsing the output from list targets, the plugin should recognize target
ids.
was:
I want to run a Matrix Job with Google Apis for instrumentation tests
Simply using the name from the android list target command like Google
Inc.:Google APIs:7 leads to problems in the build because of the spaces in the
name.
When trying to use the target id it gives me mixed results, the plugin seems
not to recognize the id.
For example, from the Konsole output:
First, using id 27, which stands for Google Inc.:Google APIs:15 in my
environment
{noformat}
$ /opt/android-sdk-linux/tools/android list target
[android] The configured Android platform needs to be installed: 27
[android] Installing the '27' SDK component(s)...
$ /opt/android-sdk-linux/tools/android update sdk -o -u -t 27
Error: Flag '-o' is not valid for 'update sdk'.
[...]
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_27.avd
[android] Setting hardware properties:
{noformat}
This build ultimately succeeds, although no sdk can be installed.
Second, using id 6, which stands for Google Inc.:Google APIs:7 in my
environment
{noformat}
[android] The configured Android platform needs to be installed: android-6
[android] Installing the 'android-6' SDK component(s)...
Error: Flag '-o' is not valid for 'update sdk'.
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_de-DE_120_WVGA_android-6.avd
[android] Failed to run AVD creation command
Error: Target id is not valid. Use 'android list targets' to get the
target ids.
{noformat}
This build fails, because no Android 6 is not available locally.
Now, the use of ids would only be a workaround, as the ids are dependent on the
sdk installation.
But failing a way to replace the whitespaces in the name, it would be nice if
the plugin would use the ids in the correct way when calling the android cli
tools.
Use Google Apis SDK Add-on via Target ID fails
--
Key: JENKINS-13785
URL: https://issues.jenkins-ci.org/browse/JENKINS-13785
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Affects Versions: current
Environment: Ubuntu Server x64, Running Jenkins stand-alone, Matrix
build, using maven.
Reporter: David Müller
Assignee: Christopher Orr
I want to run a Matrix Job with Google Apis for instrumentation tests
Simply using the name from the android list target command like Google
Inc.:Google APIs:7 leads to problems in the build because of the spaces in
the name.
When trying to use the target id it gives me mixed results, the plugin seems
not to recognize the id.
For example, from the Konsole output:
First, using id 27, which stands for Google Inc.:Google APIs:15 in my
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Hofmann reopened JENKINS-13745: - The configuration do not trigger any exception, but it is not saved :-(. After reloading the configuration page, default parameters are printed. Additionally an exception is generated when the post-build action is executed: ERROR: Publisher org.jenkinsci.plugins.valgrind.ValgrindPublisher aborted due to exception java.lang.NullPointerException at org.jenkinsci.plugins.valgrind.ValgrindPublisher.perform(ValgrindPublisher.java:84) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632) at hudson.model.Run.run(Run.java:1459) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception Key: JENKINS-13745 URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 Project: Jenkins Issue Type: Bug Components: plugin Affects Versions: current Environment: Ubuntu 12.04 Jenkins 1.463 Reporter: Georg Hofmann Assignee: Johannes Ohlemacher Labels: exception, plugin Fix For: current Attachments: hudson_valgrind_plugin_excpetion.txt I have tested the Valgrind plugin, but I cannot configure it. The build configuration part is working find, but when I try to configure the publish valgrind results part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459
[ https://issues.jenkins-ci.org/browse/JENKINS-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jacob_robertson updated JENKINS-13464: -- Component/s: sectioned-view Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459 -- Key: JENKINS-13464 URL: https://issues.jenkins-ci.org/browse/JENKINS-13464 Project: Jenkins Issue Type: Bug Components: sectioned-view, view-job-filters Reporter: Vincent Latombe Assignee: jacob_robertson Priority: Blocker Attachments: StackOverflow.txt Due to https://github.com/jenkinsci/jenkins/commit/85e13303f8cfbebeb7dab347fda8ccf4069070b6 , any view using Other Views filter now gets a StackOverflowError. The reason is that it uses a wrong way of retrieving the referenced view, by getting first 'all' the views. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13786) Plugin is not compliant with new Jenkins core gui lay-out
Lars Kruse created JENKINS-13786: Summary: Plugin is not compliant with new Jenkins core gui lay-out Key: JENKINS-13786 URL: https://issues.jenkins-ci.org/browse/JENKINS-13786 Project: Jenkins Issue Type: Improvement Components: prqa Reporter: Lars Kruse Assignee: Lars Kruse the newest Jenkins release doesn't seem to work at all with the PRQA plugin (the dialog doesn't show up) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13787) Error when job is running on slave
Lars Kruse created JENKINS-13787: Summary: Error when job is running on slave Key: JENKINS-13787 URL: https://issues.jenkins-ci.org/browse/JENKINS-13787 Project: Jenkins Issue Type: Bug Components: prqa Reporter: Lars Kruse Assignee: Lars Kruse If I set up the PRQA plugin on a Jenkins running on my machine (just install the official 1.441 war file and start it via java -jar jenkins.war, everything works fine. Now if I setup my machine to run as a slave and let the job be triggered by the master somewhere else (also version 1.441), I get the following error: This job will try to create a report with the following selected parameters: QAR selected project file:Sources\QAC\LibFusion\LibFusion.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources\QAC\LibFusion\LibFusion.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml Viewer dummy not available, result will not be rendered. Generating - Please wait... Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xhtml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report-Main.xhtml Finished remote reporting. Found report. Attempting to copy Compliance Report.xhtml to artifacts directory: /home/qqmthk1/.jenkins/jobs/OFRF_LibFusion_QAC/builds/2012-05-11_17-32-05/archive Attempting to copy report to following target: Compliance Report.xhtml Succesfully copied report ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception java.lang.NullPointerException at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Notifying upstream projects of job completion Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13264) fail checkout 2 modules with different path
[ https://issues.jenkins-ci.org/browse/JENKINS-13264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162803#comment-162803 ] James Gustafson commented on JENKINS-13264: --- Yes, it is Windows 7 64-bit with Jenkins 1.464 installed as a service. fail checkout 2 modules with different path --- Key: JENKINS-13264 URL: https://issues.jenkins-ci.org/browse/JENKINS-13264 Project: Jenkins Issue Type: Bug Components: cvs Environment: linux Reporter: Eric Co Assignee: Michael Clarke Fix For: current I create two cvs modules with the path lib/flac-1.2.1 drv/linux/fuse when it check out, got the error: cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib/flac-1.2.1 lib/flac-1.2.1 cvs [checkout aborted]: could not change directory to requested checkout directory `lib': No such file or directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13788) Git user and Crowd 2 authenticated user should be equal (one User-Id)
Thomas Lehmann created JENKINS-13788: Summary: Git user and Crowd 2 authenticated user should be equal (one User-Id) Key: JENKINS-13788 URL: https://issues.jenkins-ci.org/browse/JENKINS-13788 Project: Jenkins Issue Type: Bug Components: crowd2, git Affects Versions: current Environment: Jenkins 1.462 on CentOS 5.8 SunJDK 1.7.0_03-b04 Crowd2 Plugin 1.4 Git Plugin 1.1.12 Against Crowd 2.4.2 Reporter: Thomas Lehmann Assignee: Thorsten Heit This is very complicated to describe. I'll try to describe our setup, our Jenkins configuration's chronology the problem and my assumptions to the current bug... I'll describe the whole situation which probably makes the description harder to understand, but I want to provide as much information as possible. Please help me to make this description more specifcally and/or create another issue for separate problems. Thank you. :) Setup -- Jenkins configured to authenticate through Crowd 2 Plugin (works fine so far, also with authorization) The authenticated username is Forename Lastname (crowd-userid). Crowd holds the crentral email address of each user. Out projects are checked out through Git. Older commits may have malformed auther name and email. Recent commits are all in form Username = 'Forename Lastname' and email = 'The same email address as in crowd'. Cronology -- - This Jenkins installation started with no security configured. - I can't ensure there was never a Jenkins-based usermanagement configured as this installation was administered by a colleague before. - All jobs check out from a Git-Repository - Before today the Peoples view showed a variety of user id from more or less real names (also misleading names like root, see my assumptions below) over through odd usernames like contextMenu (we can't figure out what caused this username). - Some users seemed to appear twice (this is actually another issue) - Today I've configures authentication through the Crowd 2 Plugin - Now there are further users, one for each Crowd user that has logged in once Problem There are at least 2, sometimes 3 users (obviously depending on how much different Git users exists) in Peoples view. Only one of them, apparently the user generated out of the Git user can show information under Builds Assumptions - A username is generated for each user of a Git commit - If there was accidently no username like or login login@hostname or root root@hostname such user IDs (, login, root) will be generated So how can I... - delete these accidently created users - tell Jenkins to see/understand automatically generated user x is equal to Crowd user X or at least map each Git user to a Crow 2 user - keep Jenkins from generating user IDs for all Git users I know there are other issues and solutions on the web about removing users, but deleting in users/ did not work either. All user-directories are re-generated on Jenkins startup (all having statup date). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Ohlemacher updated JENKINS-13745: -- Component/s: valgrind (was: plugin) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception Key: JENKINS-13745 URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 Project: Jenkins Issue Type: Bug Components: valgrind Affects Versions: current Environment: Ubuntu 12.04 Jenkins 1.463 Reporter: Georg Hofmann Assignee: Johannes Ohlemacher Labels: exception, plugin Fix For: current Attachments: hudson_valgrind_plugin_excpetion.txt I have tested the Valgrind plugin, but I cannot configure it. The build configuration part is working find, but when I try to configure the publish valgrind results part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12250) Critical block can not be added into conditional step
[
https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162805#comment-162805
]
Carsten Pfeiffer commented on JENKINS-12250:
I've often had trouble uploading plugins via the Advanced tab of the plugin
manager. What did work was manually extracting the .hpi file in the jenkins
{{plugins}} folder.
Critical block can not be added into conditional step
-
Key: JENKINS-12250
URL: https://issues.jenkins-ci.org/browse/JENKINS-12250
Project: Jenkins
Issue Type: Bug
Components: conditional-buildstep, exclusion
Environment: Jenkins 1.445
Jenkins Exclusion Plug-in 0.6
conditional-buildstep 0.2
Reporter: Oleksandr Popov
Assignee: Anthony Roux
Priority: Critical
Attachments: critical-block.PNG
I'm not able to add critical block into conditional step. See screen-shot for
details
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13435) Auto Install jdk from oracle downloads html instead of bin
[
https://issues.jenkins-ci.org/browse/JENKINS-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162804#comment-162804
]
Andreyev Melo commented on JENKINS-13435:
-
Great! Using version 1.464 in a clean install it works! Thanks a lot!
Auto Install jdk from oracle downloads html instead of bin
--
Key: JENKINS-13435
URL: https://issues.jenkins-ci.org/browse/JENKINS-13435
Project: Jenkins
Issue Type: Bug
Components: core
Reporter: Jenni Syed
On version 1.455 (saw on 1.459 as well), choosing to auto-install the jdk
from oracle results in an html page being downloaded and the message below.
When I look at the jdk.sh, it's the html page from oracle complaining about
not accepting the license terms. Also see:
https://groups.google.com/group/jenkinsci-users/browse_thread/thread/1d510fae9816f086
{quote}
Installing JDK jdk-1.5.0_22-oth-JPR
Downloading JDK from
http://download.oracle.com/otn/java/jdk/1.5.0_22/jdk-1_5_0_22-linux-amd64.bin
Downloading 5307bytes
Installing /home/exodus/jenkins/tools/jdk1.5_22/jdk.sh
[jdk1.5_22] $ /home/exodus/jenkins/tools/jdk1.5_22/jdk.sh -noregister
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 1: html: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 2: head: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 3: title: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 4: META: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 5: link: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 6: link: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 7:
: command not found
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 8: body: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 9: div: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 10: table: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 11: tr: No such file or
directory
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 12: syntax error near
unexpected token `'
/home/exodus/jenkins/tools/jdk1.5_22/jdk.sh: line 12: ` td rowspan=2
valign=middle nowrapa href=http://www.oracle.com;img
src=/errors/us/assets/oralogo-small.gif width=154 height=19 hspace=10
vspace=25 border=0 /a/td
'
[EnvInject] - [ERROR] - SEVERE ERROR occurs: hudson.AbortException: Failed to
install JDK. Exit code=2
Finished: FAILURE
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162807#comment-162807 ] Amir Isfy commented on JENKINS-13227: - I am building a Module that comes from a CVS branch. 'cvs checkout' correctly keeps the branch name in the Tag file. Now after a clean checkout if the 'Use Update' is checked under 'Source Code Management' then the command looks like: cvs update -d -P -r branch_name -D 15 May 2012 13:12:24 -0600 module_name After this the Tag file will have 'D2012.05.15.19.12.24' in it which basically corresponds to the Head now. This could be related to this. Help please. CVS plugin 2.1 does not detect changes -- Key: JENKINS-13227 URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Guillaume Bilodeau Assignee: Michael Clarke Priority: Critical Labels: cvs Attachments: rlog.txt As presented in the user group: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS repository for a few weeks now, without any problems. The CVS plugin (v1.6) was using the local cvsnt install. We've since upgraded the CVS plugin to version 2.1 (by manually pinning the plugin) and since then, CVS changes are not detected. The CVS polling log is triggered properly, tons of cvs rlog instructions are sent, but at the end No changes is displayed. Using CVS plugin 1.6 the cvs polling command looked like this (executed at 5:26:21 PM EDT): cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D Thursday, March 22, 2012 9:26:21 PM UTC Using CVS plugin 2.1, the last cvs checkout command looked like this (executed at 11:56:16 AM EDT): cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 11:56:16 EDT -d portailInt portailInt We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12250) Critical block can not be added into conditional step
[ https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162809#comment-162809 ] domi commented on JENKINS-12250: does that mean the issue is resolved with this SNAPSHOT and I should do a release of it? Critical block can not be added into conditional step - Key: JENKINS-12250 URL: https://issues.jenkins-ci.org/browse/JENKINS-12250 Project: Jenkins Issue Type: Bug Components: conditional-buildstep, exclusion Environment: Jenkins 1.445 Jenkins Exclusion Plug-in 0.6 conditional-buildstep 0.2 Reporter: Oleksandr Popov Assignee: Anthony Roux Priority: Critical Attachments: critical-block.PNG I'm not able to add critical block into conditional step. See screen-shot for details -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13007) Git plugin cannot find revision to build on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162810#comment-162810 ] chanti vlad commented on JENKINS-13007: --- @Martin-Louis: yes git is working manually on windows. We are here concerned about letting jenkins check out automatically an existing tag, whcih results in the error described above. Git plugin cannot find revision to build on Windows --- Key: JENKINS-13007 URL: https://issues.jenkins-ci.org/browse/JENKINS-13007 Project: Jenkins Issue Type: Bug Components: git Environment: Windows 2008 Server 64 Bit NTFS Reporter: ritzmann Assignee: Nicolas De Loof Priority: Critical After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on Windows build slaves started failing like this: Started by user anonymous Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.Channel@95ff886:win-slave1 Using strategy: Default Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 (origin/master) Checkout:my-app / d:\hudson\workspace\my-app - hudson.remoting.LocalChannel@470a4b80 Fetching changes from 1 remote Git repository Fetching upstream changes from d:\hudson\shared\repo.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The builds on our Linux slaves are not affected. Wiping the workspaces on the Windows slaves did not help. Both clones and checkouts/updates seem to fail with the same error. Downgrading back to 1.1.14 made the Windows builds work again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13789) 'cvs update' replaces the Tag file which has the branch name in it with a Tag with time and date which effectively corresponds back to the Head
Amir Isfy created JENKINS-13789: --- Summary: 'cvs update' replaces the Tag file which has the branch name in it with a Tag with time and date which effectively corresponds back to the Head Key: JENKINS-13789 URL: https://issues.jenkins-ci.org/browse/JENKINS-13789 Project: Jenkins Issue Type: Bug Components: cvs, cvs-tag Reporter: Amir Isfy I am building a Module that comes from a CVS branch. 'cvs checkout' correctly keeps the branch name in the Tag file. Now after a clean checkout if the 'Use Update' is checked under 'Source Code Management' then the command looks like: cvs update -d -P -r branch_name -D 15 May 2012 13:12:24 -0600 module_name After this the Tag file will have 'D2012.05.15.19.12.24' in it which basically corresponds to the Head now. This could be related to this. Help please. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Ohlemacher resolved JENKINS-13745. --- Resolution: Fixed oops, that should not have happened...shame on me. I released versions 0.7 and 0.8 to address this issue, i tested it with 1.464 and it should finally work now. Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception Key: JENKINS-13745 URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 Project: Jenkins Issue Type: Bug Components: valgrind Affects Versions: current Environment: Ubuntu 12.04 Jenkins 1.463 Reporter: Georg Hofmann Assignee: Johannes Ohlemacher Labels: exception, plugin Fix For: current Attachments: hudson_valgrind_plugin_excpetion.txt I have tested the Valgrind plugin, but I cannot configure it. The build configuration part is working find, but when I try to configure the publish valgrind results part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162812#comment-162812 ] Amir Isfy commented on JENKINS-13227: - So 'cvs update' is out of the question. So here is what I did: cvs checkout of the branch build commit a dummy change wipe out workspace cvs checkout of the branch build Changes page: No changes. Then I committed another change Let the SCM poll trigger (this is also a clean build without 'Use Update' checked) No change. Didn't work :( CVS plugin 2.1 does not detect changes -- Key: JENKINS-13227 URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Guillaume Bilodeau Assignee: Michael Clarke Priority: Critical Labels: cvs Attachments: rlog.txt As presented in the user group: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS repository for a few weeks now, without any problems. The CVS plugin (v1.6) was using the local cvsnt install. We've since upgraded the CVS plugin to version 2.1 (by manually pinning the plugin) and since then, CVS changes are not detected. The CVS polling log is triggered properly, tons of cvs rlog instructions are sent, but at the end No changes is displayed. Using CVS plugin 1.6 the cvs polling command looked like this (executed at 5:26:21 PM EDT): cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D Thursday, March 22, 2012 9:26:21 PM UTC Using CVS plugin 2.1, the last cvs checkout command looked like this (executed at 11:56:16 AM EDT): cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 11:56:16 EDT -d portailInt portailInt We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162813#comment-162813 ] Amir Isfy commented on JENKINS-13227: - Is there any way to revert back to what was there in say version 1.6? CVS plugin 2.1 does not detect changes -- Key: JENKINS-13227 URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Guillaume Bilodeau Assignee: Michael Clarke Priority: Critical Labels: cvs Attachments: rlog.txt As presented in the user group: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS repository for a few weeks now, without any problems. The CVS plugin (v1.6) was using the local cvsnt install. We've since upgraded the CVS plugin to version 2.1 (by manually pinning the plugin) and since then, CVS changes are not detected. The CVS polling log is triggered properly, tons of cvs rlog instructions are sent, but at the end No changes is displayed. Using CVS plugin 1.6 the cvs polling command looked like this (executed at 5:26:21 PM EDT): cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D Thursday, March 22, 2012 9:26:21 PM UTC Using CVS plugin 2.1, the last cvs checkout command looked like this (executed at 11:56:16 AM EDT): cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 11:56:16 EDT -d portailInt portailInt We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8617) cannot customize security group to launch slaves into
[ https://issues.jenkins-ci.org/browse/JENKINS-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162814#comment-162814 ] mwhudson commented on JENKINS-8617: --- The problem with tags, unless I'm misremembering or things have changed, is that you can't start an instance with a tag, you can only start an instance and then tag it. So there is a risk of a race there. But you're right that it's probably a bit silly to use security groups for that, and there is certainly a case for wanting to have per slave template security groups rather than per cloud groups. cannot customize security group to launch slaves into - Key: JENKINS-8617 URL: https://issues.jenkins-ci.org/browse/JENKINS-8617 Project: Jenkins Issue Type: Improvement Components: ec2 Reporter: mwhudson Assignee: mwhudson Priority: Minor It's slightly inconvenient to have to use the 'default' security group for our slaves. It's only slightly inconvenient, but it seems that this should be pretty easy to fix, too. I may even try myself! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
chikigai created JENKINS-13790: -- Summary: Subversion externals fail Key: JENKINS-13790 URL: https://issues.jenkins-ci.org/browse/JENKINS-13790 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows XP SP3 Reporter: chikigai Updates on a repository with svn:externals property set fail with the following: AssertionError: appears to be using unpatched svnkit at jar:xxx/SVNEvent.class The issue is present with the latest 1.40 release. The issue is not preset with the 1.39 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13791) naginator plugin NullPointerException on successful build
jieryn created JENKINS-13791:
Summary: naginator plugin NullPointerException on successful build
Key: JENKINS-13791
URL: https://issues.jenkins-ci.org/browse/JENKINS-13791
Project: Jenkins
Issue Type: Bug
Components: naginator
Reporter: jieryn
Assignee: Nayan Hajratwala
Jenkins v1.447.1
Naginator Plugin v1.6.1
{code}[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 24:13.510s
[INFO] Finished at: Tue May 15 22:27:18 EDT 2012
[INFO] Final Memory: 38M/2048M
[INFO]
ERROR: Processing failed due to a bug in the code. Please report this to
jenkinsci-us...@googlegroups.com
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
project=hudson.maven.MavenModuleSet@6b006b0[release_com.acme.project]
project.getModules()=[hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:],
hudson.maven.MavenModule@64856485[release_com.acme.project/com.acme.project:cim][release_com.acme.project/com.acme.project:cim][relativePath:cim],
hudson.maven.MavenModule@b100b10[release_com.acme.project/com.acme.project:dao][release_com.acme.project/com.acme.project:dao][relativePath:dao],
hudson.maven.MavenModule@1e001e[release_com.acme.project/com.acme.project:domain][release_com.acme.project/com.acme.project:domain][relativePath:domain],
hudson.maven.MavenModule@1e271e27[release_com.acme.project/com.acme.project:gwt][release_com.acme.project/com.acme.project:gwt][relativePath:gwt],
hudson.maven.MavenModule@7a0b7a0b[release_com.acme.project/com.acme.project:mock][release_com.acme.project/com.acme.project:mock][relativePath:mock],
hudson.maven.MavenModule@4ac34ac3[release_com.acme.project/com.acme.project:service][release_com.acme.project/com.acme.project:service][relativePath:service],
hudson.maven.MavenModule@3b173b17[release_com.acme.project/com.acme.project:war][release_com.acme.project/com.acme.project:war][relativePath:war],
hudson.maven.MavenModule@e030e03[release_com.acme.project/com.acme.project:ws][release_com.acme.project/com.acme.project:ws][relativePath:ws],
hudson.maven.MavenModule@474c474c[release_com.acme.project/com.acme.project.ws:domain][release_com.acme.project/com.acme.project.ws:domain][relativePath:ws/domain],
hudson.maven.MavenModule@18041804[release_com.acme.project/com.acme.project.ws:rs][release_com.acme.project/com.acme.project.ws:rs][relativePath:ws/rs],
hudson.maven.MavenModule@26132613[release_com.acme.project/com.acme.project.ws:war][release_com.acme.project/com.acme.project.ws:war][relativePath:ws/war]]
project.getRootModule()=hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:]
FATAL: null
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
{code}
--
This message is
[JIRA] (JENKINS-13791) naginator plugin NullPointerException on successful build
[
https://issues.jenkins-ci.org/browse/JENKINS-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162815#comment-162815
]
jieryn commented on JENKINS-13791:
--
https://github.com/jenkinsci/naginator-plugin/pull/2
naginator plugin NullPointerException on successful build
-
Key: JENKINS-13791
URL: https://issues.jenkins-ci.org/browse/JENKINS-13791
Project: Jenkins
Issue Type: Bug
Components: naginator
Reporter: jieryn
Assignee: Nayan Hajratwala
Jenkins v1.447.1
Naginator Plugin v1.6.1
{code}[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 24:13.510s
[INFO] Finished at: Tue May 15 22:27:18 EDT 2012
[INFO] Final Memory: 38M/2048M
[INFO]
ERROR: Processing failed due to a bug in the code. Please report this to
jenkinsci-us...@googlegroups.com
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at
hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
project=hudson.maven.MavenModuleSet@6b006b0[release_com.acme.project]
project.getModules()=[hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:],
hudson.maven.MavenModule@64856485[release_com.acme.project/com.acme.project:cim][release_com.acme.project/com.acme.project:cim][relativePath:cim],
hudson.maven.MavenModule@b100b10[release_com.acme.project/com.acme.project:dao][release_com.acme.project/com.acme.project:dao][relativePath:dao],
hudson.maven.MavenModule@1e001e[release_com.acme.project/com.acme.project:domain][release_com.acme.project/com.acme.project:domain][relativePath:domain],
hudson.maven.MavenModule@1e271e27[release_com.acme.project/com.acme.project:gwt][release_com.acme.project/com.acme.project:gwt][relativePath:gwt],
hudson.maven.MavenModule@7a0b7a0b[release_com.acme.project/com.acme.project:mock][release_com.acme.project/com.acme.project:mock][relativePath:mock],
hudson.maven.MavenModule@4ac34ac3[release_com.acme.project/com.acme.project:service][release_com.acme.project/com.acme.project:service][relativePath:service],
hudson.maven.MavenModule@3b173b17[release_com.acme.project/com.acme.project:war][release_com.acme.project/com.acme.project:war][relativePath:war],
hudson.maven.MavenModule@e030e03[release_com.acme.project/com.acme.project:ws][release_com.acme.project/com.acme.project:ws][relativePath:ws],
hudson.maven.MavenModule@474c474c[release_com.acme.project/com.acme.project.ws:domain][release_com.acme.project/com.acme.project.ws:domain][relativePath:ws/domain],
hudson.maven.MavenModule@18041804[release_com.acme.project/com.acme.project.ws:rs][release_com.acme.project/com.acme.project.ws:rs][relativePath:ws/rs],
hudson.maven.MavenModule@26132613[release_com.acme.project/com.acme.project.ws:war][release_com.acme.project/com.acme.project.ws:war][relativePath:ws/war]]
project.getRootModule()=hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:]
FATAL: null
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at
hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at
