[JIRA] [cli] (JENKINS-17929) Fail to run 'groovysh' in CLI due to insufficient permission
Meng Xin Zhu
created JENKINS-17929
Fail to run groovysh in CLI due to insufficient permission
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
cli
Created:
13/May/13 6:00 AM
Description:
1: verified that I am authenticated: java -jar jenkins-cli.jar -s http://myserver/jenkins who-am-i
Authenticated as: myuser
Authorities:
authenticated
2: tried to run a trivial script via groovysh and got an error
java -jar jenkins-cli.jar -s http://myserver/jenkins groovysh 'jenkins.model.Jenkins.instance.pluginManager.plugins.each { println("${it.longName} - ${it.version}") };'
Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
at $Proxy2.main(Unknown Source)
at hudson.cli.CLI.execute(CLI.java:271)
at hudson.cli.CLI._main(CLI.java:417)
at hudson.cli.CLI.main(CLI.java:322)
Caused by: hudson.remoting.ProxyException: hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
The workaround is using command 'groovysh' instead.
java -jar jenkins-cli.jar -s http://localhost:8080/jenkins/ groovy test_script.gsh
It's also discussed in group.1
1 https://groups.google.com/forum/#!msg/jenkinsci-users/Vb1p7tbWfQk/4vcVrHOC19MJ
Environment:
version 1.502
Project:
Jenkins
Priority:
Major
Reporter:
Meng Xin Zhu
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: JMS Restart
Thanks for your reply. This is the error i get [startJMS] $ /bin/bash /var/tmp/hudson3826384858297686021.sh FATAL: command execution failed java.io.IOException: : not found at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.init(UNIXProcess.java:53) at java.lang.ProcessImpl.start(ProcessImpl.java:65) at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:763) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:637) Build step 'Execute shell' marked build as failure Finished: FAILURE If i apply after the cd /opt/app/documentum/share/jboss4.3.0/server nohup ./startMethodServer.sh I get below error startJMS] $ /bin/sh -xe /var/tmp/hudson7153432316218641686.sh + cd /opt/app/documentum/share/jboss4.3.0/server + nohup ./startMethodServer.sh = JBoss Bootstrap Environment JBOSS_HOME: /opt/app/documentum/share/jboss4.3.0 JAVA: /opt/app/documentum/share/jboss4.3.0/jdk/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1024m -Xmx2048m CLASSPATH: /opt/app/documentum/share/jboss4.3.0/bin/run.jar:/opt/app/documentum/share/jboss4.3.0/jdk/lib/tools.jar = 08:05:06,432 INFO [Server] Starting JBoss (MX MicroKernel)... 08:05:06,436 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA_CP06 (build: SVNTag=JBPAPP_4_3_0_GA_CP06 date=200907141446) 08:05:06,441 INFO [Server] Home Dir: /opt/app/documentum/share/jboss4.3.0 08:05:06,441 INFO [Server] Home URL: file:/opt/app/documentum/share/jboss4.3.0/ 08:05:06,444 INFO [Server] Patch URL: null 08:05:06,445 INFO [Server] Server Name: DctmServer_MethodServer 08:05:06,445 INFO [Server] Server Home Dir: /opt/app/documentum/share/jboss4.3.0/server/DctmServer_MethodServer 08:05:06,446 INFO [Server] Server Home URL: file:/opt/app/documentum/share/jboss4.3.0/server/DctmServer_MethodServer/ 08:05:06,447 INFO [Server] Server Log Dir: /opt/app/documentum/share/jboss4.3.0/server/DctmServer_MethodServer/log 08:05:06,448 INFO [Server] Server Temp Dir: /opt/app/documentum/share/jboss4.3.0/server/DctmServer_MethodServer/tmp 08:05:06,450 INFO [Server] Root Deployment Filename: jboss-service.xml 08:05:07,507 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 08:05:07,508 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 08:05:07,508 INFO [ServerInfo] OS-System: SunOS 5.10,sparc 08:05:07,519 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms1024m -Xmx2048m -Djava.endorsed.dirs=/opt/app/documentum/share/jboss4.3.0/lib/endorsed 08:05:08,740 INFO [Server] Core system initialized Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information 08:05:18,286 INFO [Server] Runtime shutdown hook called, forceHalt: true 08:05:18,287 INFO [Server] JBoss SHUTDOWN: Undeploying all packages 08:05:18,335 INFO [WebService] Using RMI server codebase: http://appt4-mb2:9083/ 08:05:18,349 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 08:05:18,506 INFO [Server] Shutdown complete Shutdown complete 08:05:18,568 INFO [STDOUT] Halting VM 08:05:18,578 WARN [ServiceController] Problem creating service jboss.system:type=Log4jService,service=Logging java.lang.IllegalStateException: Invalid usage of undeployed classloader at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:625) at java.lang.ClassLoader.loadClass(ClassLoader.java:303) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:467) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316) at
Re: JMS Restart
Also, cd /opt/app/documentum/share/jboss4.3.0/server nohup ./startMethodServer.sh [startJMS] $ /bin/sh -xe /var/tmp/hudson5714722254593125383.sh + cd /opt/app/documentum/share/jboss4.3.0/server + nohup ./startMethodServer.sh = JBoss Bootstrap Environment JBOSS_HOME: /opt/app/documentum/share/jboss4.3.0 JAVA: /opt/app/documentum/share/jboss4.3.0/jdk/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1024m -Xmx2048m CLASSPATH: /opt/app/documentum/share/jboss4.3.0/bin/run.jar:/opt/app/documentum/share/jboss4.3.0/jdk/lib/tools.jar = 08:21:34,074 INFO [Server] Starting JBoss (MX MicroKernel)... 08:21:34,078 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA_CP06 (build: SVNTag=JBPAPP_4_3_0_GA_CP06 date=200907141446) 08:21:34,083 INFO [Server] Home Dir: /opt/app/documentum/share/jboss4.3.0 08:21:34,084 INFO [Server] Home URL: file:/opt/app/documentum/share/jboss4.3.0/ 08:21:34,087 INFO [Server] Patch URL: null 08:21:34,087 INFO [Server] Server Name: DctmServer_MethodServer 08:21:34,088 INFO [Server] Server Home Dir: /opt/app/documentum/share/jboss4.3.0/server/DctmServer_MethodServer 08:21:34,089 INFO [Server] Server Home URL: file:/opt/app/documentum/share/jboss4.3.0/server/DctmServer_MethodServer/ 08:21:34,089 INFO [Server] Server Log Dir: /opt/app/documentum/share/jboss4.3.0/server/DctmServer_MethodServer/log 08:21:34,090 INFO [Server] Server Temp Dir: /opt/app/documentum/share/jboss4.3.0/server/DctmServer_MethodServer/tmp 08:21:34,092 INFO [Server] Root Deployment Filename: jboss-service.xml 08:21:35,141 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc. 08:21:35,142 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc. 08:21:35,143 INFO [ServerInfo] OS-System: SunOS 5.10,sparc 08:21:35,153 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms1024m -Xmx2048m -Djava.endorsed.dirs=/opt/app/documentum/share/jboss4.3.0/lib/endorsed 08:21:36,366 INFO [Server] Core system initialized 08:21:45,836 INFO [WebService] Using RMI server codebase: http://appt4-mb2:9083/ 08:21:45,843 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 08:21:47,743 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 08:21:47,744 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 08:21:48,428 INFO [TransactionManagerService] Starting recovery manager 08:21:48,715 INFO [TransactionManagerService] Recovery manager started 08:21:48,716 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 08:21:57,523 INFO [EJB3Deployer] Starting java:comp multiplexer 08:22:08,044 INFO [NativeServerConfig] JBoss Web Services - Native 08:22:08,044 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2_CP06 (build=200905251649) 08:22:13,155 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/ 08:22:15,613 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/ 08:22:16,129 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/ 08:22:17,666 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/ 08:22:19,042 INFO [MailService] Mail Service bound to java:/Mail 08:22:19,431 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar 08:22:19,528 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar 08:22:19,601 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar 08:22:19,680 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar 08:22:19,744 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar 08:22:19,845 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar 08:22:19,871 INFO [QuartzResourceAdapter] start quartz!!! 08:22:20,076 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main 08:22:20,163 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 08:22:20,173 INFO [RAMJobStore] RAMJobStore initialized. 08:22:20,174 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties' 08:22:20,175 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 08:22:20,175 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 08:22:21,726 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 08:22:33,321 INFO
[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)
Yi Sun reopened JENKINS-14026 git plugin doesnt support branch name contains slash (/) jenkins 1.509.1 and jenkins git plugin 1.3.0 this bug is still here... Branch Specifier: patch/tmp20130513/141148-7 console log: git --version git version 1.7.10.2 (Apple Git-33) Fetching upstream changes from origin No candidate revisions ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Finished: FAILURE Change By: Yi Sun (13/May/13 7:25 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17868) In a multi-config project executed on slave nodes test results are not gathered in the general build view
Tom Bujok commented on JENKINS-17868 In a multi-config project executed on slave nodes test results are not gathered in the general build view Guys, come on, I am willing to code it up. Just a small hint, don't want to grep the whole jenkins code to find this tiny piece... A bit more community-friendly approach would be appreciated... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
Martin Ba commented on JENKINS-10468 Build Queue does not show the executor a build is waiting for I re-checked the issue with my updated Jenkins 1.480.3. Still the same. The build queue is showing: whyWaiting for next available executor on /why without any node info. This time, this is a local Jenkins test-instance and not even the actual build server I used originally. List of installed plugins: External Monitor Job Type Plugin LDAP Plugin pam-auth ant Token Macro Plugin javadoc build-name-setter Maven Integration plugin Dashboard View Build Pipeline Plugin Jenkins user build vars plugin Run Condition Plugin conditional-buildstep Jenkins CVS Plug-in Downstream build view Environment Injector Plugin Extended Choice Parameter Plug-In Hudson Groovy builder Jenkins Subversion Plug-in Jenkins Parameterized Trigger plugin Jenkins Multijob plugin Jython Plugin Locale plugin Priority Sorter Role-based Authorization Strategy Jenkins SSH Slaves plugin Jenkins Throttle Concurrent Builds Plug-in Jenkins Translation Assistance plugin Full queue XML: queue item action parameter nameP1/name value/ /parameter /action action cause shortDescriptionStarted by user x/shortDescription userIdx/userId userNamex/userName /cause /action blockedfalse/blocked buildabletrue/buildable id6/id inQueueSince1368438462785/inQueueSince params (StringParameterValue) P1='' /params stuckfalse/stuck task nameSingle3/name urlhttp://localhost:8080/job/Single3//url colorblue/color /task whyWaiting for next available executor on /why buildableStartMilliseconds1368438462894/buildableStartMilliseconds /item /queue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
Martin Ba assigned JENKINS-10468 to Fred G Build Queue does not show the executor a build is waiting for Change By: Martin Ba (13/May/13 9:50 AM) Assignee: MartinBa FredG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I am getting similar errors, but it is not always sidepanel.jelly 07-May-2013 14:56:53 org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/PluginManager/table.jelly:49:41: st:include No signature of method: java.lang.String.header() is applicable for argument types: () values: [] Possible solutions: center(java.lang.Number), center(java.lang.Number), center(java.lang.Number, java.lang.CharSequence), center(java.lang.Number, java.lang.String), every(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) 07-May-2013 14:38:16 org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.514.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include No signature of method: java.lang.String.entry() is applicable for argument types: (java.util.LinkedHashMap, jenkins.model.MasterBuildConfiguration.config$_run_closure1) values: [[title:# of executors, field:numExecutors], ...] Possible solutions: every(), intern(), any(), next(), next(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings edited a comment on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I am getting similar errors, but it is not always sidepanel.jelly 07-May-2013 14:56:53 org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/PluginManager/table.jelly:49:41: st:include No signature of method: java.lang.String.header() is applicable for argument types: () values: [] Possible solutions: center(java.lang.Number), center(java.lang.Number), center(java.lang.Number, java.lang.CharSequence), center(java.lang.Number, java.lang.String), every(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) 07-May-2013 14:38:16 org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.514.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include No signature of method: java.lang.String.entry() is applicable for argument types: (java.util.LinkedHashMap, jenkins.model.MasterBuildConfiguration.config$_run_closure1) values: [[title:# of executors, field:numExecutors], ...] Possible solutions: every(), intern(), any(), next(), next(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger I will try and test later when no builds are occurring This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-17930) Automatic workspace cleanup issues after upgrade to 0.13
Dirk Kuypers created JENKINS-17930 Automatic workspace cleanup issues after upgrade to 0.13 Issue Type: Bug Assignee: vjuranek Components: ws-cleanup Created: 13/May/13 11:13 AM Description: After upgrading the ws-cleanup plugin to 0.13 all my test projects are not cleaning up their workspaces anymore. There was no special flag set, just the default Cleanup workspace as a post build action. This led to a full hard disk over the weekend on our Jenkins server.:-/ OK, now I can see that there are some new flags added which I can use to actively set when the workspace should be cleaned. But this is very tedious to set if you had configured the cleanup-ws plugin for more than 50 projects and if you are now forced to edit all these projects by hand. I would suggest these flags to be true per default. The next thing: when I tick all fields for "Clean when status is" in my browser's job configuration window and save the job config, the configuration is written into the XML of the job, but when reconfiguring the job I do not see these ticks?!? Running the job deletes the workspace now successfully. So my complaints are: I would like to have true as a default for all the "Clean when status is" ticks like it was before Viewing the configuration seems to be broken although the job config XML file is ok Environment: Jenkins 1.513 Project: Jenkins Priority: Major Reporter: Dirk Kuypers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17653) git-plugin cause endless number of builds
Mattias Andersson commented on JENKINS-17653 git-plugin cause endless number of builds I wouldn't mind if you would make the hpi available because I have no jenkins plugin development environment. If so I could probably squeeze in some time to verify the fix on Friday. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17662) Sometime Jenkins could not checkout code from SVN
Chris Z commented on JENKINS-17662 Sometime Jenkins could not checkout code from SVN Hi, have you checked answers for similar issue on SO ? http://stackoverflow.com/questions/12527800/authentification-error-with-svn-in-jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-16810) CLI: java.io.EOFException
Manuel Coenen commented on JENKINS-16810 CLI: java.io.EOFException This issue still exists in Jenkins 1.514 - everything is fine with 1.499. I am currently using AD plugin 1.33. Is there anything in sight that this problem will be fixed? I rely on using the CLI but I would like to upgrade Jenkins as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Adrien CLERC created JENKINS-17931 cvs rlog files in /tmp are not deleted Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 13/May/13 12:34 PM Description: CVS Plugin seems to create one cvsXXXrlog in /tmp for each CVS poll. Unfortunately, those files are never deleted. Is there any solution for that? Environment: GNU/Linux SLES 10 Project: Jenkins Priority: Major Reporter: Adrien CLERC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17884) Support CTest XML format
Gregoire AUJAY updated JENKINS-17884 Support CTest XML format CTest xml output sample Change By: Gregoire AUJAY (13/May/13 1:07 PM) Attachment: Test.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17884) Support CTest XML format
Gregoire AUJAY commented on JENKINS-17884 Support CTest XML format Hello, here is the xslt file I use. It is from rpavlik: https://github.com/rpavlik/jenkins-ctest-plugin/blob/master/ctest-to-junit.xsl I will add a CTest XML output sample. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17932) NullPointerException Processing Custom Tool
Andrzej Krentosz
created JENKINS-17932
NullPointerException Processing Custom Tool
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
xunit
Created:
13/May/13 1:25 PM
Description:
This is probably related to JENKINS-17877. It works with JUnit but not with Custom Tool.
{{xUnit INFO - Starting to record.
xUnit INFO - Processing Custom Tool
ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception
java.lang.NullPointerException
at com.thalesgroup.dtkit.metrics.hudson.api.type.MetricsType.isSkipNoTestFiles(MetricsType.java:80)
at org.jenkinsci.plugins.xunit.XUnitPublisher.getXUnitToolInfoObject(XUnitPublisher.java:211)
at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:182)
at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:119)
at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
at com.cloudbees.plugins.flow.FlowRun$RunnerImpl.post2(FlowRun.java:210)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
at hudson.model.Run.execute(Run.java:1600)
at hudson.model.Run.run(Run.java:1521)
at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:174)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:241)
at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)}}
Project:
Jenkins
Priority:
Major
Reporter:
Andrzej Krentosz
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17932) NullPointerException Processing Custom Tool
Andrzej Krentosz
updated JENKINS-17932
NullPointerException Processing Custom Tool
Change By:
Andrzej Krentosz
(13/May/13 1:26 PM)
Description:
ThisisprobablyrelatedtoJENKINS-17877.ItworkswithJUnitbutnotwithCustomTool.
{{
[xUnit][INFO]-Startingtorecord.[xUnit][INFO]-ProcessingCustomToolERROR:Publisherorg.jenkinsci.plugins.xunit.XUnitPublisherabortedduetoexceptionjava.lang.NullPointerException atcom.thalesgroup.dtkit.metrics.hudson.api.type.MetricsType.isSkipNoTestFiles(MetricsType.java:80) atorg.jenkinsci.plugins.xunit.XUnitPublisher.getXUnitToolInfoObject(XUnitPublisher.java:211) atorg.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:182) atorg.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:119) atorg.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) atcom.cloudbees.plugins.flow.FlowRun$RunnerImpl.post2(FlowRun.java:210) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) athudson.model.Run.execute(Run.java:1600) athudson.model.Run.run(Run.java:1521) atcom.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:174) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:241) athudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Dan Lewis commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows We are running 1.514 and have this issue. It causes tons of stack traces which slows performance. I have filtered out the messages in the logging config which helps. +1 getting it into 1.509.2 because we want to move to LTS but won't until this is fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-15611) Builds launched programmatically via Queue.schedule() fail with error
Roland Gruber commented on JENKINS-15611 Builds launched programmatically via Queue.schedule() fail with error Any news on this one or any workaround? This makes the plugin useless for us because jobs fail even if EnvInject is not enabled for them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17933) Errors in GroovyInitScript can halt startup
Jesse Glick created JENKINS-17933 Errors in GroovyInitScript can halt startup Issue Type: Bug Assignee: Jesse Glick Components: core Created: 13/May/13 1:55 PM Description: A type etc. in init.groovy can halt startup, which seems excessive: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:899) at jenkins.model.Jenkins.init(Jenkins.java:804) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:888) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.reflect.InvocationTargetException 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 hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: groovy.lang.MissingPropertyException: No such property: WhateverClass for class: init at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at init.run(init.groovy:23) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at hudson.init.impl.GroovyInitScript.execute(GroovyInitScript.java:83) at hudson.init.impl.GroovyInitScript.execute(GroovyInitScript.java:78) at hudson.init.impl.GroovyInitScript.init(GroovyInitScript.java:57) ... 13 more Project: Jenkins Labels: groovy startup robustness Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-16633) NullPointerException in build flow plugin if disabled build is part of build flow
Mika Hepoviita
commented on JENKINS-16633
NullPointerException in build flow plugin if disabled build is part of build flow
Poor man's workaround is to use block
ignore(FAILURE) {
build( "this_build_is_disabled" )
}
The limitation is that enabled and failed build job does not fail and terminate Build Flow build like it should.
But this avoids crashing Build Flow plugin to a disabled job.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
lacostej commented on JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) Not really sure what is happening here. The stack trace isn't full either. I will try to reproduce it but I would appreciate some help from users who do reproduce the issue. Are you all in a distributed build scenario ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17880) Not all files are copied.
Dimitry Declercq commented on JENKINS-17880 Not all files are copied. I have the same problem, this is a blocking issue for me as I want to do git operations in downstream projects (commit/push/branching/tagging/..) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17933) Errors in GroovyInitScript can halt startup
SCM/JIRA link daemon resolved JENKINS-17933 as Fixed Errors in GroovyInitScript can halt startup Change By: SCM/JIRA link daemon (13/May/13 2:48 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17933) Errors in GroovyInitScript can halt startup
SCM/JIRA link daemon commented on JENKINS-17933 Errors in GroovyInitScript can halt startup Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/init/impl/GroovyInitScript.java test/src/test/java/hudson/init/impl/GroovyInitScriptTest.java test/src/test/resources/hudson/init/impl/GroovyInitScriptTest/errorsHandled.zip http://jenkins-ci.org/commit/jenkins/688420177afa64deb4adc9b4b92eede221cad884 Log: FIXED JENKINS-17933 Catch errors in init.groovy. Compare: https://github.com/jenkinsci/jenkins/compare/a4bd40d3da82...688420177afa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15304) Drop list broken, does nothing
bcygan commented on JENKINS-15304 Drop list broken, does nothing Same here, running Jenkins 1.510 behind an Apache reverse proxy. The proxied URL/$stapler/bound/6e8ac2e4-2fa3-4326-abff-bac3f3381a4d/render fails with error 404. Doing the same with non-proxied URL/$stapler/bound/6e8ac2e4-2fa3-4326-abff-bac3f3381a4d/render works. Hopefully this information helps to diagnose the culprit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [update-center] (JENKINS-17029) update-center.json seems to be broken
R.J. Lorimer commented on JENKINS-17029 update-center.json seems to be broken Same here: SEVERE: ERROR: Digest mismatch: computed=AN2CENXxCIQlAGGWm2jdT7xWqLs= vs expected=HHGarvNOLe1YgEh8NGiChOuXfhc= in update site default That's from 1.514 running on two separate installs of Ubuntu 12.10. As of yet haven't figured out what is missing to allow this to work. Both boxes have openssl installed FWIW. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [update-center] (JENKINS-17029) update-center.json seems to be broken
R.J. Lorimer updated JENKINS-17029 update-center.json seems to be broken Change By: R.J. Lorimer (13/May/13 3:49 PM) Environment: 1.503,1.504,1.505,1.509,1.510 ,1.514 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17934) Subversion plugin checks out redundant copy of code when using matrix build projects
Kevin Phillips created JENKINS-17934 Subversion plugin checks out redundant copy of code when using matrix build projects Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: subversion Created: 13/May/13 3:52 PM Description: When configuring a multi-configuration project in Jenkins using the SVN plugin, it appears there is a single, redundant copy of the source for the associated job checked out in the root workspace folder, on top of the copies that are checked out for each "axis". For example, suppose you have a single axis configuration (called JENKINS_PLATFORM) with two possible values: win32 and x64. When you execute this job, you will end up with three copies of your source code. The exact folder structures depend on the job configuration, but generally they look something like this: .\MyCodeModule .\JENKINS_PLATFORM\win32\MyCodeModule .\JENKINS_PLATFORM\x64\MyCodeModule (NOTE: .\ is the root workspace folder in these examples). At best, this causes un-necessary bloat and overhead on a build machine, checking out the source three times instead of two. At worse, if you happen to have a sub-folder in your source project that matches exactly one of the subfolder names generated by Jenkins you end up with Subversion checkout errors because a folder of the same name already exists. I exploited this particular problem quite easily with the following configuration: set job to use a custom workspace folder set the "Directory for sub-builds" to $JENKINS_PLATFORM set the Subversion checkout options with the "Local module directory" to "." (ie: the root workspace folder) Doing so will first checkout your code module in the root folder, then subsequently it will attempt to create two subfolders, one called "win32" and one "x64" for each axis in the configuration. If, however, you have a folder called "win32" and / or "x64" in your code module (which we do), you'll end up with a folder clash. Now, to me this seems to indicate one of several possible problems with the Subversion plugin and the matrix build project, including: The code checkout operation should only happen once, one for each of the threads that builds each axis (except, perhaps, in the case when the "Directory for sub-builds" option under the custom workspace configuration is set to "." - which forces all axis configurations to use the same workspace) The "Local module directory" field in the Subversion configuration options should be relative to the "current workspace folder", which should be a result of concatenating (a) the root workspace folder or the custom workspace directory (b) the directory for sub-builds All path properties, including the custom workspace directory, directory for sub-builds, and possibly the local SVN module directory, should respect the axis specific environment variables generated by the matrix runner to allow consistent parameterization of the configuration. Environment: windows 7 x64 Project: Jenkins Priority: Major Reporter: Kevin Phillips This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [subversion] (JENKINS-16865) SVN fail to revert working dir : NullPointerException
Chris Z
commented on JENKINS-16865
SVN fail to revert working dir : NullPointerException
All points to the src/main/java/hudson/scm/subversion/UpdateUpdater.java:
175 } catch (final SVNException e) {
176SVNException cause = e;
and exception is caused probably starting the 151 line:
151 preUpdate(location, local);
152 SVNDepth svnDepth = getSvnDepth(location.getDepthOption());
It seems that SVNException cause = e; is causing null pointer exception which is odd.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17679) Git plugins crashes with exception for jobs using git merging features
Jesse Glick resolved JENKINS-17679 as Duplicate Git plugins crashes with exception for jobs using git merging features Change By: Jesse Glick (13/May/13 4:00 PM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Jesse Glick commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Since https://github.com/jenkinsci/git-plugin/pull/148 has been merged, should this not be set to Resolved? (I know no plugin release containing the fix has yet been made, but it is conventional to mark bugs closed once the fix has been committed to the master branch.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite resolved JENKINS-16941 as Fixed Git publisher post build action fails on slave agent - unable to serialize Agreed with @jglick that since the change has been submitted, this should be resolved. Change By: Mark Waite (13/May/13 4:33 PM) Status: InProgress Resolved Assignee: AdamPAPAI NicolasDeLoof Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17935) NPE from Run.getDynamic
Jesse Glick created JENKINS-17935 NPE from Run.getDynamic Issue Type: Bug Assignee: Jesse Glick Components: core Created: 13/May/13 4:53 PM Description: Observed using terminal and trying to click on the interactiveTerminal link for a completed build prior to refreshing its page: java.lang.NullPointerException hudson.model.Run.getDynamic(Run.java:2123) Project: Jenkins Labels: exception Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mstestrunner] (JENKINS-17937) MSTestRunner issues when the path to the test project contains a space
Jeff Longino created JENKINS-17937 MSTestRunner issues when the path to the test project contains a space Issue Type: Bug Assignee: Unassigned Components: mstestrunner Created: 13/May/13 6:36 PM Description: We have environments where the test projects live in a space embedded path (C:\Program Files\blah) and thus we need to quote the various arguments to MSTest such as /testcontainer: etc. It looks as if adding double quote to any of these arguments then causes confusion and MSTest.exe itself can not be found. Below is sample output of the error. Note in this case we had moved the tests to c:\temp\ to help isolate the cause. Path To MSTest.exe: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\MSTest.exe Result file was not found so no action has been taken. file:/c:/Slave/$civJenkinsCustomWorkspaceRoot/SIT-(POS)(StartupSmokeTests)-RunTest/%22c:/temp/TestProjects/StartupSmokeTests.trx/%22 Executing MSTest: cmd.exe /C "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\MSTest.exe" /resultsfile:\"c:\temp\TestProjects\StartupSmokeTests.trx\" /testcontainer:\"c:\temp\TestProjects\StartupSmokeTests.orderedtest\" exit %%ERRORLEVEL%% SIT-(POS)(StartupSmokeTests)-RunTest $ cmd.exe /C "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\MSTest.exe" /resultsfile:\"c:\temp\TestProjects\StartupSmokeTests.trx\" /testcontainer:\"c:\temp\TestProjects\StartupSmokeTests.orderedtest\" exit %%ERRORLEVEL%% 'C:\Program' is not recognized as an internal or external command, operable program or batch file. Project: Jenkins Priority: Major Reporter: Jeff Longino This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Kohsuke just pushed a release of git-client-plugin 1.0.6 and git-plugin 1.4.0. The git-client-plugin release is already available on the updates site. The git-plugin release should be available soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite edited a comment on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Nicolas just pushed a release of git-client-plugin 1.0.6 and git-plugin 1.4.0. The git-client-plugin release is already available on the updates site. The git-plugin release should be available soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Ken Garland updated JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session Change By: Ken Garland (13/May/13 8:35 PM) Attachment: css_issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17932) NullPointerException Processing Custom Tool
SCM/JIRA link daemon commented on JENKINS-17932 NullPointerException Processing Custom Tool Code changed in jenkins User: Gregory Boissinot Path: pom.xml http://jenkins-ci.org/commit/xunit-plugin/10a79251820ee036686fb1a4ab335f5d4151fb39 Log: Fix JENKINS-17932 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Ken Garland updated JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session Change By: Ken Garland (13/May/13 8:37 PM) Attachment: css_issue.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17884) Support CTest XML format
SCM/JIRA link daemon commented on JENKINS-17884 Support CTest XML format Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/types/CTestInputMetric.java src/main/java/org/jenkinsci/plugins/xunit/types/CTestType.java src/main/resources/org/jenkinsci/plugins/xunit/types/ctest-to-junit.xsl src/test/java/org/jenkinsci/plugins/xunit/types/CTestTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase1/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/ctest/testcase1/result.xml http://jenkins-ci.org/commit/xunit-plugin/c99126460efa9978126ee764afacb2f3d4fbd1a7 Log: Fix JENKINS-17884 Compare: https://github.com/jenkinsci/xunit-plugin/compare/10a79251820e...c99126460efa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17932) NullPointerException Processing Custom Tool
Gregory Boissinot resolved JENKINS-17932 as Fixed NullPointerException Processing Custom Tool Fixed. Sorry for the inconvenience. Change By: Gregory Boissinot (13/May/13 8:44 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17884) Support CTest XML format
Gregory Boissinot resolved JENKINS-17884 as Fixed Support CTest XML format Thanks. Integrated Change By: Gregory Boissinot (13/May/13 8:45 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extensible-choice-parameter] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers
mirumpf commented on JENKINS-17875 Make Jenkins environment variables available to dynamic providers The only chance I see is that an extension to the ParameterDefinition type is introduced where the job context is passed upon instantiation. The ParameterDefinition is instantiated in the context of a job, so that should not be an issue. But overall that would require some change in the Jenkins internal APIs. I think I will stick to manually setting the jobname in the System Groovy List Provider for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17653) git-plugin cause endless number of builds
Mark Waite resolved JENKINS-17653 as Fixed git-plugin cause endless number of builds The git-client-plugin 1.0.6 and git-plugin 1.4.0 should be available from the usual download site soon with those submissions. Change By: Mark Waite (13/May/13 9:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-15611) Builds launched programmatically via Queue.schedule() fail with error
Gregory Boissinot commented on JENKINS-15611 Builds launched programmatically via Queue.schedule() fail with error I'm sorry for my late reply. I don't know why you have this error. Could you test for now with the latest version? Do you have any excpetion stack traces in the Jenkins log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)
Yi Sun edited a comment on JENKINS-14026 git plugin doesnt support branch name contains slash (/) jenkins 1.509.1 and jenkins git plugin 1.3.0 this bug is still here...but can be workaround easily. Branch Specifier: patch/tmp20130513/141148-7 console log: git --version git version 1.7.10.2 (Apple Git-33) Fetching upstream changes from origin No candidate revisions ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Finished: FAILURE BUT if we add leading "origin/" . then it works. Branch Specifier| works or not | master | Y| originmaster| Y| feature/test1 | N| origin/feature/test1| Y| This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)
Yi Sun edited a comment on JENKINS-14026 git plugin doesnt support branch name contains slash (/) jenkins 1.509.1 and jenkins git plugin 1.3.0 this bug is still here...but can be workaround easily. Branch Specifier: patch/tmp20130513/141148-7 console log: git --version git version 1.7.10.2 (Apple Git-33) Fetching upstream changes from origin No candidate revisions ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Finished: FAILURE BUT if we add leading "origin/" . then it works. Branch Specifier| works or not | master | Y| origin/master | Y| feature/test1 | N| origin/feature/test1| Y| This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-14105) Build timeout plugin 1.9 always sets timeout period to 3 minutes
sogabe resolved JENKINS-14105 as Fixed Build timeout plugin 1.9 always sets timeout period to 3 minutes If reproduced, please reopen. Change By: sogabe (14/May/13 2:06 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mantis] (JENKINS-9044) Update all the changesets for one issue
sogabe resolved JENKINS-9044 as Not A Defect Update all the changesets for one issue If reproduced, please reopen. Change By: sogabe (14/May/13 2:08 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sloccount] (JENKINS-17427) sloccount NPE
sogabe resolved JENKINS-17427 as Fixed sloccount NPE If reproduced, please reopen. Change By: sogabe (14/May/13 2:11 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
