[JIRA] (JENKINS-15601) Main dashboard takes minutes to load in browser
David Resnick updated JENKINS-15601 Main dashboard takes minutes to load in browser Change By: David Resnick (29/Oct/12 5:58 AM) Component/s: project-stats This message is automatically generated by JIRA. 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-13844) Emulate clean checkout by... does not work with 1.7 subversion repositories
SCM/JIRA link daemon commented on JENKINS-13844 Emulate clean checkout by... does not work with 1.7 subversion repositories Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/scm/subversion/UpdateWithCleanUpdater.java http://jenkins-ci.org/commit/subversion-plugin/82377581f16cccaed8c4a90169d7d4c11d3f9845 Log: Merge pull request #22 from forderud/master JENKINS-13844: "Emulate clean checkout by..." does not work with 1.7 subversion repositories Compare: https://github.com/jenkinsci/subversion-plugin/compare/3f18badadf37...82377581f16c This message is automatically generated by JIRA. 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-13859) Emulate clean check out seems to fail after upgrading to v1.4 of subversion plugin
Fredrik Orderud resolved JENKINS-13859 as Duplicate Emulate clean check out seems to fail after upgrading to v1.4 of subversion plugin Seems to be a duplicate of JENKINS-13844, therefore resolving. Change By: Fredrik Orderud (29/Oct/12 7:51 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
[JIRA] (JENKINS-13844) Emulate clean checkout by... does not work with 1.7 subversion repositories
Fredrik Orderud resolved JENKINS-13844 as Fixed Emulate clean checkout by... does not work with 1.7 subversion repositories Unable to reproduce problem anymore after commit of pull request #22. Therefore resolving. Change By: Fredrik Orderud (29/Oct/12 7: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
[JIRA] (JENKINS-13815) scm-sync-configuration raises unexpectedError() loading job configuration in IE8
Alex Dover commented on JENKINS-13815 scm-sync-configuration raises unexpectedError() loading job configuration in IE8 Same still occurs in 0.0.6.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-15637) JIRA: missing component - 'debian-package-builder'
Marat Mavlyutov updated JENKINS-15637 JIRA: missing component - debian-package-builder Change By: Marat Mavlyutov (29/Oct/12 8:52 AM) Labels: plugin Affects Version/s: current This message is automatically generated by JIRA. 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-12473) Subversion option vanishes under Source-Code-Management in project configuration
Joost Geerdink commented on JENKINS-12473 Subversion option vanishes under Source-Code-Management in project configuration And the similar situation here. Also happened after upgrading Jenkins to 1.448. For me all the SCM options vanished but one and now incremental builds happen. And the funny thing is that they succeed while a clean build would fail so my colleagues even committed not knowing the build was actually broken. This message is automatically generated by JIRA. 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-15650) Users with project-level workspace permission cannot view workspaces in matrix builds
Martin Heimlich created JENKINS-15650 Users with project-level workspace permission cannot view workspaces in matrix builds Issue Type: Bug Assignee: Daniel Petisme Components: role-strategy Created: 29/Oct/12 9:47 AM Description: We are using the role-strategy plugin to manage permissions. We encountered a problem on matrix builds with users accessing the workspaces on the individual slaves. All users do have the "Workspace" permission for their projects set. Unfortunately, they can only view the workspace on the master (the main job) but not on the individual slaves. Let me know if you need any futher information. Project: Jenkins Priority: Major Reporter: Martin Heimlich This message is automatically generated by JIRA. 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-15650) Users with project-level workspace permission cannot view workspaces in matrix builds
Martin Heimlich updated JENKINS-15650 Users with project-level workspace permission cannot view workspaces in matrix builds Change By: Martin Heimlich (29/Oct/12 9:49 AM) Environment: role-strategy1.1.2,jenkins1.476 This message is automatically generated by JIRA. 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-10818) Clearcase plugin does not compile on JDK 7
Krzysztof Malinowski reopened JENKINS-10818 Clearcase plugin does not compile on JDK 7 It's not been integrated yet in trunk, awaiting maintainer's acceptance. Change By: Krzysztof Malinowski (29/Oct/12 9:53 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15620) Can't start Emulator with Android SDK 20.0.3
Stefan T closed JENKINS-15620 as Fixed Cant start Emulator with Android SDK 20.0.3 We updated the Plugin again. It said reload failed, but now it works. Change By: Stefan T (29/Oct/12 10:14 AM) Status: Open Closed Assignee: ChristopherOrr 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-14128) Workspaces not getting cleaned upon build completion
vjuranek commented on JENKINS-14128 Workspaces not getting cleaned upon build completion Hi, do I get it right, that matrix sub-job is removed, but on the node is left parent matrix build folder (e.g. with SVN checkout, which does matrix parent)? This message is automatically generated by JIRA. 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-15651) Workaround GitHub connection issues
Julien Carsique created JENKINS-15651 Workaround GitHub connection issues Issue Type: Improvement Assignee: Unassigned Components: github Created: 29/Oct/12 10:53 AM Description: GitHub often has connection issues making the build fails for bad reasons. The workaround we currently apply on https://qa.nuxeo.org/jenkins/job/addons-master/ is to rebuild up to 5 times, using "Retry build after failure", when the regexp ".*GitException: Could not fetch from any repository" matches the logs. Such error could be easier detected by the GitHub plugin and the "retry" workaround being automatically applied. Project: Jenkins Priority: Major Reporter: Julien Carsique This message is automatically generated by JIRA. 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-15217) Wrong vertical scale in coverage report graph
Aleksandr Zhuikov commented on JENKINS-15217 Wrong vertical scale in coverage report graph I think I'm suffering from the same issue. Here is the link https://reference.ci.cloudbees.com/view/gradle/job/1%20-%20snapshot-gradle/lastBuild/jacoco/ You can see that there was "lineCovered" initially, but then it disappears. Line disappeared after I've fixes "classes" folder location, previously it was pointing to 2 locations - main and test classes. This message is automatically generated by JIRA. 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-15177) main project coverage trend graph has wrong y axis
Aleksandr Zhuikov commented on JENKINS-15177 main project coverage trend graph has wrong y axis Same here: https://reference.ci.cloudbees.com/view/gradle/job/1%20-%20snapshot-gradle/ This message is automatically generated by JIRA. 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-13202) Artifact archiving from an ssh slave fails if symlinks are present
Natalia Naumova commented on JENKINS-13202 Artifact archiving from an ssh slave fails if symlinks are present didn't fix the problem. I installed 1.488 that looks like contains the fix - but the artifacts can't be archived all the same. This message is automatically generated by JIRA. 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
David Resnick commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Same exception for me (see below) on 1.487 on Windows. The "invalid directory name" mentioned is a link to an existing directory; the builds in question were created recently (with 1.487). Oct 29, 2012 1:32:30 PM hudson.model.RunMap retrieve WARNING: could not load C:\jenkins\jobs\job\builds\1 hudson.util.IOException2: Invalid directory name C:\jenkins\jobs\job\builds\1 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:332) at hudson.model.Run.init(Run.java:278) at hudson.model.AbstractBuild.init(AbstractBuild.java:182) at hudson.model.Build.init(Build.java:103) at hudson.model.FreeStyleBuild.init(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor103.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1061) at hudson.model.AbstractProject$1.create(AbstractProject.java:275) at hudson.model.AbstractProject$1.create(AbstractProject.java:273) at hudson.model.RunMap.retrieve(RunMap.java:220) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:638) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:601) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:344) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:502) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:355) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:210) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103) at hudson.model.ResultTrend.getPreviousNonAbortedBuild(ResultTrend.java:168) at hudson.model.ResultTrend.getResultTrend(ResultTrend.java:132) at hudson.model.Run.getBuildStatusSummary(Run.java:1739) at hudson.model.Run$DefaultFeedAdapter.getEntryTitle(Run.java:2102) at hudson.model.Run$DefaultFeedAdapter.getEntryTitle(Run.java:2100) at sun.reflect.GeneratedMethodAccessor378.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at
[JIRA] (JENKINS-15450) ask Jenkins to update their plugin for the latest StarTeam SDK 13.0
maximiliano carneiro started work on JENKINS-15450 ask Jenkins to update their plugin for the latest StarTeam SDK 13.0 Change By: maximiliano carneiro (29/Oct/12 12:55 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
[JIRA] (JENKINS-15450) ask Jenkins to update their plugin for the latest StarTeam SDK 13.0
maximiliano carneiro resolved JENKINS-15450 as Fixed ask Jenkins to update their plugin for the latest StarTeam SDK 13.0 “We were using Jenkins as a windows service. It was installed, by the provided installer, on x86 enviroment. When we tried to use Jenkins as a App on JBoss, all in x64, the connection with Starteam worked fine. For now, there's no need to use it as a service and we are going to let it this way, running on JBoss.” Change By: maximiliano carneiro (29/Oct/12 12:55 PM) 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
[JIRA] (JENKINS-12473) Subversion option vanishes under Source-Code-Management in project configuration
Joost Geerdink edited a comment on JENKINS-12473 Subversion option vanishes under Source-Code-Management in project configuration And the similar situation here. Also happened after upgrading Jenkins to 1.448. For me all the SCM options vanished but one and now incremental builds happen. And the funny thing is that they succeed while a clean build would fail so my colleagues even committed not knowing the build was actually broken. Did as Greg Snyder suggested and that worked (but tbh i also updated a few other plugins and disabled some). I did not have to reconfigure though (maybe because Jenkins Job Configuration History Plugin helped?). This message is automatically generated by JIRA. 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-11664) Ability to add additional parameter on manual trigger
wernight edited a comment on JENKINS-11664 Ability to add additional parameter on manual trigger deleted This message is automatically generated by JIRA. 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-15654) Trigger on reason provided so as to change behavior for change-merged
wernight created JENKINS-15654 Trigger on reason provided so as to change behavior for change-merged Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger Created: 29/Oct/12 2:19 PM Description: Goal: Have the same job do deployment and staging by Promoting all successful Change-Merge triggered builds (promotion then does the deployment). Missing Feature: "Trigger on" reason is not provided as parameter. Note: There is no obvious way to distinguish a Patchset Created for a Merge to master Gerrit event. Two jobs are possible and works fine. Can also monitor the repo though and poll which then would have less GERRIT fields. Project: Jenkins Priority: Major Reporter: wernight This message is automatically generated by JIRA. 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-14948) Cannot commit the configuration change
Yury Pukhalsky closed JENKINS-14948 as Wont Fix Cannot commit the configuration change Change By: Yury Pukhalsky (29/Oct/12 3:03 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15656) Java Web Start Slave Agent Terminating Connection on Mountain Lion
Michael Sica created JENKINS-15656 Java Web Start Slave Agent Terminating Connection on Mountain Lion Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 29/Oct/12 3:57 PM Description: I've got a Snow Leopard/Java 7 slave running successfully (along with several Windows slaves), but when I setup a new node on Mountain Lion (separate machine from the Snow Leopard one) the status of the slave agent window just says Terminated. I originally tried using the latest stable version of Java, but after that didn't work I also tried installing the latest preview, but I got the same results. (1.7.0_09 vs 1.7.0_10-ea) Here is the log from Java on the slave: Java Web Start 10.10.2.13 Using JRE version 1.7.0_10-ea-b13 Java HotSpot(TM) 64-Bit Server VM User home directory = /Users/osxsafarislave c: clear console window f: finalize objects on finalization queue g: garbage collect h: display this help message m: print memory usage o: trigger logging p: reload proxy configuration q: hide console r: reload policy configuration s: dump system and deployment properties t: dump thread list v: dump thread stack 0-5: set trace level to n Match: beginTraversal Match: digest selected JREDesc: JREDescversion 1.5+, heap=-1--1, args=null, href="" sel=false, null, null, JREInfo: JREInfo for index 0: platform is: 1.7 product is: 1.7.0_10-ea location is: http://java.sun.com/products/autodl/j2se path is: /Library/Internet Plug-ins/JavaAppletPlugin.plugin/Contents/Home/bin/java args is: null native platform is: Mac OS X, x86_64 [ x86_64, 64bit ] JavaFX runtime is: JavaFX 2.2.4 found at /Library/Internet Plug-ins/JavaAppletPlugin.plugin/Contents/Home/ enabled is: true registered is: true system is: true Match: ignoring maxHeap: -1 Match: ignoring InitHeap: -1 Match: digesting vmargs: null Match: digested vmargs: JVMParameters: isSecure: true, args: Match: JVM args after accumulation: JVMParameters: isSecure: true, args: Match: digest LaunchDesc: null Match: digest properties: -Dhudson.showWindowsServiceInstallLink=true Match: JVM args: JVMParameters: isSecure: false, args: -Dhudson.showWindowsServiceInstallLink=true Match: endTraversal .. Match: JVM args final: -Dhudson.showWindowsServiceInstallLink=true Match: Running JREInfo Versionmatch: 1.7.0.10.ea == 1.7.0.10.ea Match: Running JVM args match the secure subset: have: satisfy want:-Dhudson.showWindowsServiceInstallLink=true Oct 29, 2012 11:34:54 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel channel java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2571) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) at hudson.remoting.Command.readFrom(Command.java:90) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Oct 29, 2012 11:35:04 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel channel java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2571) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) at hudson.remoting.Command.readFrom(Command.java:90) at
[JIRA] (JENKINS-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail
Tim Pizey commented on JENKINS-13341 Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail Problem still present in 1.488. I tried updating to jna-posix-1.0.3.jar ie replacing jna-posix-1.0.1.jar in war/WEB-INF/lib/ but to no effect. Ubuntu 12.0.4 The code is at http://grepcode.com/file/repo1.maven.org/maven2/org.jvnet.hudson.main/hudson-core/1.396/hudson/os/PosixAPI.java jna-posix details here: http://mvnrepository.com/artifact/org.jruby.ext.posix/jna-posix/1.0.3 This occurs during maven site build This message is automatically generated by JIRA. 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-13754) Error when compiling a plugin against jenkins version 1.463
SCM/JIRA link daemon resolved JENKINS-13754 as Fixed Error when compiling a plugin against jenkins version 1.463 Change By: SCM/JIRA link daemon (29/Oct/12 4:41 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15493) Excessive memory usage with large number of request threads
Jesse Glick commented on JENKINS-15493 Excessive memory usage with large number of request threads @chrisgwarp: your problem is unrelated to this issue. See JENKINS-8754 and related issues and try a newer build. This message is automatically generated by JIRA. 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-13202) Artifact archiving from an ssh slave fails if symlinks are present
Jesse Glick commented on JENKINS-13202 Artifact archiving from an ssh slave fails if symlinks are present @nnau: you may be seeing an unrelated problem. Capture thread dumps and file separately with as much information to reproduce as you can muster. This message is automatically generated by JIRA. 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-15486) Documentation is needed for Project GTest Sample TapTestlink for C++ testing
Bruno P. Kinoshita closed JENKINS-15486 as Fixed Documentation is needed for Project GTest Sample TapTestlink for C++ testing Change By: Bruno P. Kinoshita (29/Oct/12 6:04 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15588) TestLink is not getting Updated
Bruno P. Kinoshita started work on JENKINS-15588 TestLink is not getting Updated Change By: Bruno P. Kinoshita (29/Oct/12 6:05 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
[JIRA] (JENKINS-15343) Unable to use Conditional BuildStep Plugin with Testlink Plugin
Bruno P. Kinoshita closed JENKINS-15343 as Fixed Unable to use Conditional BuildStep Plugin with Testlink Plugin Fixed in 3.1.8 Change By: Bruno P. Kinoshita (29/Oct/12 6:05 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15588) TestLink is not getting Updated
Bruno P. Kinoshita commented on JENKINS-15588 TestLink is not getting Updated Hi, could you elaborate a bit more, I couldn't understand what is the issue here. This message is automatically generated by JIRA. 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-13754) Error when compiling a plugin against jenkins version 1.463
dogfood commented on JENKINS-13754 Error when compiling a plugin against jenkins version 1.463 Integrated in jenkins_main_trunk #2041 FIXED JENKINS-13754 (Revision abeebce2230c37c1ad6bd6b5d5af615859980568) Result = SUCCESS kohsuke : abeebce2230c37c1ad6bd6b5d5af615859980568 Files : core/pom.xml maven-plugin/pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15657) Getting failed to connect when using latest Jenkins CLI
James Murray created JENKINS-15657 Getting failed to connect when using latest Jenkins CLI Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli Created: 29/Oct/12 8:43 PM Description: Hi, I have recently upgraded to Java Version 7 Update 9 (on Windows 7) and am now getting a permission denied error from the jenkins-cli.jar. I can access the URL below fine in a web browser so is not DNS/firewall/authentication. Any thoughts on what could be causing this? Thanks, James. C:\Dev\Wave\Integration\WaveKickStart\WaveKickStart\bin\Releasejava -jar jenkin s-cli.jar -s http://lonsb03.wecomm.local:8080/ help Exception in thread "main" java.io.IOException: Failed to connect to http://lons b03.wecomm.local:8080/ at hudson.cli.CLI.getCliTcpPort(CLI.java:227) at hudson.cli.CLI.init(CLI.java:123) at hudson.cli.CLI.init(CLI.java:107) at hudson.cli.CLI._main(CLI.java:395) at hudson.cli.CLI.main(CLI.java:330) Caused by: java.net.SocketException: Permission denied: connect at java.net.DualStackPlainSocketImpl.connect0(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.init(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Sour ce) at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) at hudson.cli.CLI.getCliTcpPort(CLI.java:225) ... 4 more C:\Dev\Wave\Integration\WaveKickStart\WaveKickStart\bin\Releasejava -jar jenkin s-cli.jar -s http://lonsb03.wecomm.local:8080/ help Exception in thread "main" java.io.IOException: Failed to connect to http://lons b03.wecomm.local:8080/ at hudson.cli.CLI.getCliTcpPort(CLI.java:227) at hudson.cli.CLI.init(CLI.java:123) at hudson.cli.CLI.init(CLI.java:107) at hudson.cli.CLI._main(CLI.java:395) at hudson.cli.CLI.main(CLI.java:330) Caused by: java.net.SocketException: Permission denied: connect at java.net.DualStackPlainSocketImpl.connect0(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.init(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Sour ce) at
[JIRA] (JENKINS-15657) Getting failed to connect when using latest Jenkins CLI
James Murray updated JENKINS-15657 Getting failed to connect when using latest Jenkins CLI Change By: James Murray (29/Oct/12 8:45 PM) Description: Hi,IhaverecentlyupgradedtoJavaVersion7Update9(onWindows7)andamnowgettingapermissiondeniederrorfromthejenkins-cli.jar.IcanaccesstheURLbelowfineinawebbrowsersoisnotDNS/firewall/authentication.Anythoughtsonwhatcouldbecausingthis?Thanks,James.C:\Dev\Wave\Integration\WaveKickStart\WaveKickStart\bin\Releasejava-jarjenkins-cli.jar-shttp://lonsb03.wecomm.local:8080/ help get-jobWave_Expo_Prod_iPhone1 iPhone_job_details.xml Exceptioninthreadmainjava.io.IOException:Failedtoconnecttohttp://lonsb03.wecomm.local:8080/athudson.cli.CLI.getCliTcpPort(CLI.java: 227 266 )athudson.cli.CLI.init(CLI.java: 123 129 )athudson.cli. CLI CLIConnectionFactory . init connect ( CLI CLIConnectionFactory .java: 107 68 ) athudson.cli.CLI._main(CLI.java: 395 439 )athudson.cli.CLI.main(CLI.java: 330 374 )Causedby:java.net.SocketException:Permissiondenied:connectatjava.net.DualStackPlainSocketImpl.connect0(NativeMethod)atjava.net.DualStackPlainSocketImpl.socketConnect(UnknownSource)atjava.net.AbstractPlainSocketImpl.doConnect(UnknownSource)atjava.net.AbstractPlainSocketImpl.connectToAddress(UnknownSource)atjava.net.AbstractPlainSocketImpl.connect(UnknownSource)atjava.net.PlainSocketImpl.connect(UnknownSource)atjava.net.SocksSocketImpl.connect(UnknownSource)atjava.net.Socket.connect(UnknownSource)atjava.net.Socket.connect(UnknownSource)atsun.net.NetworkClient.doConnect(UnknownSource)atsun.net.www.http.HttpClient.openServer(UnknownSource)atsun.net.www.http.HttpClient.openServer(UnknownSource)atsun.net.www.http.HttpClient.init(UnknownSource)atsun.net.www.http.HttpClient.New(UnknownSource)atsun.net.www.http.HttpClient.New(UnknownSource)atsun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(UnknownSource)atsun.net.www.protocol.http.HttpURLConnection.plainConnect(UnknownSource)atsun.net.www.protocol.http.HttpURLConnection.connect(UnknownSource)athudson.cli.CLI.getCliTcpPort(CLI.java: 225 264 )...4more C:\Dev\Wave\Integration\WaveKickStart\WaveKickStart\bin\Releasejava-jarjenkin s-cli.jar-shttp://lonsb03.wecomm.local:8080/ help get-jobWave_Expo_Prod_Java1Ja va_job_details.xml Exceptioninthreadmainjava.io.IOException:Failedtoconnecttohttp://lons b03.wecomm.local:8080/ athudson.cli.CLI.getCliTcpPort(CLI.java: 227 266 ) athudson.cli.CLI.init(CLI.java: 123 129 ) athudson.cli. CLI CLIConnectionFactory . init connect ( CLI CLIConnectionFactory .java: 107 68 )athudson.cli.CLI._main(CLI.java: 395 439 ) athudson.cli.CLI.main(CLI.java: 330 374 ) Causedby:java.net.SocketException:Permissiondenied:connect atjava.net.DualStackPlainSocketImpl.connect0(NativeMethod) atjava.net.DualStackPlainSocketImpl.socketConnect(UnknownSource) atjava.net.AbstractPlainSocketImpl.doConnect(UnknownSource) atjava.net.AbstractPlainSocketImpl.connectToAddress(UnknownSource) atjava.net.AbstractPlainSocketImpl.connect(UnknownSource) atjava.net.PlainSocketImpl.connect(UnknownSource) atjava.net.SocksSocketImpl.connect(UnknownSource) atjava.net.Socket.connect(UnknownSource) atjava.net.Socket.connect(UnknownSource) atsun.net.NetworkClient.doConnect(UnknownSource) atsun.net.www.http.HttpClient.openServer(UnknownSource) atsun.net.www.http.HttpClient.openServer(UnknownSource) atsun.net.www.http.HttpClient.init(UnknownSource) atsun.net.www.http.HttpClient.New(UnknownSource) atsun.net.www.http.HttpClient.New(UnknownSource) atsun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) atsun.net.www.protocol.http.HttpURLConnection.plainConnect(UnknownSour ce) atsun.net.www.protocol.http.HttpURLConnection.connect(UnknownSource) athudson.cli.CLI.getCliTcpPort(CLI.java: 225 264 ) ...4more Permalink C:\Dev\Wave\Integration\WaveKickStart\WaveKickStart\bin\Releaseechobuild_get_c Reply omplete1lock_wait_build_get_complete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see:
[JIRA] (JENKINS-5584) Automatically add -Djava.awt.headless=true on Mac?
Joshua Tharp commented on JENKINS-5584 Automatically add -Djava.awt.headless=true on Mac? I was able to work around this issue by adding the -Djava.awt.headless=true to the JVM Options of the Launch Method section of the build slave 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
[JIRA] (JENKINS-5584) Automatically add -Djava.awt.headless=true on Mac?
Joshua Tharp edited a comment on JENKINS-5584 Automatically add -Djava.awt.headless=true on Mac? I was able to work around this issue by adding the -Djava.awt.headless=true to the JVM Options of the (Advanced) Launch Method section of the build slave 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
[JIRA] (JENKINS-15658) EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable
Jim Searle created JENKINS-15658 EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 29/Oct/12 11:01 PM Description: In my jenkins configuration for "Global properties", I have a property TEST_WORKSPACE defined as ${WORKSPACE}. Then in my jenkins job I have "prepare an environment for the run" defined to a file which does not set TEST_WORKSPACE or WORKSPACE. But, when I run the job, TEST_WORKSPACE is not defined in console, I get this: EnvInject - Loading node environment variables. EnvInject - Preparing an environment for the build. EnvInject - Keeping Jenkins system variables. EnvInject - Keeping Jenkins build variables. EnvInject - Adding build parameters as variables. EnvInject - Injecting as environment variables the properties file path '/home/jims/global.prop' EnvInject - Variables injected successfully. EnvInject - Injecting contributions. Building on master in workspace /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace workspace $ /bin/sh -x /tmp/hudson3013573853871224155.sh + echo 'WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace' WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace + echo 'TEST_WORKSPACE = ' TEST_WORKSPACE = Notifying upstream projects of job completion Finished: SUCCESS If I revert back to envinject 1.36, then it is defined and I see this in the console: EnvInject - Preparing an environment for the job. EnvInject - Keep Jenkins system variables. EnvInject - Keep Jenkins build variables. EnvInject - Injecting as environment variables the properties file path '/home/jims/global.prop' EnvInject - Variables injected successfully. EnvInject - Unset unresolved 'TEST_WORKSPACE' variable. Building on master in workspace /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace workspace $ /bin/sh -x /tmp/hudson3503397345619621354.sh + echo 'WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace' WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace + echo 'TEST_WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace' TEST_WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace Notifying upstream projects of job completion Finished: SUCCESS Environment: Linux lc-irv-1231 2.6.9-89.0.9.ELsmp #1 SMP Wed Aug 19 08:06:10 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Jenkins 1.486 envinject 1.72 Project: Jenkins Priority: Major Reporter: Jim Searle This message is automatically generated by JIRA. 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-10569) When installing plugins with overlapping dependencies, Jenkins downloads the duplicate plugins multiple times
evernat assigned JENKINS-10569 to evernat When installing plugins with overlapping dependencies, Jenkins downloads the duplicate plugins multiple times Change By: evernat (29/Oct/12 11:06 PM) Assignee: evernat This message is automatically generated by JIRA. 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-10569) When installing plugins with overlapping dependencies, Jenkins downloads the duplicate plugins multiple times
evernat commented on JENKINS-10569 When installing plugins with overlapping dependencies, Jenkins downloads the duplicate plugins multiple times I have submitted a pull request: https://github.com/jenkinsci/jenkins/pull/598 This message is automatically generated by JIRA. 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-15656) Java Web Start Slave Agent Terminating Connection on Mountain Lion
Szilard P commented on JENKINS-15656 Java Web Start Slave Agent Terminating Connection on Mountain Lion I'm having the same issue after updating from 1.486 to 1.487 on Mac OS X Lion (10.7) with an pretty old 1.6.0_29 Java. This message is automatically generated by JIRA. 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-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
SCM/JIRA link daemon commented on JENKINS-15540 Update logging levels in LogRotator - hudson.tasks.LogRotator perform Code changed in jenkins User: Olivier Lamy Path: core/src/main/java/hudson/tasks/LogRotator.java http://jenkins-ci.org/commit/jenkins/88503bce4971814455481df1bba13f5d9d987b4e Log: Merge pull request #592 from wwade/master FIXED JENKINS-15540 Update logging levels in LogRotator Compare: https://github.com/jenkinsci/jenkins/compare/fcbc0c683e1b...88503bce4971 This message is automatically generated by JIRA. 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-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
SCM/JIRA link daemon resolved JENKINS-15540 as Fixed Update logging levels in LogRotator - hudson.tasks.LogRotator perform Change By: SCM/JIRA link daemon (30/Oct/12 3:34 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
[JIRA] (JENKINS-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
SCM/JIRA link daemon commented on JENKINS-15540 Update logging levels in LogRotator - hudson.tasks.LogRotator perform Code changed in jenkins User: Wade Carpenter Path: core/src/main/java/hudson/tasks/LogRotator.java http://jenkins-ci.org/commit/jenkins/3ae859402002320394829bcdbddf6408a45d0610 Log: FIXED JENKINS-15540 Update logging levels in LogRotator 1. Log all removals as FINE instead of FINER. 2. Log artifact removes as FINE. Affects: hudson.tasks.LogRotator perform() This message is automatically generated by JIRA. 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-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
SCM/JIRA link daemon commented on JENKINS-15540 Update logging levels in LogRotator - hudson.tasks.LogRotator perform Code changed in jenkins User: Olivier Lamy Path: changelog.html http://jenkins-ci.org/commit/jenkins/ff3cf5e1047fff9f0106a1372b9a460b6f08ecd9 Log: JENKINS-15540 add changelog entry This message is automatically generated by JIRA. 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-15659) Cannot “Disable” an external job
Jesse Glick created JENKINS-15659 Cannot “Disable” an external job Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Oct/12 3:58 AM Description: If you create an external job project, the Delete link works (after the usual confirmation) but the Disable button just gives a 404. Project: Jenkins Labels: external Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15659) Cannot “Disable” an external job
Jesse Glick updated JENKINS-15659 Cannot “Disable” an external job Change By: Jesse Glick (30/Oct/12 4:06 AM) Labels: external Component/s: external-monitor-job 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
[JIRA] (JENKINS-1392) Extension of Monitor an external job jobs.
Jesse Glick updated JENKINS-1392 Extension of Monitor an external job jobs. Change By: Jesse Glick (30/Oct/12 4:09 AM) Component/s: external-monitor-job 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
[JIRA] (JENKINS-1677) External job will not be executed of connection to Hudson can't be obtained.
Jesse Glick updated JENKINS-1677 External job will not be executed of connection to Hudson cant be obtained. Change By: Jesse Glick (30/Oct/12 4:10 AM) Component/s: external-monitor-job Component/s: other This message is automatically generated by JIRA. 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-330) External jobs should not fail if server is down
Jesse Glick updated JENKINS-330 External jobs should not fail if server is down Change By: Jesse Glick (30/Oct/12 4:11 AM) Component/s: external-monitor-job 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
[JIRA] (JENKINS-13824) Jenkins can't monitor external job if master has no executor set
Jesse Glick updated JENKINS-13824 Jenkins cant monitor external job if master has no executor set Change By: Jesse Glick (30/Oct/12 4:13 AM) Component/s: external-monitor-job 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
[JIRA] (JENKINS-14107) Unable to monitor external job in 1.470 (IllegalAccessError)
Jesse Glick updated JENKINS-14107 Unable to monitor external job in 1.470 (IllegalAccessError) Change By: Jesse Glick (30/Oct/12 4:12 AM) Component/s: external-monitor-job 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
[JIRA] (JENKINS-7961) Monitoring external jobs doesn't work with CSRF protection enabled.
Jesse Glick updated JENKINS-7961 Monitoring external jobs doesnt work with CSRF protection enabled. Change By: Jesse Glick (30/Oct/12 4:12 AM) Component/s: external-monitor-job 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
[JIRA] (JENKINS-15487) External monitoring job exception java.lang.NoSuchMethodError: hudson.model.RunMap.put
Jesse Glick updated JENKINS-15487 External monitoring job exception java.lang.NoSuchMethodError: hudson.model.RunMap.put Change By: Jesse Glick (30/Oct/12 4:15 AM) Labels: externalmonitoring Component/s: external-monitor-job Component/s: monitoring This message is automatically generated by JIRA. 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-9414) ERROR for LDAP-Users and GROUPS at external-jobs
Jesse Glick updated JENKINS-9414 ERROR for LDAP-Users and GROUPS at external-jobs Change By: Jesse Glick (30/Oct/12 4:14 AM) Component/s: external-monitor-job 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
[JIRA] (JENKINS-6871) Allow external job monitoring with instant-messaging plugins
Jesse Glick updated JENKINS-6871 Allow external job monitoring with instant-messaging plugins Change By: Jesse Glick (30/Oct/12 4:13 AM) Component/s: external-monitor-job This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12503) Jenkins monitoring external job causes HTTP 500 error, stack trace from jenkins-core-*.jar
Jesse Glick resolved JENKINS-12503 as Duplicate Jenkins monitoring external job causes HTTP 500 error, stack trace from jenkins-core-*.jar Change By: Jesse Glick (30/Oct/12 4:17 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
[JIRA] (JENKINS-12503) Jenkins monitoring external job causes HTTP 500 error, stack trace from jenkins-core-*.jar
Jesse Glick updated JENKINS-12503 Jenkins monitoring external job causes HTTP 500 error, stack trace from jenkins-core-*.jar Change By: Jesse Glick (30/Oct/12 4:16 AM) Component/s: external-monitor-job 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
[JIRA] (JENKINS-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
dogfood commented on JENKINS-15540 Update logging levels in LogRotator - hudson.tasks.LogRotator perform Integrated in jenkins_main_trunk #2042 FIXED JENKINS-15540 Update logging levels in LogRotator (Revision 3ae859402002320394829bcdbddf6408a45d0610) JENKINS-15540 add changelog entry (Revision ff3cf5e1047fff9f0106a1372b9a460b6f08ecd9) Result = SUCCESS wcarpenter : 3ae859402002320394829bcdbddf6408a45d0610 Files : core/src/main/java/hudson/tasks/LogRotator.java Olivier Lamy : ff3cf5e1047fff9f0106a1372b9a460b6f08ecd9 Files : changelog.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-15653) Filter changes by viewspec
Rob Petti commented on JENKINS-15653 Filter changes by viewspec The plugin already only shows the changesets that contain files that are in the currently defined workspace/view map. So #1, (and by extension #3,) is already implemented... The file listing for each changeset is provided by perforce itself, and the 'p4 describe' command used does not have the ability to filter that file listing. As you say, ideally perforce would do this filtering for you, but I don't believe there is such a command for doing that... Please let me know if I'm wrong. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira