[JIRA] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs
Frédéric Camblor closed JENKINS-15969 as Fixed Build Stats Plugin Returns so much data it hangs Ok Don't hesitate to reopen it if you re-face the same problem. I'm worried about it. Change By: Frédéric Camblor (30/Nov/12 8:20 AM) 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
[JIRA] (JENKINS-9650) plugin for global build stats just hangs after clicking on create new chart
Frédéric Camblor commented on JENKINS-9650 plugin for global build stats just hangs after clicking on create new chart Could you please provide more hints ? Like identifying some contention points on the chrome dev tools' network tab. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Yury Pukhalsky commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Jenkins 1.489 here and it happens too. The master and slave are RHEL5.8. The task runs for quite a time, alright. But there is output being spewn and setting neither ClientAliveInterval and ClientAliveCountMax nor TCPKeepAlive helped. It started to happen after i've joined two "execute shell" steps into one, moreso (we run a series of tests) it always happens around the test number, say, N±3 which adds weight to the timeout hypothesis. Probably it's somewhere in the JVM entrails? Now i'll try to play with different JVMs and settings as it's a blocking issue for 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
[JIRA] (JENKINS-9650) plugin for global build stats just hangs after clicking on create new chart
Kamal Mettananda
commented on JENKINS-9650
plugin for global build stats just hangs after clicking on create new chart
Sure Fred.
prototype.js:1585 is pending for so long.
Following is extracted from HAR--
{
"startedDateTime": "2012-11-30T08:29:45.976Z",
"time": -1,
"request": {
"method": "POST",
"url": "http://jenkins-host/plugin/global-build-stats/createChartMap?buildStatId=ID",
"httpVersion": "HTTP/1.1",
"headers": [
{
"name": "Origin",
"value": "http://jenkins-host"
},
{
"name": "X-Prototype-Version",
"value": "1.7"
},
{
"name": "X-Requested-With",
"value": "XMLHttpRequest"
},
{
"name": "User-Agent",
"value": "Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/11.10 Chromium/18.0.1025.168 Chrome/18.0.1025.168 Safari/535.19"
},
{
"name": "Content-type",
"value": "application/x-www-form-urlencoded; charset=UTF-8"
},
{
"name": "Accept",
"value": "text/_javascript_, text/html, application/xml, text/xml, */*"
},
{
"name": "Referer",
"value": "http://jenkins-host/plugin/global-build-stats/"
}
],
"queryString": [
{
"name": "buildStatId",
"value": "ID"
}
],
"cookies": [],
"headersSize": 552,
"bodySize": 0
},
"response": {
"status": 0,
"statusText": "",
"httpVersion": "HTTP/1.1",
"headers": [],
"cookies": [],
"content": {
"size": 0,
"compression": 0
},
"redirectURL": "",
"headersSize": 13,
"bodySize": 0
},
"cache": {},
"timings": {
"blocked": 0,
"dns": -1,
"connect": -1,
"send": -1,
"wait": -1,
"receive": -1,
"ssl": -1
},
"pageref": "page_1"
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15477) Loading All Build History Fails - error 500
Richard Mortimer commented on JENKINS-15477 Loading All Build History Fails - error 500 This issue is fixed in 1.492. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Yury Pukhalsky edited a comment on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Jenkins 1.489 here and it happens too. The master and slave are RHEL5.8. The task runs for 15 minutes in my case. The output is being spewn and setting neither ClientAliveInterval and ClientAliveCountMax nor TCPKeepAlive helped. It started to happen after i've joined two "execute shell" steps into one, moreso (we run a series of tests) it always happens around the test number, say, N±3 which adds weight to the timeout hypothesis. Probably it's somewhere in the JVM entrails? Now i'll try to play with different JVMs and settings as it's a blocking issue for 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
[JIRA] (JENKINS-15986) Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed
Tomas Westling commented on JENKINS-15986 Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed This looks different from the problem we have seen, which is described on the wiki page for the plugin. We have seen an error in loading configuration pages, not saving them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Yury Pukhalsky edited a comment on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Jenkins 1.489 here and it happens too. The master and slave are RHEL5.8. The task runs for 15 minutes in my case. The output is being spewn and setting neither ClientAliveInterval and ClientAliveCountMax nor TCPKeepAlive helped. It started to happen after i've joined two "execute shell" steps into one. The sockets, processes numbers are well within limits The slave appears to exit (crash?). In the slave log there is: ... Evacuated stdout Slave successfully connected and online ERROR: Connection terminated java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException Probably it's somewhere in the JVM entrails? Now i'll try to play with different JVMs and settings as it's a blocking issue for 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
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Mikko Tapaninen commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 Jenkins 1.491 Slave_1 with jdk1.6.0_35: 11:16:25 Build step 'Execute Windows batch command' marked build as failure 11:16:26 11:16:38 Deleting project workspace... done Slave_2 with jdk1.6.0_37 11:16:14 Build step 'Execute Windows batch command' marked build as failure 11:16:15 11:16:15 Deleting project workspace... ERROR: Publisher hudson.plugins.ws_cleanup.WsCleanup aborted due to exception 11:16:15 hudson.util.IOException2: remote file operation failed: e:\build_e\slave_2\workspace\image\ebaa21bd at hudson.remoting.Channel@6db17b38:slave_2 11:16:15 at hudson.FilePath.act(FilePath.java:848) 11:16:15 at hudson.FilePath.act(FilePath.java:825) 11:16:15 at hudson.FilePath.deleteRecursive(FilePath.java:981) 11:16:15 at hudson.plugins.ws_cleanup.WsCleanup.perform(WsCleanup.java:68) 11:16:15 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) 11:16:15 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 11:16:15 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) 11:16:15 at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) 11:16:15 at hudson.model.Run.execute(Run.java:1560) 11:16:15 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 11:16:15 at hudson.model.ResourceController.execute(ResourceController.java:88) 11:16:15 at hudson.model.Executor.run(Executor.java:236) 11:16:15 Caused by: java.io.IOException: Remote call on slave_2 failed 11:16:15 at hudson.remoting.Channel.call(Channel.java:674) 11:16:15 at hudson.FilePath.act(FilePath.java:841) 11:16:15 ... 11 more 11:16:15 Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.util.jna.Kernel32 11:16:15 at hudson.util.jna.Kernel32Utils.getWin32FileAttributes(Kernel32Utils.java:76) 11:16:15 at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:80) 11:16:15 at hudson.Util.isSymlink(Util.java:322) 11:16:15 at hudson.Util.deleteRecursive(Util.java:283) 11:16:15 at hudson.FilePath$11.invoke(FilePath.java:983) 11:16:15 at hudson.FilePath$11.invoke(FilePath.java:981) 11:16:15 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309) 11:16:15 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 11:16:15 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 11:16:15 at hudson.remoting.Request$2.run(Request.java:287) 11:16:15 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 11:16:15 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 11:16:15 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 11:16:15 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 11:16:15 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 11:16:15 at hudson.remoting.Engine$1$1.run(Engine.java:60) 11:16:15 at java.lang.Thread.run(Thread.java:662) 11:16:15 Finished: FAILURE Slaves do have also other differences. Builds where matrix run siblings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15989) Inconsistent display, some warnings are assigned to Default Module
Yves Harms created JENKINS-15989 Inconsistent display, some warnings are assigned to Default Module Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-collector Created: 30/Nov/12 10:06 AM Description: We are using a maven build setup, all modules do have explicit names. The build only collects findbugs, pmd and checkstyle warnings. The checkstyle, PMD and findbugs views shows a correct structure. In the analysis collector view (that aggregates everything) however, a minority of the warnings is spread through the tree with correct module names (1). The majority is assigned to "Default Module". Drilling into "Default module" shows the correct module names as childs. But the warnings assigned to (1) are not shown. Environment: Static Analysis Collector Plug-in 1.27 Static Analysis Utilities 1.4.1 Project: Jenkins Priority: Major Reporter: Yves Harms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Harro Schmidt edited a comment on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 When cleaning the workspace of a project using Jenkins ver. 1.492-SNAPSHOT on Java 6 (jdk1.6.0_22) I get the following error: Nov 29, 2012 11:05:18 AM org.apache.catalina.core.ApplicationContext log SEVERE: Error while serving http://mycisserver/net/jenkins/view/N2/job/myclient/doWipeOutWorkspace java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at
[JIRA] (JENKINS-15990) Support for multiple local_manifest.xml files
Pekka Nikander created JENKINS-15990 Support for multiple local_manifest.xml files Issue Type: New Feature Assignee: Unassigned Components: repo Created: 30/Nov/12 10:45 AM Description: The recent versions of the Android repo tool support multiple local_manifest.xml files, and indeed recommend using multiple files instead of one: https://gerrit.googlesource.com/git-repo/+/master/docs/manifest-format.txt It would be useful to have this feature supported in the Repo plugin. Project: Jenkins Priority: Minor Reporter: Pekka Nikander This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15991) Allow local_manifest.xml to be available through the Config File Provide Plugin
Pekka Nikander created JENKINS-15991 Allow local_manifest.xml to be available through the Config File Provide Plugin Issue Type: New Feature Assignee: Unassigned Components: repo Created: 30/Nov/12 10:48 AM Description: The repo plugin currently allows the local_manifest.xml file to be defined either in-situ, at the plugin, or via an URL. It would be useful if the local_manifest.xml contents were available from files managed by the Config File Provider Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin If implemented, it would also be useful if the contents of any such file were expanded for environment variables while being read. Project: Jenkins Priority: Minor Reporter: Pekka Nikander This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15992) Don't skip jobs when earlier job failed
Ben Golding
created JENKINS-15992
Dont skip jobs when earlier job failed
Issue Type:
Improvement
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
30/Nov/12 11:15 AM
Description:
The user should be able to configure behaviour when a failure occurs. Currently all following jobs are skipped.
In some cases this is the correct behaviour, e.g.:
B depends on A, so if A fails we want to skip B
parallel(
{ build("A"); build("B"); },
{ build("C"); }
)
In other cases we always want to run a job, e.g.:
Always run CLEANUP, even if A, B or C fails
parallel(
{ build("A"); build("B"); },
{ build("C"); }
)
build("CLEANUP");
In general we probably want to pass a parameter to build() indicating whether to run the job.
We may also need a value returned from build() indicating the status of that job.
This may already be possible to some extent with guard..rescue. I need to try some experiments.
Environment:
Jenkins 1.492
Build Flow 0.6
Red Hat Enterprise Linux 6.2 64 bit
Sun Java 1.6.0_20
Project:
Jenkins
Priority:
Major
Reporter:
Ben Golding
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15993) Add an option to send only one message for multi-configuration builds
camico created JENKINS-15993 Add an option to send only one message for multi-configuration builds Issue Type: Improvement Affects Versions: current Assignee: kutzi Components: jabber Created: 30/Nov/12 11:34 AM Description: When building a multi-configuration job with e.g. 10 configurations, the Jabber plugin currently sends 10 messages with the same contents. Project: Jenkins Priority: Major Reporter: camico This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2487) Please wait, getting ready to work takes very long
Herman Meerlo commented on JENKINS-2487 Please wait, getting ready to work takes very long Ok, this is really ridiculous. What on earth is it doing for 45 minutes? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15992) Don't skip jobs when earlier job failed
Ben Golding
updated JENKINS-15992
Dont skip jobs when earlier job failed
Change By:
Ben Golding
(30/Nov/12 12:54 PM)
Description:
Theusershouldbeabletoconfigurebehaviourwhenafailureoccurs.Currentlyallfollowingjobsareskipped.Insomecasesthisisthecorrectbehaviour,e.g.:{code:title=BdependsonA,soifAfailswewanttoskipB}parallel({build(A);build(B);},{build(C);}){code}Inothercaseswealwayswanttorunajob,e.g.:{code:title=AlwaysrunCLEANUP,evenifA,BorCfails}parallel({build(A);build(B);},{build(C);})build(CLEANUP);{code}
Theaboveispossiblewithguard..rescue.{code:title=AlwaysrunAandB,evenifPREPARATIONfails}build(PREPARATION);build(A);build(B);{code}TheaboveisnotpossiblecurrentlyAFAIK.Howtoimplementthefix?Someideasbelow:
Ingeneralweprobablywanttopassaparametertobuild()indicatingwhethertorunthejob.
Wemayalsoneedavaluereturnedfrombuild()indicatingthestatusofthatjob.
Thismayalreadybepossibleto
Alternatively
some
extentwithguard
constructlike{code}ignore{
..
.}{code}Theignorewouldbehaveasifalljobsintheignore-blockweresuccessful:jobsintheparentblockwouldnotbeskipped.oreven{code}ignore{...}
rescue
{
.
Ineed
..}{code}Theignore..rescuewouldhaveastatusequal
to
trysomeexperiments
thestatusofthejobsintherescue-block
.
Inthatcase{code}ignore{...}rescue{}{code}wouldalwaysbesuccessful,canbeusedinthecasenocleanupisneeded.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15886) parameterized builds start default ant target in Ant-Task
Robert Lachner updated JENKINS-15886 parameterized builds start default ant target in Ant-Task Change By: Robert Lachner (30/Nov/12 1:18 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15995) Arguments passed to Managed Script called in Conditional BuildStep could not be saved
Nickolay Rumyantsev created JENKINS-15995 Arguments passed to Managed Script called in Conditional BuildStep could not be saved Issue Type: Bug Affects Versions: current Assignee: domi Components: conditional-buildstep, managed-scripts Created: 30/Nov/12 1:23 PM Description: I have a managed script which accepts two parameters. I have a job where I want to call this script only when the specific condition is met. So I reconfigure that job and hit 'save' and no error occurs. Then I reload webpage and see that the buildstep is saved but its arguments are not. Saving fails both for 'Conditional step (Single)' and for 'Conditional step (Multiple)' Environment: WinXP, Linux Project: Jenkins Priority: Major Reporter: Nickolay Rumyantsev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15886) parameterized builds start default ant target in Ant-Task
Robert Lachner commented on JENKINS-15886 parameterized builds start default ant target in Ant-Task the parameter is set up via "build is parameterized" Option in the Konfiguration the user selects a certain build to copy artefacts from and this build number is stored in BUILD_SELECTOR Variable Later then a copy step copies the artefacts from this build to the workspace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15886) parameterized builds start default ant target in Ant-Task
Robert Lachner updated JENKINS-15886 parameterized builds start default ant target in Ant-Task Change By: Robert Lachner (30/Nov/12 1:26 PM) Attachment: screenshot-2.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15964) All configuration screens are stuck LOADING
Steven Post commented on JENKINS-15964 All configuration screens are stuck LOADING This also occurs in 1.491 on the project configuration, same stacktrace in the logs. The first time this occurred I could get around it by removing the project and creating it again, however the error returned a day after. Upgraded to 1.492, same issue, then found this bug report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15996) Parmeterized Job with file upload failing
Alexander Barthel updated JENKINS-15996 Parmeterized Job with file upload failing Change By: Alexander Barthel (30/Nov/12 1:36 PM) Attachment: SystemInformationJenkins.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15986) Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed
Christopher Orr commented on JENKINS-15986 Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed I've seen this too on our 1.490 installation, and I've seen it reported on the users' mailing list. I didn't notice any problems when loading config pages; only when saving. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15886) parameterized builds start default ant target in Ant-Task
cjo9900 commented on JENKINS-15886 parameterized builds start default ant target in Ant-Task Can you attach the config.xml for the job, and an example of of the build output where this occurs. As looking at the example of the logs(below) I have tested with the copy artifact plugin, I see that the value of BUILD_SELECTOR is added to the ant command. As I am not a ANT user by default, can you see if that extra parameter(s) passed in is causing the command line to be too long and truncated, and therefore the actual targets are are not included in the cmd. Also try running the ant command in the log, in a console session as the jenkins user in the workspace for the job and see if the same occurs. example output Building on master in workspace /home/jenkins/jenkins_dev/test Copied 1 artifact from "asdfgh" build number 2 [test] $ /bin/sh -xe /tmp/hudson5015636101750070796.sh + env + grep BUILD_SELECTOR BUILD_SELECTOR=SpecificBuildSelector plugin="copyartifact@1.25" buildNumber2/buildNumber/SpecificBuildSelector [test] $ /home/jenkins/.jenkins/tools/Ant/1.8.4/bin/ant '-DBUILD_SELECTOR=SpecificBuildSelector plugin="copyartifact@1.25" buildNumber2/buildNumber/SpecificBuildSelector' clean jar Buildfile: /home/jenkins/jenkins_dev/test/build.xml clean: [delete] Deleting directory /home/jenkins/jenkins_dev/test/build compile: [mkdir] Created dir: /home/jenkins/jenkins_dev/test/build/classes [javac] /home/jenkins/jenkins_dev/test/build.xml:19: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 1 source file to /home/jenkins/jenkins_dev/test/build/classes jar: [mkdir] Created dir: /home/jenkins/jenkins_dev/test/build/jar [jar] Building jar: /home/jenkins/jenkins_dev/test/build/jar/HelloWorld.jar BUILD SUCCESSFUL Total time: 3 seconds Finished: 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
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
John Werner commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs More info to help track this down: The issue did not start happening until we upgraded from 1.472 to 1.492. This was done on 27-Nov-2012. Weve been in a we-need-to-get-this-released mode so we have held off on Jenkins and plug-in offsets for a while. When DST expired, we were still running 1.472. I searched the old err.log files and did not find the issue. The machine is a Windows Server 2003, Standard Edition, and Jenkins is running as a service. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11943) NPE when a Plugin Fails to Install if it has a missing dep to another plugin
evernat resolved JENKINS-11943 as Duplicate NPE when a Plugin Fails to Install if it has a missing dep to another plugin Change By: evernat (30/Nov/12 2:23 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Trevor Baker commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 This is a critical issue wreaking havoc on our build system! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10296) Empty emailAddress causes Mailer error.
evernat resolved JENKINS-10296 as Duplicate Empty emailAddress causes Mailer error. Change By: evernat (30/Nov/12 2:37 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9952) Subversion revision not passed along to all downstream jobs
cjo9900 commented on JENKINS-9952 Subversion revision not passed along to all downstream jobs You should be passing the Subversion revision parameter in both jobs A and B. You might also want to check JENKINS-13852 which would allow the svn revisions to be passed from job A to C/D where job B uses a different svn directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15997) Error while Publishing Doxygen HTML results
Miguel Algaba created JENKINS-15997 Error while Publishing Doxygen HTML results Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: doxygen Created: 30/Nov/12 4:22 PM Description: We are running a job in one Ubuntu server 12.04 slave machine with the Doxygen plugin installed. The documentation is generated as part of the build process, and the 'html' folder is filled with all the Doxygen output as expected, however we have encounter a problem while publishing the Doxygen documentation: Publishing Doxygen HTML results. FATAL: error java.lang.IllegalStateException: Can't send a remote FilePath to a different remote channel at hudson.FilePath.writeObject(FilePath.java:1951) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:959) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1480) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at hudson.remoting.UserRequest.perform(UserRequest.java:126) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) 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 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) Build step 'Publish Doxygen' changed build result to FAILURE Thanks! Environment: Ubuntu server 12.04, slave machine Project: Jenkins Priority: Major Reporter: Miguel Algaba This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15997) Error while Publishing Doxygen HTML results
Miguel Algaba closed JENKINS-15997 as Fixed Error while Publishing Doxygen HTML results Change By: Miguel Algaba (30/Nov/12 4:54 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
[JIRA] (JENKINS-13592) Details part of each ccm warning always displays all file
Danny Janssens commented on JENKINS-13592 Details part of each ccm warning always displays all file Same problem here: Windows 7 Jenkins 1.492 CCM plugin 3.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
[JIRA] (JENKINS-15998) builds assigned to wrong job
G. Ann Campbell created JENKINS-15998 builds assigned to wrong job Issue Type: Bug Assignee: vjuranek Components: build-publisher Created: 30/Nov/12 6:22 PM Description: We have jobs with similar names: longishName and longishName_2_3_4 The one without the number at the end is a head build. The with the number is a branch. After upgrading this week from 1.472 to 1.491 and then subsequently downgrading, we found branch builds populated (subdirectories created under builds) into the head job. We could tell at a glance that there was a problem since we use the formatted version number as the build display name. Also, the head build job was on build # 13, but the build history contained builds with numbers in the 40's and 60's - although not everything from 40-70, just a frightening, confusing handful. Project: Jenkins Priority: Critical Reporter: G. Ann Campbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15998) builds copied to wrong job
G. Ann Campbell updated JENKINS-15998 builds copied to wrong job Change By: G. Ann Campbell (30/Nov/12 6:23 PM) Summary: builds assigned copied towrongjob Description: Wehavejobswithsimilarnames:longishNameandlongishName_2_3_4Theonewithoutthenumberattheendisaheadbuild.Thewiththenumberisabranch.Afterupgradingthisweekfrom1.472to1.491andthensubsequentlydowngrading,wefoundbranchbuildspopulated(subdirectoriescreatedunderbuilds)intotheheadjob.Wecouldtellataglancethattherewasaproblemsinceweusetheformattedversionnumberasthebuilddisplayname.Also,theheadbuildjobwasonbuild#13,butthebuildhistorycontainedbuildswithnumbersinthe40sand60s-althoughnoteverythingfrom40-70,justafrightening,confusinghandful. Thecopiedbuildsstillexisted,unmolested,intheiractualparentjobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
Mitch Dempsey commented on JENKINS-15704 Incomplete list of builds when I go to JobName/api/json This is caused by 'hudson.util.RunList' in the function named 'newBuilds()' The .limit call is hard coded to show the last 10 builds. This should probably be a configuration option, or should just show all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
Overmind DL1 commented on JENKINS-15704 Incomplete list of builds when I go to JobName/api/json For note, it is not showing the 'last' 10, it is showing 10 after the last 1. Currently we build the changelog from it (so we want it to show all, not 10), and it is not showing the current one either. Whenever we get the list from jenkins it omits the current one, gets the ten before it, and omits the remainder. We need all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
Overmind DL1 edited a comment on JENKINS-15704 Incomplete list of builds when I go to JobName/api/json For note, it is not showing the 'last' 10, it is showing 10 after the last 1. Currently we build the changelog from it (so we want it to show all, not 10), and it is not showing the current one either. Whenever we get the list from jenkins it omits the current one, gets the ten before it, and omits the remainder. We need all. Back when we ran the version about 5 builds ago (??7) it did show all including the current. It worked properly at that point, hence why this is a regression. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15972) No display available in post build actions
zregvart commented on JENKINS-15972 No display available in post build actions Hi thanks for reporting this. Xvfb plugin is a build wrapper and as such, AFAIK, cannot be called after post build actions, but rather with the build's job start and end. I'll try and see if there is a way to be called when the whole of the job is done - including the post build actions, until then I would advise you to create a freestyle build that includes calling Sonar as one of the job steps not as a post build action. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15957) All build executors permanently Dead!
candrews commented on JENKINS-15957 All build executors permanently Dead! I'm experiencing the same problem using Jenkin 1.492 on Windows 7 x86, Java 1.6.0_26-b03. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
candrews commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs This may be the same as JENKINS-15957 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15957) All build executors permanently Dead!
candrews commented on JENKINS-15957 All build executors permanently Dead! This could be the same as JENKINS-15652 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15999) Flow Jobs Do Not Run Properly When Configured to Run on a Node Other Than Master
Greg horvath created JENKINS-15999 Flow Jobs Do Not Run Properly When Configured to Run on a Node Other Than Master Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow Created: 30/Nov/12 8:25 PM Description: When running a flow job that has been configured to run on an external build node (i.e. anything other than master), it doesn't really run there. I discovered this when I added some steps to my job to copy some build artifacts into the flow job's workspace. The workspace variable was set properly for running on an external build node, but when my post-build publisher ran (specifically, the checkstyle step), it would fail because it couldn't find the files that my job had just copied into the workspace. Additionally, viewing the contents of the workspace via the UI indicated that it was empty. Lastly, I confirmed that the workspace directory on the external build node was in fact empty. After some investigation, I discovered that the files were being copied to the correct directory the directory that it should have been put in on the external build node but on the master node! If I lock down the job to run on the master node, it works fine. The build artifacts are exactly where I expect them to be, and the publisher runs successfully. The workaround works for me in the near term, but it's not a workable long term solution. One of my Jenkins instances could have many instances of this job running in parallel, and I would have to significantly increase the number of executors on my master node to support this, which we have observed to cause instability. Environment: CentOS 6, Jenkins 1.486 Project: Jenkins Priority: Major Reporter: Greg horvath This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15999) Flow Jobs Do Not Run Properly When Configured to Run on a Node Other Than Master
Greg horvath commented on JENKINS-15999 Flow Jobs Do Not Run Properly When Configured to Run on a Node Other Than Master I should also add that when a flow job locked to an external build node runs, all indications are that the job is running on the remote builder (i.e. console output indicates remote builder). Very confusing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer updated JENKINS-12967 Cannot view HTML report for a specific build. This patch fixes it for me. Change By: Carsten Pfeiffer (30/Nov/12 8:59 PM) Attachment: fix.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer edited a comment on JENKINS-12967 Cannot view HTML report for a specific build. I have the same issue with Jenkins 1.488. And it appears to be the same problem as JENKINS-14625. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16000) Color bars do not match actual values
Carsten Pfeiffer created JENKINS-16000 Color bars do not match actual values Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Attachments: somewrongbars.png, wrongbars.png Components: jacoco Created: 30/Nov/12 9:51 PM Description: I'm using version 1.0.9 of the plugin with Jenkins 1.488 and some of the graphical bars do not match the actual values. See for example. In the packages-reports some bars look about right, while some others are again wrong. Project: Jenkins Priority: Minor Reporter: Carsten Pfeiffer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15578) hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
Liam Reimers commented on JENKINS-15578 hudson.security.AccessDeniedException2: anonymous is missing the Administer permission Same setup - LDAP auth and only a few users have admin rights. Same plugin, same error on slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16000) Color bars do not match actual values
Ognjen Bubalo commented on JENKINS-16000 Color bars do not match actual values Hi, The color bars do not represent the percent value. Please check Marc Hoffmann's suggestion: https://groups.google.com/d/topic/jenkins-jacoco-plugin-mailing-list/016MPoIIr2c/discussion (The bars are all red because Missed Covered.) Cheers, Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16001) batch-task
Sud Ramasamy created JENKINS-16001 batch-task Issue Type: New Feature Affects Versions: current Assignee: Kohsuke Kawaguchi Components: batch-task Created: 30/Nov/12 10:50 PM Description: The batch task does not display the user who kicked off the build. This is useful information to know when using shared resources. Environment: all Project: Jenkins Priority: Major Reporter: Sud Ramasamy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16002) JobConfigHistory plugin does not record config changes done through API
Anthony Veckey created JENKINS-16002 JobConfigHistory plugin does not record config changes done through API Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory, plugin Created: 30/Nov/12 11:53 PM Description: When using the API to POST a new config.xml for a job, that action is not recorded in the job history. Due Date: 21/Dec/12 12:00 AM Environment: We are using version 1.11 of the plugin, but looking at the release notes of the releases that came after this, it does not look like this issue was addressed. Project: Jenkins Labels: plugin jobconfighistory Priority: Major Reporter: Anthony Veckey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15957) All build executors permanently Dead!
Bruce Adams commented on JENKINS-15957 All build executors permanently Dead! I looked at JENKINS-15652 (and a few others) before I posted this. That is related to a bad build. I don't have an item.isStuck() message and removing the build history didn't make any difference. It is the executor threads themselves that fail to start. Any idea where I could find an older .war to downgrade to manually? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
sogabe commented on JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException @kurt, You can get from https://ci.jenkins-ci.org/job/jenkins_main_trunk/lastSuccessfulBuild/artifact/war/target/ . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
