[JIRA] [core] (JENKINS-18304) created alias testalias not worked after command alias testalias='echo test' at executor shell window
hiteswar kumar created JENKINS-18304 created alias testalias not worked after command alias testalias=echo test at executor shell window Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Jun/13 6:00 AM Description: ideally below command should work at job execute shell alias testalias='echo test' testalias abc output-test abc but at execute shell window build failed with below error message: /tmp/hudson4340322490463779489.sh: line 13: testalias: command not found Environment: checked on 1.447.2 but at any LTS. Project: Jenkins Priority: Major Reporter: hiteswar kumar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [libvirt-slave] (JENKINS-18305) error 500 on configure screen
Brandon Rochon created JENKINS-18305 error 500 on configure screen Issue Type: Bug Assignee: Philipp Bartsch Components: libvirt-slave Created: 12/Jun/13 6:42 AM Description: Can successfully create a new libvirt slave, but when later returning to the slave's configuration screen, the below error is displayed rendering the config page unusable: Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: file:/home/jenkins/plugins/libvirt-slave/WEB-INF/classes/hudson/plugins/libvirt/VirtualMachineSlave/configure-entries.jelly:20:144: j:forEach Error looking up function 'virDomainSnapshotNum': /usr/lib64/libvirt.so.0.7.5: undefined symbol: virDomainSnapshotNum Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file:/home/jenkins/plugins/libvirt-slave/WEB-INF/classes/hudson/plugins/libvirt/VirtualMachineSlave/configure-entries.jelly:20:144: j:forEach Error looking up function 'virDomainSnapshotNum': /usr/lib64/libvirt.so.0.7.5: undefined symbol: virDomainSnapshotNum 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.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) 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) 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:48) 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.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by:
[JIRA] [adaptiveplugin] (JENKINS-14998) Cannot do si comands from shell or batch file (MKS Integrity CLI)
satya b commented on JENKINS-14998 Cannot do si comands from shell or batch file (MKS Integrity CLI) i too getting same error while connecting mks from jenkins slave machine. i have updated my IntegrityClientSite.rc file in slave machine as per Istvan Baska suggestion. i got same error after updation also. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [libvirt-slave] (JENKINS-18305) error 500 on configure screen
Brandon Rochon commented on JENKINS-18305 error 500 on configure screen My VMs have no snapshots BTW, nor does it even seem possible to take them (I have no virsh create-snapshot command) in my version? So perhaps the plugin is expecting newer APIs... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18306) Variables in body no longer working after plugin update
Pawel Gronkiewicz created JENKINS-18306 Variables in body no longer working after plugin update Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 12/Jun/13 6:48 AM Description: After upgrading plugin to version 2.30.2 from 2.28 variables in email content working - but they work in subject. My subject that is working: CI $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS! Non-working body: h1a href=""$PROJECT_NAME - Build #$BUILD_NUMBER - $BUILD_STATUS/a/h1 After reverting to 2.28 all is working properly. My Jenkins is 1.517 Project: Jenkins Labels: plugin Priority: Major Reporter: Pawel Gronkiewicz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-17955) DownstreamPassCondition mishandles jobs in folders
SCM/JIRA link daemon resolved JENKINS-17955 as Fixed DownstreamPassCondition mishandles jobs in folders Change By: SCM/JIRA link daemon (12/Jun/13 7:48 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-17955) DownstreamPassCondition mishandles jobs in folders
SCM/JIRA link daemon commented on JENKINS-17955 DownstreamPassCondition mishandles jobs in folders Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/promoted_builds/PromotionTrigger.java src/main/java/hudson/plugins/promoted_builds/conditions/DownstreamPassCondition.java http://jenkins-ci.org/commit/promoted-builds-plugin/063a50bfe65e845bd74507507d1b4038a7338dc2 Log: FIXED JENKINS-17955 fix job (full)Name comparison This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-17233) Maven release fails when password contains space
Joachim Kunz commented on JENKINS-17233 Maven release fails when password contains space We have a similar problem with the password. If the password is the character '#' contains. We get the message: "svn: missing argument: --password" The same password without '#' works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ruby] (JENKINS-18308) load script from file instead http form
cforce created JENKINS-18308 load script from file instead http form Issue Type: New Feature Assignee: vivekp Components: ruby, ruby-plugin-runtime, ruby-runtime Created: 12/Jun/13 8:56 AM Description: For bigger scripts its is usefull to manage them in scm instead inside jenkins http form, so it would be very useful to enter apth for the ruby script to execute which is e.somewhere in workspace. Project: Jenkins Priority: Major Reporter: cforce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [twitter] (JENKINS-18302) TwitterException in Auth.jar
Sybren Gjaltema updated JENKINS-18302 TwitterException in Auth.jar Change By: Sybren Gjaltema (12/Jun/13 9:01 AM) Summary: TwitterException inAuth.jar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18306) Variables in body no longer working after plugin update
Alex Earl commented on JENKINS-18306 Variables in body no longer working after plugin update I can't seem to replicate this issue at all. Please attach the build log, job XML file and Jenkins's 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] [email-ext] (JENKINS-18306) Variables in body no longer working after plugin update
Pawel Gronkiewicz
commented on JENKINS-18306
Variables in body no longer working after plugin update
I have digged into log and I think I have a candidate for the problem.
This is whole body used:
h1a href=""$PROJECT_NAME - Build #$BUILD_NUMBER - $BUILD_STATUS/a/h1
h2Recent changes/h2
pre${CHANGES_SINCE_LAST_SUCCESS,reverse=true,showPaths=false,showDependencies=true}/pre
h2Build log/h2
pre${BUILD_LOG,maxLines=9}/pre
In the job log (job is defined to use default body and subject) I have found this line (which appeared only with upgraded plugin):
00:20:42.330 Sending email for trigger: Failure
00:20:42.331 Error evaluating token: Undefined parameter showDependencies in token CHANGES_SINCE_LAST_SUCCESS
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Ralf Rausch
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
${VARNAME}, $VARNAME and ${ENV, var="VARNAME"} works for me, too. Something like this $VARNAME doesn´t work. It is the backslash(es) in front of the $. See comment by Alex Earl on 20/May/13 10:42 PM
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Ralf Rausch
edited a comment on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
${VARNAME}, $VARNAME and ${ENV, var="VARNAME"} works for me, too.
Something like this \$VARNAME doesn´t work. It is the backslash(es) in front of the $. See comment by Alex Earl on 20/May/13 10:42 PM
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Ralf Rausch
edited a comment on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
${VARNAME}, $VARNAME and ${ENV, var="VARNAME"} works for me, too.
Something like this $VARNAME doesn´t work. It is the backslash(es) in front of the $. See comment by Alex Earl on 20/May/13 10:42 PM
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18292) Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path
Danny Beerens updated JENKINS-18292 Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path Change By: Danny Beerens (12/Jun/13 9:36 AM) Summary: TeamConcert plug-in plugin cannotresolveJenkinspathandBuildDefinitionJazzSourceControlpath This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18284) Team Concert plugin doesn't load components as root folders
Danny Beerens updated JENKINS-18284 Team Concert plugin doesnt load components as root folders Change By: Danny Beerens (12/Jun/13 9:38 AM) Summary: TeamConcert plugin doesntloadcomponentsasrootfolders This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [summary_report] (JENKINS-18309) Summary report display is empty on the project page (display ok for a build)
Geoffroy Jabouley created JENKINS-18309 Summary report display is empty on the project page (display ok for a build) Issue Type: Bug Assignee: Unassigned Attachments: result.xml Components: summary_report Created: 12/Jun/13 9:49 AM Description: I have created a simple result.xml file to test the plugin (see attached file). I have configured the plugin according to the user guide (archive artifact then publish xml result). On the job/build_X page, the plugin displays correct information On main the job page, nothing is displayed under "Result of build #X" Environment: Windows 7 64 bits Java 7u21 Jenkins 1.505 Project: Jenkins Labels: plugins jenkins Priority: Major Reporter: Geoffroy Jabouley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [summary_report] (JENKINS-18309) Summary report display is empty on the project page (display ok for a build)
Geoffroy Jabouley updated JENKINS-18309 Summary report display is empty on the project page (display ok for a build) Change By: Geoffroy Jabouley (12/Jun/13 9:52 AM) Attachment: Jenkins_SummaryPlugin_Job_Build_Page_DisplayOK.png Attachment: Jenkins_SummaryPlugin_Job_Main_Page_DisplayKO.png Description: Ihavecreatedasimpleresult.xmlfiletotesttheplugin(seeattachedfile).Ihaveconfiguredthepluginaccordingtotheuserguide(archiveartifactthenpublishxmlresult).-Onthejob/build_Xpage,theplugindisplayscorrectinformation-Onmainthejobpage,nothingisdisplayedunderResultofbuild#X Edit:added2screenshots This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18306) Variables in body no longer working after plugin update
Alex Earl commented on JENKINS-18306 Variables in body no longer working after plugin update Looks like the showDependencies parameter did not make it in the port to the new content token method. I'll try and get a fix in ASAP. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ruby-runtime] (JENKINS-18310) ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Yuu Yamashita
updated JENKINS-18310
ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Change By:
Yuu Yamashita
(12/Jun/13 10:37 AM)
Description:
FromJenkins1.518,ruby-runtime0.10throws{{java.lang.IncompatibleClassChangeError}}onstartup.Ifthishappens,allpluginswhichdependonruby-runtimearealsofailedtostart.{code}Runningfrom:/usr/share/jenkins/jenkins.warJun12,20136:26:15PMwinstone.LoggerlogInternalINFO:BeginningextractionfromwarfileJenkinshomedirectory:/var/lib/jenkinsfoundat:EnvVars.masterEnvVars.get(JENKINS_HOME)Jun12,20136:26:16PMwinstone.LoggerlogInternalINFO:HTTPListenerstarted:port=8081Jun12,20136:26:16PMwinstone.LoggerlogInternalINFO:WinstoneServletEnginev0.9.10running:controlPort=disabledJun12,20136:26:16PMjenkins.InitReactorRunner$1onAttainedINFO:StartedinitializationJun12,20136:26:16PMhudson.ClassicPluginStrategycreatePluginWrapperINFO:Pluginrvm.jpiisdisabledJun12,20136:26:16PMjenkins.InitReactorRunner$1onAttainedINFO:ListedallpluginsJun12,20136:26:16PMruby.RubyRuntimePluginstartINFO:InjectingJRubyintoXStreamjava.lang.IncompatibleClassChangeError:Foundclasscom.kenai.jffi.InvocationBuffer,butinterfacewasexpected atcom.kenai.jaffl.provider.jffi.AsmRuntime.marshal(AsmRuntime.java:169) atorg.jruby.ext.posix.LinuxLibC$jaffl$0.setenv(UnknownSource) atorg.jruby.ext.posix.BaseNativePOSIX.setenv(BaseNativePOSIX.java:221) atorg.jruby.ext.posix.LazyPOSIX.setenv(LazyPOSIX.java:263) atorg.jruby.RubyGlobal$StringOnlyRubyHash.case_aware_op_aset(RubyGlobal.java:176) atorg.jruby.RubyGlobal$CaseInsensitiveStringOnlyRubyHash.op_aset(RubyGlobal.java:87) atorg.jruby.RubyHash$i$2$0$op_aset.call(RubyHash$i$2$0$op_aset.gen:65535) atorg.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:332) atorg.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:203) atorg.jruby.ast.AttrAssignTwoArgNode.interpret(AttrAssignTwoArgNode.java:42) atorg.jruby.ast.NewlineNode.interpret(NewlineNode.java:104) atorg.jruby.ast.BlockNode.interpret(BlockNode.java:71) atorg.jruby.ast.RootNode.interpret(RootNode.java:129) atorg.jruby.evaluator.ASTInterpreter.INTERPRET_ROOT(ASTInterpreter.java:120) atorg.jruby.Ruby.runInterpreter(Ruby.java:720) atorg.jruby.Ruby.runInterpreter(Ruby.java:728) atorg.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:119) atorg.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1231) atorg.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1224) atorg.kohsuke.stapler.jelly.jruby.haml.HamlLanguage.createContainer(HamlLanguage.java:28) atorg.kohsuke.stapler.jelly.jruby.JRubyFacet.init(JRubyFacet.java:71) atruby.RubyRuntimePlugin.registerJRubyFacet(RubyRuntimePlugin.java:39) atruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:30) athudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379) athudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368) athudson.PluginManager$2$1$1.run(PluginManager.java:334) atorg.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) atjenkins.model.Jenkins$7.runTask(Jenkins.java:893) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:722){code}Theentirelogisattachedas
!
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] [ruby-runtime] (JENKINS-18310) ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Yuu Yamashita
created JENKINS-18310
ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Attachments:
jenkins.log
Components:
ruby-runtime
Created:
12/Jun/13 10:35 AM
Description:
From Jenkins 1.518, ruby-runtime 0.10 throws java.lang.IncompatibleClassChangeError on start up. If this happens, all plugins which depend on ruby-runtime are also failed to start.
Running from: /usr/share/jenkins/jenkins.war
Jun 12, 2013 6:26:15 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /var/lib/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
Jun 12, 2013 6:26:16 PM winstone.Logger logInternal
INFO: HTTP Listener started: port=8081
Jun 12, 2013 6:26:16 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
Jun 12, 2013 6:26:16 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Jun 12, 2013 6:26:16 PM hudson.ClassicPluginStrategy createPluginWrapper
INFO: Plugin rvm.jpi is disabled
Jun 12, 2013 6:26:16 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Jun 12, 2013 6:26:16 PM ruby.RubyRuntimePlugin start
INFO: Injecting JRuby into XStream
java.lang.IncompatibleClassChangeError: Found class com.kenai.jffi.InvocationBuffer, but interface was expected
at com.kenai.jaffl.provider.jffi.AsmRuntime.marshal(AsmRuntime.java:169)
at org.jruby.ext.posix.LinuxLibC$jaffl$0.setenv(Unknown Source)
at org.jruby.ext.posix.BaseNativePOSIX.setenv(BaseNativePOSIX.java:221)
at org.jruby.ext.posix.LazyPOSIX.setenv(LazyPOSIX.java:263)
at org.jruby.RubyGlobal$StringOnlyRubyHash.case_aware_op_aset(RubyGlobal.java:176)
at org.jruby.RubyGlobal$CaseInsensitiveStringOnlyRubyHash.op_aset(RubyGlobal.java:87)
at org.jruby.RubyHash$i$2$0$op_aset.call(RubyHash$i$2$0$op_aset.gen:65535)
at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:332)
at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:203)
at org.jruby.ast.AttrAssignTwoArgNode.interpret(AttrAssignTwoArgNode.java:42)
at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
at org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
at org.jruby.ast.RootNode.interpret(RootNode.java:129)
at org.jruby.evaluator.ASTInterpreter.INTERPRET_ROOT(ASTInterpreter.java:120)
at org.jruby.Ruby.runInterpreter(Ruby.java:720)
at org.jruby.Ruby.runInterpreter(Ruby.java:728)
at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:119)
at org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1231)
at org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1224)
at org.kohsuke.stapler.jelly.jruby.haml.HamlLanguage.createContainer(HamlLanguage.java:28)
at org.kohsuke.stapler.jelly.jruby.JRubyFacet.init(JRubyFacet.java:71)
at ruby.RubyRuntimePlugin.registerJRubyFacet(RubyRuntimePlugin.java:39)
at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:30)
at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379)
at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368)
at hudson.PluginManager$2$1$1.run(PluginManager.java:334)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
The entire log is attached as Unable to embed resource: jenkins.log of type text/plain.
Environment:
Linux sid 3.8-1-amd64 #1 SMP Debian 3.8.11-1
[JIRA] [email-ext] (JENKINS-18306) showDependencies not longer works for CHANGES_SINCE_x tokens
Alex Earl updated JENKINS-18306 showDependencies not longer works for CHANGES_SINCE_x tokens Change By: Alex Earl (12/Jun/13 10:40 AM) Summary: Variablesinbodyno showDependenciesnot longer workingafterpluginupdate worksforCHANGES_SINCE_xtokens This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18285) Executor should carry Authentication for better access control
SCM/JIRA link daemon resolved JENKINS-18285 as Fixed Executor should carry Authentication for better access control Change By: SCM/JIRA link daemon (12/Jun/13 10:57 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18285) Executor should carry Authentication for better access control
SCM/JIRA link daemon commented on JENKINS-18285 Executor should carry Authentication for better access control Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/pom.xml core/src/main/java/hudson/ExtensionListView.java core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/Executor.java core/src/main/java/hudson/model/Fingerprint.java core/src/main/java/hudson/model/Node.java core/src/main/java/hudson/model/Run.java core/src/main/java/hudson/model/queue/AbstractQueueTask.java core/src/main/java/hudson/model/queue/AbstractSubTask.java core/src/main/java/hudson/model/queue/MappingWorksheet.java core/src/main/java/hudson/model/queue/QueueTaskFilter.java core/src/main/java/hudson/model/queue/SubTask.java core/src/main/java/hudson/model/queue/Tasks.java core/src/main/java/hudson/security/GlobalSecurityConfiguration.java core/src/main/java/hudson/util/CopyOnWriteList.java core/src/main/java/hudson/util/PersistedList.java core/src/main/java/jenkins/security/ProjectAuthenticator.java core/src/main/java/jenkins/security/ProjectAuthenticatorConfiguration.java core/src/main/java/jenkins/security/ProjectAuthenticatorDescriptor.java core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/jenkins/security/ProjectAuthenticator/config.groovy core/src/main/resources/jenkins/security/ProjectAuthenticatorConfiguration/config.groovy test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/2d09a0e54be7bea3ae8d0f203aa5baac6e062275 Log: FIXED JENKINS-18285 Merge the feature branch Compare: https://github.com/jenkinsci/jenkins/compare/3c01366e0bc5...2d09a0e54be7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18306) showDependencies not longer works for CHANGES_SINCE_x tokens
Alex Earl commented on JENKINS-18306 showDependencies not longer works for CHANGES_SINCE_x tokens Actually, it looks like that parameter never did anything for CHANGES_SINCE_LAST_SUCCESS or CHANGES_SINCE_LAST_FAILURE, it was just ignored. You should be able to remove it and have the same functionality as before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ruby-runtime] (JENKINS-18310) ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Yuu Yamashita edited a comment on JENKINS-18310 ruby-runtime throws java.lang.IncompatibleClassChangeError on start up This problem must be comes from SHA@ 2a1d163. 2a1d1631bd4d3e6d37d82295089d70e229ea0548 is the first bad commit commit 2a1d1631bd4d3e6d37d82295089d70e229ea0548 Author: Jesse Glick jgl...@cloudbees.com Date: Fri May 31 14:36:15 2013 -0400 [FIXED JENKINS-14351] jna-posix → jnr-posix upgrade (opt in). :100644 100644 67fcc38739c5049cb772c3eba064de1df04fc4bf b64e62fa9def0663fbff65956b403540a218e802 M changelog.html :04 04 9c34c4672f0e6d662a76a9e6074fb682015272a6 ad0e83a4a4eb92c14f7d8ab3146236608fe354aa M core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ruby-runtime] (JENKINS-18310) ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Yuu Yamashita commented on JENKINS-18310 ruby-runtime throws java.lang.IncompatibleClassChangeError on start up This problem must be comes from SHA@ 2a1d163 2a1d1631bd4d3e6d37d82295089d70e229ea0548 is the first bad commit commit 2a1d1631bd4d3e6d37d82295089d70e229ea0548 Author: Jesse Glick jgl...@cloudbees.com Date: Fri May 31 14:36:15 2013 -0400 [FIXED JENKINS-14351] jna-posix → jnr-posix upgrade (opt in). :100644 100644 67fcc38739c5049cb772c3eba064de1df04fc4bf b64e62fa9def0663fbff65956b403540a218e802 M changelog.html :04 04 9c34c4672f0e6d662a76a9e6074fb682015272a6 ad0e83a4a4eb92c14f7d8ab3146236608fe354aa M core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18310) ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Yuu Yamashita edited a comment on JENKINS-18310 ruby-runtime throws java.lang.IncompatibleClassChangeError on start up This problem might come from SHA@ 2a1d163. 2a1d1631bd4d3e6d37d82295089d70e229ea0548 is the first bad commit commit 2a1d1631bd4d3e6d37d82295089d70e229ea0548 Author: Jesse Glick jgl...@cloudbees.com Date: Fri May 31 14:36:15 2013 -0400 [FIXED JENKINS-14351] jna-posix → jnr-posix upgrade (opt in). :100644 100644 67fcc38739c5049cb772c3eba064de1df04fc4bf b64e62fa9def0663fbff65956b403540a218e802 M changelog.html :04 04 9c34c4672f0e6d662a76a9e6074fb682015272a6 ad0e83a4a4eb92c14f7d8ab3146236608fe354aa M core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18310) ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Yuu Yamashita updated JENKINS-18310 ruby-runtime throws java.lang.IncompatibleClassChangeError on start up Change By: Yuu Yamashita (12/Jun/13 11:16 AM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime
Björn Peemöller updated JENKINS-18311 Jenkins 1.518 fails to load plugin ruby-runtime Change By: Björn Peemöller (12/Jun/13 11:28 AM) Description: AfterupgradingtoJenkins1.518,myRuby project projects
[JIRA] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime
Björn Peemöller
created JENKINS-18311
Jenkins 1.518 fails to load plugin ruby-runtime
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
ruby-runtime
Created:
12/Jun/13 11:27 AM
Description:
After upgrading to Jenkins 1.518, my Ruby project (using the rvm plugin) are not loaded. The log says:
INFO: Beginning extraction from war file
Jenkins home directory: /var/lib/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
Jun 12, 2013 11:24:38 AM winstone.Logger logInternal
INFO: HTTP Listener started: port=8080
Jun 12, 2013 11:24:38 AM winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
Jun 12, 2013 11:24:39 AM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Jun 12, 2013 11:24:39 AM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Jun 12, 2013 11:24:39 AM ruby.RubyRuntimePlugin start
INFO: Injecting JRuby into XStream
java.lang.IncompatibleClassChangeError: Found class com.kenai.jffi.InvocationBuffer, but interface was expected
at com.kenai.jaffl.provider.jffi.AsmRuntime.marshal(AsmRuntime.java:169)
at org.jruby.ext.posix.LinuxLibC$jaffl$0.setenv(Unknown Source)
at org.jruby.ext.posix.BaseNativePOSIX.setenv(BaseNativePOSIX.java:221)
at org.jruby.ext.posix.LazyPOSIX.setenv(LazyPOSIX.java:263)
at org.jruby.RubyGlobal$StringOnlyRubyHash.case_aware_op_aset(RubyGlobal.java:176)
at org.jruby.RubyGlobal$CaseInsensitiveStringOnlyRubyHash.op_aset(RubyGlobal.java:87)
at org.jruby.RubyHash$i$2$0$op_aset.call(RubyHash$i$2$0$op_aset.gen:65535)
at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:332)
at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:203)
at org.jruby.ast.AttrAssignTwoArgNode.interpret(AttrAssignTwoArgNode.java:42)
at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
at org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
at org.jruby.ast.RootNode.interpret(RootNode.java:129)
at org.jruby.evaluator.ASTInterpreter.INTERPRET_ROOT(ASTInterpreter.java:120)
at org.jruby.Ruby.runInterpreter(Ruby.java:720)
at org.jruby.Ruby.runInterpreter(Ruby.java:728)
at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:119)
at org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1231)
at org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1224)
at org.kohsuke.stapler.jelly.jruby.haml.HamlLanguage.createContainer(HamlLanguage.java:28)
at org.kohsuke.stapler.jelly.jruby.JRubyFacet.init(JRubyFacet.java:71)
at ruby.RubyRuntimePlugin.registerJRubyFacet(RubyRuntimePlugin.java:39)
at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:30)
at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379)
at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368)
at hudson.PluginManager$2$1$1.run(PluginManager.java:334)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Jun 12, 2013 11:24:41 AM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin ruby-runtime
hudson.util.IOException2: Failed to initialize
at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:371)
at hudson.PluginManager$2$1$1.run(PluginManager.java:334)
at
[JIRA] [redmine] (JENKINS-18312) changelog browsing uses the wrong path
uri milman created JENKINS-18312 changelog browsing uses the wrong path Issue Type: Bug Affects Versions: current Assignee: gaooh Components: redmine Created: 12/Jun/13 11:29 AM Description: I'm running the latest plugin agains Redmine 2.3.0. When browsing the changelog, it leads to "repositories/entry/" + projectName + filePath (https://github.com/jenkinsci/redmine-plugin/blob/master/src/main/java/hudson/plugins/redmine/RedmineRepositoryBrowser.java, line 49) However, the format in Redmine is: /redmine/projects/projectName/repository/entry/filePath Same thing with the revision views: In the plugin is "repositories/revision/" + projectName + "/" + changeSet.getRevision() but in Redmine is different. Project: Jenkins Priority: Major Reporter: uri milman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18306) showDependencies does not work for CHANGES_SINCE_x tokens
Alex Earl updated JENKINS-18306 showDependencies does not work for CHANGES_SINCE_x tokens Change By: Alex Earl (12/Jun/13 12:08 PM) Summary: showDependencies does not longerworks work forCHANGES_SINCE_xtokens This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18291) http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb 404 not found
Nicolas Mongrain-Lacombe resolved JENKINS-18291 as Fixed http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb 404 not found Was able to download package today (just now). Change By: Nicolas Mongrain-Lacombe (12/Jun/13 1:16 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15412) Jenkins not working with Java 8
Kohsuke Kawaguchi resolved JENKINS-15412 as Not A Defect Jenkins not working with Java 8 This is a bug in JRE. See https://java.net/jira/browse/MACOSX_PORT-705 Change By: Kohsuke Kawaguchi (12/Jun/13 1:24 PM) Status: Open Resolved Assignee: KohsukeKawaguchi 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] [xfpanel] (JENKINS-16635) NPE in XFPanel XFPanelEntry.getNumberOfFailedBuilds
Joel Huttunen resolved JENKINS-16635 as Fixed NPE in XFPanel XFPanelEntry.getNumberOfFailedBuilds fixed: commit 3684c1f16228be30e9307e95449c0a69d6c61e2b https://github.com/jenkinsci/xfpanel-plugin/commit/3684c1f16228be30e9307e95449c0a69d6c61e2b Change By: Joel Huttunen (12/Jun/13 1:26 PM) Status: Open Resolved Assignee: JulienRENAUT JoelHuttunen 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] [cron_column] (JENKINS-18313) H cron syntax - cannot specify between 10 pm and 6 am
Dave Ohlsson created JENKINS-18313 H cron syntax - cannot specify between 10 pm and 6 am Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cron_column Created: 12/Jun/13 1:30 PM Description: Hi, I would like to specify a job to start once a day, between 10 pm and 6 am. This: H H(22-6) * * * is not accepted: Invalid input: "H H(22-6) * * *": line 1:9: 1 is an invalid value. Must be within 1 and -15 According to an answer I got on the users forum, this syntax should be valid - see http://jenkins-ci.361315.n4.nabble.com/quot-H-quot-cron-syntax-How-to-specify-quot-between-10-pm-and-6-am-quot-tt4669184.html Environment: Linux Project: Jenkins Priority: Major Reporter: Dave Ohlsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xfpanel] (JENKINS-16616) XFPanel update takes long before it reloads
Joel Huttunen resolved JENKINS-16616 as Fixed XFPanel update takes long before it reloads Fixed by olio: https://github.com/jenkinsci/xfpanel-plugin/commit/a8d352abc3e51ce49cc596a4c953149eb8d7ded2 Change By: Joel Huttunen (12/Jun/13 1:30 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] [publish-over-ftp] (JENKINS-16681) Publish Over FTP 1.8 not working with spaces in filename/path of source files
Alex Klein commented on JENKINS-16681 Publish Over FTP 1.8 not working with spaces in filename/path of source files Okay, it should have been obvious but I didn't find it right away: it now works, but one has to change the separator pattern in the advanced options from ", +" to ",+". Otherwise the whitespace is still interpreted as a possibility to split the string into multiple parts. Perhaps the default pattern should be changed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-18093) thinBackup stops if there's no unstable build
Robert Ristroph commented on JENKINS-18093 thinBackup stops if theres no unstable build I have also ran into this issue, my jenkins version is 1.515. It has been recently set up and has jobs that have not failed yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-17544) Promoted Build Plugin shows 404 on promotion log.
Alex Klein commented on JENKINS-17544 Promoted Build Plugin shows 404 on promotion log. I've also run into this problem, very problematic. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
Oleg Nenashev commented on JENKINS-14515 Malformed PATH environment variable on Windows slave (unix syntax used) Hello, I've resolved this issue. Pull request: https://github.com/jenkinsci/customtools-plugin/pull/2 Best regards, Oleg Nenashev RD Engineer, Synopsys Inc. www.synopsys.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
Oleg Nenashev assigned JENKINS-14515 to Oleg Nenashev Malformed PATH environment variable on Windows slave (unix syntax used) Change By: Oleg Nenashev (12/Jun/13 2:00 PM) Assignee: recampbell OlegNenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-17844) 'Tool Home' does not expand environment variables
Oleg Nenashev commented on JENKINS-17844 Tool Home does not expand environment variables Hello, I have resolved this issue. Pull request: https://github.com/jenkinsci/customtools-plugin/pull/2 Best regards, Oleg Nenashev RD Engineer, Synopsys Inc. www.synopsys.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-17844) 'Tool Home' does not expand environment variables
Oleg Nenashev assigned JENKINS-17844 to Oleg Nenashev Tool Home does not expand environment variables Change By: Oleg Nenashev (12/Jun/13 2:02 PM) Assignee: recampbell OlegNenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
Oleg Nenashev started work on JENKINS-14515 Malformed PATH environment variable on Windows slave (unix syntax used) Change By: Oleg Nenashev (12/Jun/13 2:03 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-17844) 'Tool Home' does not expand environment variables
Oleg Nenashev started work on JENKINS-17844 Tool Home does not expand environment variables Change By: Oleg Nenashev (12/Jun/13 2:03 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-18153) Crowd2 Plugin Authenticates user, but does not log user in
Bill Mooney commented on JENKINS-18153 Crowd2 Plugin Authenticates user, but does not log user in I don't know if this is related, but I had similar behavior when I was porting over a hudson site to a new jenkins instance and I didn't have DNS for my new server setup and the authentication cookies were set for a different domain. I verified this by adding the fully qualified server name to my local /etc/hosts file and the authentication worked as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-10524) winstone.ClientSocketException: Failed to write to client
teilo commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client have the issue and we do not use a reverse proxy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-17844) 'Tool Home' does not expand environment variables
Oleg Nenashev edited a comment on JENKINS-17844 Tool Home does not expand environment variables Hello, I have partially resolved this issue. Now installer supports job environment variables (including build parameters) and Slave's properties. BTW, EnvInject's variables aren't supported (TODO) Pull request: https://github.com/jenkinsci/customtools-plugin/pull/2 Best regards, Oleg Nenashev RD Engineer, Synopsys Inc. www.synopsys.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-17844) 'Tool Home' does not expand environment variables
Oleg Nenashev edited a comment on JENKINS-17844 Tool Home does not expand environment variables Hello, I have partially resolved this issue. In my fork custom tools wrapper supports job environment variables (including build parameters) and Slave's properties. BTW, EnvInject's variables aren't supported (TODO) Pull request: https://github.com/jenkinsci/customtools-plugin/pull/2 Best regards, Oleg Nenashev RD Engineer, Synopsys Inc. www.synopsys.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ruby-plugin-runtime] (JENKINS-18314) Possible incompatibility between jffi-1.2.7 and jruby 1.6.5 as shipped with ruby-runtime plugin
steve bussetti created JENKINS-18314 Possible incompatibility between jffi-1.2.7 and jruby 1.6.5 as shipped with ruby-runtime plugin Issue Type: Bug Affects Versions: current Assignee: Jørgen Tjernø Components: ruby-plugin-runtime, ruby-runtime Created: 12/Jun/13 2:52 PM Description: After upgrading to Jenkins 1.518 (from 1.517) last night, the ruby-runtime plugin disappeared from the list of installed plugins. Attempting to reinstall the plugin fails, and results in a stack trace ending with: Caused by: org.jruby.embed.EvalFailedException: java.lang.IncompatibleClassChangeError: Found class com.kenai.jffi.InvocationBuffer, but interface was expected A little googling suggests that this is a backwards incompatibility between jruby and more recent versions jffi. Project: Jenkins Priority: Critical Reporter: steve bussetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-10524) winstone.ClientSocketException: Failed to write to client
Bernard McKeever edited a comment on JENKINS-10524 winstone.ClientSocketException: Failed to write to client I've worked around this by adding Keepalive=On to the ProxyPass line in my VHost configuration. The above hasn't worked. Still seeing this issue. It seems to happen more often in chrome where I've disabled the browser's cache than firefox where I haven't... There seem to be a LOT of _javascript_ files loaded on each page refresh, so this may have something to do with it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18260) 500 Error on configSubmit for Manage Jenkins Screen
Jonathan Zimmerman commented on JENKINS-18260 500 Error on configSubmit for Manage Jenkins Screen This is a duplicate of JENKINS-18268. The root cause is that the alternativeUrl was not being passed during validation of the JiraSite. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-18229) Error in Jira Plugin
Jonathan Zimmerman commented on JENKINS-18229 Error in Jira Plugin This is a duplicate of JENKINS-18268. The root cause is that the alternativeUrl was not being passed during validation of the JiraSite. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18296) Build Issue - plugin dependency could not be resolved
Paige Riley resolved JENKINS-18296 as Not A Defect Build Issue - plugin dependency could not be resolved Not a bug. Use mvn install -s settings.xml instead of mvn clean install when building. Change By: Paige Riley (12/Jun/13 3:38 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-3709) Jira login information should be scrambled in the configuration file
Jonathan Zimmerman started work on JENKINS-3709 Jira login information should be scrambled in the configuration file Change By: Jonathan Zimmerman (12/Jun/13 3:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
hardwickj
edited a comment on JENKINS-10524
winstone.ClientSocketException: Failed to write to client
If it were a matter of too many _javascript_ files being loaded than a lot more users would be having this problem.
If you guys are running Jenkins behind an apache proxy, try just hitting jenkins directly for a day and see what your results are. This might require typing a longer URL and appending :8080 at the end, but definitely worth it for debugging reasons.
All our problems went away once we figured out our apache proxying issue. We initially discovered the discrepancy by running the following curl command against jenkins, first through the apache proxy, and second against jenkins directly:
#!/bin/bash
for i in {1..100}
do
# via proxy
wget --quiet --spider http://build/api/json?pretty=true
if [ $? -ne 0 ]; then
echo "wget failed via proxy"
fi
done
for i in {1..100}
do
# bypassing the proxy
wget --quiet --spider http://jenkins:8080/api/json?pretty=true
if [ $? -ne 0 ]; then
echo "wget failed directly"
fi
done
If you run that and you only see "wget failed via proxy" but nothing directly, then it's your proxy configuration.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-10524) winstone.ClientSocketException: Failed to write to client
hardwickj
commented on JENKINS-10524
winstone.ClientSocketException: Failed to write to client
If it were a matter of too many _javascript_ files being loaded than a lot more users would be having this problem.
If you guys are running Jenkins behind an apache proxy, try just hitting jenkins directly for a day and see what your results are. This might require typing a longer URL and appending :8080 at the end, but definitely worth it for debugging reasons.
All our problems went away once we figured out our apache proxying issue. We initially discovered the discrepancy by running the following curl command against jenkins, first through the apache proxy, and second against jenkins directly:
{{
#!/bin/bash
for i in {1..100}
do
# via proxy
wget --quiet --spider http://build/api/json?pretty=true
if [ $? -ne 0 ]; then
echo "wget failed via proxy"
fi
done
for i in {1..100}
do
bypassing the proxy
wget --quiet --spider http://jenkins:8080/api/json?pretty=true
if [ $? -ne 0 ]; then
echo "wget failed directly"
fi
done
}}
If you run that and you only see "wget failed via proxy" but nothing directly, then it's your proxy configuration.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-10524) winstone.ClientSocketException: Failed to write to client
hardwickj
edited a comment on JENKINS-10524
winstone.ClientSocketException: Failed to write to client
If it were a matter of too many _javascript_ files being loaded than a lot more users would be having this problem.
If you guys are running Jenkins behind an apache proxy, try just hitting jenkins directly for a day and see what your results are. This might require typing a longer URL and appending :8080 at the end, but definitely worth it for debugging reasons.
All our problems went away once we figured out our apache proxying issue. We initially discovered the discrepancy by running the following curl command against jenkins, first through the apache proxy, and second against jenkins directly:
Unable to find source-code formatter for language: bash. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, java#!/bin/bash
for i in {1..100}
do
# via proxy
wget --quiet --spider http://build/api/json?pretty=true
if [ $? -ne 0 ]; then
echo "wget failed via proxy"
fi
done
for i in {1..100}
do
# bypassing the proxy
wget --quiet --spider http://jenkins:8080/api/json?pretty=true
if [ $? -ne 0 ]; then
echo "wget failed directly"
fi
done
If you run that and you only see "wget failed via proxy" but nothing directly, then it's your proxy configuration.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-10524) winstone.ClientSocketException: Failed to write to client
hardwickj
edited a comment on JENKINS-10524
winstone.ClientSocketException: Failed to write to client
If it were a matter of too many _javascript_ files being loaded than a lot more users would be having this problem.
If you guys are running Jenkins behind an apache proxy, try just hitting jenkins directly for a day and see what your results are. This might require typing a longer URL and appending :8080 at the end, but definitely worth it for debugging reasons.
All our problems went away once we figured out our apache proxying issue. We initially discovered the discrepancy by running the following curl command against jenkins, first through the apache proxy, and second against jenkins directly:
#!/bin/bash
for i in {1..100}
do
# via proxy
wget --quiet --spider http://build/api/json?pretty=true
if [ $? -ne 0 ]; then
echo "wget failed via proxy"
fi
done
for i in {1..100}
do
# bypassing the proxy
wget --quiet --spider http://jenkins:8080/api/json?pretty=true
if [ $? -ne 0 ]; then
echo "wget failed directly"
fi
done
If you run that and you only see "wget failed via proxy" but nothing directly, then it's your proxy configuration.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ruby-plugin-runtime] (JENKINS-18314) Possible incompatibility between jffi-1.2.7 and jruby 1.6.5 as shipped with ruby-runtime plugin
steve bussetti commented on JENKINS-18314 Possible incompatibility between jffi-1.2.7 and jruby 1.6.5 as shipped with ruby-runtime plugin To further support this, rolling back to 1.517 completely resolves this issue. ruby-runtime re-appears in the list of installed apps, along with any plugins that depend on it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-18229) Error in Jira Plugin
Jonathan Zimmerman commented on JENKINS-18229 Error in Jira Plugin Though the validation logic needs to be tweaked. The Link URL is a required field but the validation method won't return a validation error if the alternativeUrl is empty or null. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-10524) winstone.ClientSocketException: Failed to write to client
hardwickj commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client My point being, if you use a proxy at all and are having issues, give that a try first. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-18315) Cov-commit-defects fails to find defects when the intermediate directory is a relative path
Dave Bacher created JENKINS-18315 Cov-commit-defects fails to find defects when the intermediate directory is a relative path Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: coverity Created: 12/Jun/13 3:57 PM Description: When I configure a Coverity build with the option for the plugin to perform the Coverity build, analysis and commit AND I configure the intermediate directory to be a relative path (relative to the workspace), the cov-commit-defects step reports that it can not find defects. $ "C:\Program Files\Coverity-6\Prevent\bin\cov-commit-defects" --dir coverity-build --host coverity --port 8080 --stream "My stream trunk" --user jenkins Coverity Defect Commit Client version 6.5.3 on Windows Server 2003, Standard Edition, 32-bit, Service Pack 2 (build 3790) Internal version numbers: 7d3b4ace9c p-davis-push-13307.195 [ERROR] Specified intermediate directory c:/jenkins/coverity-build doesn't contain any usable data One good reason for configuring the intermediate directory relative to the workspace is that it's straightforward for the build_log.txt to be made an artifact of the build (for later examination). Environment: Jenkins 1.517, Coverity plugin 1.2.4 Project: Jenkins Priority: Major Reporter: Dave Bacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18169) Deadlock when running multiple delete
Emil Sit updated JENKINS-18169 Deadlock when running multiple delete We have seen this issue as well. We are using Jenkins 1.510. We are using the Job-DSL-Plugin which I believe will bulk delete jobs. Change By: Emil Sit (12/Jun/13 4:10 PM) Attachment: jenkins-18169-thread-dump-redacted.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-18229) Error in Jira Plugin
Jonathan Zimmerman commented on JENKINS-18229 Error in Jira Plugin I've opened a new issue specifically for the validation logic: JENKINS-18316. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-18316) JiraSite.DescriptorImpl$doValidation does not validate alternativeUrl
Jonathan Zimmerman created JENKINS-18316 JiraSite.DescriptorImpl$doValidation does not validate alternativeUrl Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jira Created: 12/Jun/13 4:11 PM Description: When validating a Jira site the Link URL is not validated. If the field is left blank this will result in a MalformedURLException when the site is validated. Project: Jenkins Priority: Major Reporter: Jonathan Zimmerman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-3709) Jira login information should be scrambled in the configuration file
Jonathan Zimmerman commented on JENKINS-3709 Jira login information should be scrambled in the configuration file I've fixed this issue in my pull request https://github.com/jenkinsci/jira-plugin/pull/27. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-18316) JiraSite.DescriptorImpl$doValidation does not validate alternativeUrl
Jonathan Zimmerman commented on JENKINS-18316 JiraSite.DescriptorImpl$doValidation does not validate alternativeUrl I've fixed this issue in my pull request https://github.com/jenkinsci/jira-plugin/pull/27. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-18317) Coverity - Default Defect Filter selects no defects when non-default component map is associated with a stream in Coverity
Dave Bacher created JENKINS-18317 Coverity - Default Defect Filter selects no defects when non-default component map is associated with a stream in Coverity Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: coverity Created: 12/Jun/13 4:35 PM Description: I have a (non-default) component map associated with my stream in Coverity. After selecting this stream for the build results in the Jenkins build's Post-build Coverity configuration, the default Defect Filter associated with this stream does not select any defects (see build output below). If I open the Defect Filters section, I see that none of the components under Component is among in my stream's component map are selected. In addition, the Select All and Select None buttons have no effect on the component selection. Expected result: when adding a Stream for build results in the Coverity plugin, the default Defect Filter should select all components. In addition, the Select All and Select None buttons should (respectively) select all or unselect all of the components in the component map. $ "C:\Program Files\Coverity-6\Prevent\bin\cov-commit-defects" --dir c:\jenkins\coverity\temp-4525474660219577452.tmp --host dust-coverity64 --port 8080 --stream "IP Manager trunk" --user jenkins Coverity Defect Commit Client version 6.5.3 on Windows Server 2003, Standard Edition, 32-bit, Service Pack 2 (build 3790) Internal version numbers: 7d3b4ace9c p-davis-push-13307.195 Connecting to server dust-coverity64:9090 2013-06-11 21:43:20 UTC - Committing 584 file descriptions... |0--25---50--75-100| 2013-06-11 21:43:27 UTC - Committing 2 source files... |0--25---50--75-100| 2013-06-11 21:43:21 UTC - Calculating 584 cross-reference bundles... |0--25---50--75-100| 2013-06-11 21:43:29 UTC - Committing 584 cross-reference bundles... |0--25---50--75-100| 2013-06-11 21:43:31 UTC - Committing 2978 functions... |0--25---50--75-100| 2013-06-11 21:43:35 UTC - Committing 18 defect occurrences... |0--25---50--75-100| 2013-06-11 21:43:36 UTC - Committing 3 output files... |0--25---50--75-100| New snapshot ID 10020 added. Elapsed time: 00:00:17 [Coverity] deleting intermediate directory [Coverity] Found snapshot IDs [10020] [Coverity] Fetching defects for stream IP Manager trunk [Coverity] Found 17 defects [Coverity] No defects matched all filters. Environment: Jenkins 1.517, Coverity plugin 1.2.4 Project: Jenkins Priority: Major Reporter: Dave Bacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you 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] [core] (JENKINS-18169) Deadlock when running multiple delete
Emil Sit updated JENKINS-18169 Deadlock when running multiple delete Some further debugging with jstack reveals that there is a deadlock caused by the RenameListener in the Parameterized Trigger plugin. (See attached jstack output.) For each doDelete request that comes in, the thread first holds a lock on itself (via synchronized) in the delete method on Project (extends Job). Each job then winds up calling the RenameListener in the ParameterizedTrigger plugin. The RenameListener iterates over all projects, calling getPublishersList which is also synchronized. When delete A and delete B come in at the same time, job A and B are locked, and then B's RenameListener blocks on A and vice versa. It looks like getPublishersList() is synchronized just for safety in initializing the publishers list. A potential fix might be to use AtomicReference instead. Note that any fix would need to be applied to the other lazy initialized fields in Project (getBuildersList or getBuildWrappersList). Change By: Emil Sit (12/Jun/13 4:44 PM) Attachment: jenkins-18169-jstack-deadlock.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ui-changes] (JENKINS-18318) Cannot install any plugin with Chrome
Maksim Selivanov created JENKINS-18318 Cannot install any plugin with Chrome Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Untitled.png, Untitled2.png Components: ui-changes Created: 12/Jun/13 4:45 PM Description: Cannot install any plugin. It worked some time so I have installed some plugins. But at some point it worked no more. When pressing "Install without restart" or "Download now and install after restart" then there is a always same popup appears "Uploading (59%)..." and that is it. It stays always and nothing ends. When I try to refresh page then it is refreshes OK. But plugin is not installed. Tried to reboot, restart also. No help. I tried with "Publish Over SSH Plugin" and other plugins too. See attached image. Tried with latest Firefox and it worked! Thanks! maks Estonia Environment: CentOS release 6.3 (Final) openjdk 7_19 chrome Version 27.0.1453.110 m Project: Jenkins Priority: Major Reporter: Maksim Selivanov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18319) Jenkins 1.509.1 LTS Release running exceptionally slow through the web interface
dlavelle updated JENKINS-18319 Jenkins 1.509.1 LTS Release running exceptionally slow through the web interface Change By: dlavelle (12/Jun/13 4:50 PM) Environment: 4CPUVMonSandyBridgehostswith12GBofRAMand200GBifdisk.OSisUbuntu10.04-4(e.g.uptodate)x64 StoragebackendisHitachiMercury110withHUS110backendsrunningRAID10. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-16084) Exception: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/run/jenkins/war/WEB-INF/lib/jenkins-core-1.493.jar!/lib/layout/layo
dlavelle closed JENKINS-16084 as Fixed Exception: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/run/jenkins/war/WEB-INF/lib/jenkins-core-1.493.jar!/lib/layout/layout.jelly:84:53: j:forEach java.io.EOFException Stacktrace: Change By: dlavelle (12/Jun/13 4:51 PM) Status: Open Closed 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] [matrix-reloaded] (JENKINS-16591) Matrix Reloaded plugin - our case 8520
Klaus Keppler reopened JENKINS-16591 Matrix Reloaded plugin - our case 8520 I reopen this issue because we just reproduced it. We have Jenkins 1.517 here with only a handful plugins. After installing "Matrix Reloaded", no button was available (at this point I thought it doesn't work at all). The button appeared first after having rebuilt a project - since then it's always available. Howver - thanks for that great plugin! It saves us hours of time while waiting for test results. Change By: Klaus Keppler (12/Jun/13 5:10 PM) Resolution: NotADefect 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] [ruby-plugin-runtime] (JENKINS-18314) Possible incompatibility between jffi-1.2.7 and jruby 1.6.5 as shipped with ruby-runtime plugin
Bright Fulton commented on JENKINS-18314 Possible incompatibility between jffi-1.2.7 and jruby 1.6.5 as shipped with ruby-runtime plugin Same experience as steve bussetti here. Upgrading to 1.518 causes the ruby-runtime plugin to fail during initialization with the following exception Jun 12, 2013 11:53:58 AM ruby.RubyRuntimePlugin start INFO: Injecting JRuby into XStream java.lang.IncompatibleClassChangeError: Found class com.kenai.jffi.InvocationBuffer, but interface was expected at com.kenai.jaffl.provider.jffi.AsmRuntime.marshal(AsmRuntime.java:169) at org.jruby.ext.posix.LinuxLibC$jaffl$0.setenv(Unknown Source) at org.jruby.ext.posix.BaseNativePOSIX.setenv(BaseNativePOSIX.java:221) at org.jruby.ext.posix.LazyPOSIX.setenv(LazyPOSIX.java:263) at org.jruby.RubyGlobal$StringOnlyRubyHash.case_aware_op_aset(RubyGlobal.java:176) at org.jruby.RubyGlobal$CaseInsensitiveStringOnlyRubyHash.op_aset(RubyGlobal.java:87) at org.jruby.RubyHash$i$2$0$op_aset.call(RubyHash$i$2$0$op_aset.gen:65535) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:332) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:203) at org.jruby.ast.AttrAssignTwoArgNode.interpret(AttrAssignTwoArgNode.java:42) at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104) at org.jruby.ast.BlockNode.interpret(BlockNode.java:71) at org.jruby.ast.RootNode.interpret(RootNode.java:129) at org.jruby.evaluator.ASTInterpreter.INTERPRET_ROOT(ASTInterpreter.java:120) at org.jruby.Ruby.runInterpreter(Ruby.java:720) at org.jruby.Ruby.runInterpreter(Ruby.java:728) at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:119) at org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1231) at org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1224) at org.kohsuke.stapler.jelly.jruby.haml.HamlLanguage.createContainer(HamlLanguage.java:28) at org.kohsuke.stapler.jelly.jruby.JRubyFacet.init(JRubyFacet.java:71) at ruby.RubyRuntimePlugin.registerJRubyFacet(RubyRuntimePlugin.java:39) at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:30) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368) at hudson.PluginManager$2$1$1.run(PluginManager.java:334) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) This causes dependent plugins to also fail and build configs which reference them to not load. Downgrading to 1.517 fixes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18320) Nested processes aren't killed on win2003R2+
pancake created JENKINS-18320 Nested processes arent killed on win2003R2+ Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Jun/13 5:15 PM Description: Processes nested by a build aren't killed on Windows OSes newer than win2003R2: win2008R2 and win2012. When the same project is run on win2003r2/Linux slaves everything works just fine. Environment: Jenkins ver. 1.509.1. Server: CentOS 6.3 x64, Oracle JRE 1.7.0_04. Still reproduces after switching server to OpenJDK 1.7.0.19.x86_64. Reproduces slaves: - win2008R2 x86_64 (uses Oracle JRE 1.7.0_17 x86_64); - win2012 x86_64 (uses Oracle JRE 1.7.0_17 x86_64). Does not reproduce on slaves; - win2003r2 x86_64 (uses Oracle JRE 1.7.0_10 x86_64); - win2003r2 x86_32 (uses Oracle JRE 1.7.0_06); - Linux slaves. Project: Jenkins Labels: ProcessTreeKiller Priority: Major Reporter: pancake This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [walldisplay] (JENKINS-18321) When using windows batch command as a build step the wall display doesn't show failed test statistics
steven armstrong created JENKINS-18321 When using windows batch command as a build step the wall display doesnt show failed test statistics Issue Type: Bug Affects Versions: current Assignee: Christian Pelster Components: walldisplay Created: 12/Jun/13 5:18 PM Description: If I use the windows batch command as a build step the test statistics aren't displayed on the wallboard. eg (1/100) so 1 test out of 100 failed. If I remove the windows batch command as a build step the statistics are shown. No other build steps cause this issue. I am using the mstest trx plugin to display the tests. I am using Tomcat 7 on windows 2008 R2 Environment: Windows 2008 R2 Project: Jenkins Priority: Major Reporter: steven armstrong This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-18321) When using windows batch command as a build step the wall display doesn't show failed test statistics
steven armstrong updated JENKINS-18321 When using windows batch command as a build step the wall display doesnt show failed test statistics Change By: steven armstrong (12/Jun/13 5:21 PM) Component/s: jenkinswalldisplay Component/s: walldisplay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-18261) Weather icon is not properly displayed in the Latest Builds and JaCoCo Coverage Statistics Grid portlets
Kevin Wimmer closed JENKINS-18261 as Duplicate Weather icon is not properly displayed in the Latest Builds and JaCoCo Coverage Statistics Grid portlets Duplicate of JENKINS-18049 Change By: Kevin Wimmer (12/Jun/13 5:43 PM) Status: Open Closed 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] [perforce] (JENKINS-18322) Update changelog.xml to describe which user forced the build
Thomas Fields created JENKINS-18322 Update changelog.xml to describe which user forced the build Issue Type: Improvement Affects Versions: current Assignee: Rob Petti Components: perforce Created: 12/Jun/13 6:17 PM Description: Hi, If a user forces a build then there's no user entry in the changelog.xml file. Can you add this information so that I can use the build-name setter plugin to display who actually forced the build? Regards, Tom Environment: Jenkins v1.518 Project: Jenkins Priority: Major Reporter: Thomas Fields This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18322) Update changelog.xml to describe which user forced the build
Rob Petti closed JENKINS-18322 as Wont Fix Update changelog.xml to describe which user forced the build Change By: Rob Petti (12/Jun/13 6:35 PM) Status: Open Closed Fix Version/s: current Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18322) Update changelog.xml to describe which user forced the build
Rob Petti commented on JENKINS-18322 Update changelog.xml to describe which user forced the build The user who started the build is never stored in the changelog.xml. It's stored by Jenkins in the build.xml as a UserCause. Storing build causes is outside the scope of the SCM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13091) java.io.StreamCorruptedException: invalid stream header: B055002D
Kohsuke Kawaguchi commented on JENKINS-13091 java.io.StreamCorruptedException: invalid stream header: B055002D The text mode is for 8bit unsafe communication channel (such as telnet), and I'm not sure if this is one. SSH is 8bit safe. But without having access to zOS I don't think we can solve this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [leastload] (JENKINS-18323) Least Load doesn't appear to work for multi-configuration projects
Jerrod Peach created JENKINS-18323 Least Load doesnt appear to work for multi-configuration projects Issue Type: Bug Assignee: Brendan Nolan Attachments: test-load-balancing.xml Components: leastload Created: 12/Jun/13 7:26 PM Description: Least Load doesn't seem to work for multi-configuration projects. I noticed this by creating a job with 10 configurations (5x2) while I had 8 nodes with 2 executors each in my system. All 8 nodes were part of a label called "Main" and the job was assigned to build on the "Main" label. When I triggered the job, 2 of my nodes were completely empty while 4 other nodes were double-loaded. Given my setup, I should have only had 2 double-loaded nodes and no empty nodes. I've attached the XML configuration for my job. If you create a "Main" label with 8 nodes, you should be able to reproduce this behavior. Heck, you should be able to reproduce it like so if you don't want to use my exact setup: Nodes = N Executors per node = E 1 Number of configurations in project = C, where (N) C (E * N) Given Jenkins' normal scheduling algorithm, it's possible you'll need to make C = (E * N) to fill your nodes, then add a node (or subtract configurations) to fit the above formula. Environment: Jenkins 1.509.1 Least Load 1.0.1 Project: Jenkins Labels: leastload Priority: Major Reporter: Jerrod Peach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Daniel Beck
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I understand that. To clarify:
\${ENV, var="VARNAME"} does not work for me (prints '\${ENV, var="VARNAME"}'), but \$VARNAME does work for me (prints 'value').
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-16845) NullPointer in getPreviousBuild
SCM/JIRA link daemon commented on JENKINS-16845 NullPointer in getPreviousBuild Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractBuild.java http://jenkins-ci.org/commit/jenkins/cc26f23ec4f7ba58577c490b35e4c481d0527f49 Log: JENKINS-16845 Properly report the IllegalStateException, rather than throwing an NPE producing the exception message. java.lang.NullPointerException at hudson.model.Run.getFullDisplayName(Run.java:711) at hudson.model.Run.toString(Run.java:706) at java.lang.String.valueOf(Unknown Source) at java.lang.StringBuilder.append(Unknown Source) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:218) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
The reason for that is the environment variables are actually replaced differently (through a mechanism in the Jenkins core, which doesn't support escaping). This replacement of environment variables is done before token macro does it's replacement.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-17614) Jenkins triggers builds on SCM changes although not configured
Ken Raffenetti commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured I find that my build gets triggered over and over by an SCM Change even when the repository has not been updated. I updated Jenkins to 1.518 today and still see this behavior. Git plugin is 1.4.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-18324) allow sorting of scripts
Kerstin Klein created JENKINS-18324 allow sorting of scripts Issue Type: Improvement Assignee: domi Components: config-file-provider, managed-scripts Created: 12/Jun/13 9:02 PM Description: I'd like to sort scripts alphabetically by their title. I'm maintaining ca 30 managed script files. Current sort order is by ID, which is generated hash and is not very intuitive. Project: Jenkins Priority: Major Reporter: Kerstin Klein This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18251) Add support for Do not fail build if archiving returns nothing option of archiveArtifacts publisher
Chris Dore edited a comment on JENKINS-18251 Add support for Do not fail build if archiving returns nothing option of archiveArtifacts publisher During the google hangout session we had, you mentioned that you had some debugging going. Were you using Eclipse? If so, how did you get that working? I found the following, but since we're using gradle and not maven it's not too much help; https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial Can you help fast track me? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-18325) add sort and filter option for files
Kerstin Klein created JENKINS-18325 add sort and filter option for files Issue Type: New Feature Assignee: domi Components: config-file-provider, managed-scripts Created: 12/Jun/13 9:16 PM Description: I'd like to sort managed scripts alphabetically by their name. Default sort order is by ID, which is generated hash and is not very intuitive. I'm maintaining ca 30 managed script files, having them sorted by name would be good. Also, being able to filter to find a specific script would be helpful too. Project: Jenkins Priority: Major Reporter: Kerstin Klein This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-18324) allow sorting of scripts
Kerstin Klein closed JENKINS-18324 as Incomplete allow sorting of scripts please delete. Change By: Kerstin Klein (12/Jun/13 9:18 PM) Status: Open Closed Assignee: domi Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-15464) Matrix-based security -Job cancel privilege not working
Matt Legrand edited a comment on JENKINS-15464 Matrix-based security -Job cancel privilege not working We too are having this issue. The above screen shots capture it well. If 'cancel' is not possible, the checkbox should be removed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-15464) Matrix-based security -Job cancel privilege not working
Matt Legrand commented on JENKINS-15464 Matrix-based security -Job cancel privilege not working We too am having this issue. The above screen shots capture it well. If 'cancel' is not possible, the checkbox should be removed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime
Yuu Yamashita commented on JENKINS-18311 Jenkins 1.518 fails to load plugin ruby-runtime +1 I met same error on Debian sid, and reported as JENKINS-18310. These issues should be merged into one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18310) ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
Yuu Yamashita resolved JENKINS-18310 as Duplicate ruby-runtime throws java.lang.IncompatibleClassChangeError on start up Further information should be reported to JENKINS-18311. Change By: Yuu Yamashita (13/Jun/13 2:22 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18326) MavenSiteArchiver generates incorrect sites for nested submodules
Bernard Leach created JENKINS-18326 MavenSiteArchiver generates incorrect sites for nested submodules Issue Type: Bug Assignee: Unassigned Components: maven Created: 13/Jun/13 3:07 AM Description: Given a project like; . module1 module3 `-- pom.xml `-- pom.xml module2 `-- pom.xml `-- pom.xml When the site goal is run, a maven site link will be generated by the build however the final site structure is flattened to this; . module1 module2 `-- module3 This breaks the links to the nested modules. Project: Jenkins Priority: Major Reporter: Bernard Leach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
