date:20140730















































Tom FENNELLY
 created  JENKINS-24030


Modernize tabBar and bigtable















Issue Type:


Improvement



Assignee:


Tom FENNELLY



Components:


core



Created:


30/Jul/14 8:21 AM



Project:


Jenkins



Labels:


user-experience




Priority:


Major



Reporter:


Tom FENNELLY

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout















































Daniel Beck
 commented on  JENKINS-23146


StringIndexOutOfBoundsException on subversion checkout















Fabrice Robin: Just a heads up, the current fix attempt fails to compute the changelog when the folder being checked out is changed (e.g. its properties; original comment). I haven't had the time to fix this yet.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24032) Crash while restart when Jenkins isn't installed as a Windows service

2014-07-30 Thread feeblehams...@gmail.com (JIRA)















































Artem Krosheninnikov
 created  JENKINS-24032


Crash while restart when Jenkins isnt installed as a Windows service















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


30/Jul/14 8:51 AM



Description:


Right now our Jenkins installation is launched as "java -j jenkins.war" but not as a windows service (As it was before). It showed that an update is available, I've pressed "upgrade automatically" and it loaded a new version. In /manage it showed "Upgrade to Jenkins 1.574 is complete, awaiting restart." where restart is a link to restart. After pressing it an error occurred:

javax.servlet.ServletException: hudson.lifecycle.RestartNotSupportedException: Default Windows lifecycle does not support restart.
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	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.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
	at org.eclipse.jetty.server.Server.handle(Server.java:370)
	at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
	at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)
	at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021)
	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
	at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
	at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused

[JIRA] [matrix-reloaded] (JENKINS-24009) Incorrect result status after Matrix rebuild (our case 11639 )

2014-07-30 Thread jbrej...@praqma.net (JIRA)















































Jens  Brejner
 updated  JENKINS-24009


Incorrect result status after Matrix rebuild (our case 11639 )
















Change By:


Jens  Brejner
(30/Jul/14 9:13 AM)




Summary:


IncorrectresultstatusafterMatrixrebuild
(ourcase11639)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-19465) OSX Slave hangs while being launched















































Jan Hudec
 commented on  JENKINS-19465


OSX Slave hangs while being launched















For me in case of such problem it always worked to mark the slave offline, which gives up the current connection attempt and then try to connect it.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [scriptler] (JENKINS-24033) Allow to define parameters already when creating a script

2014-07-30 Thread sschube...@gmail.com (JIRA)















































Sebastian Schuberth
 created  JENKINS-24033


Allow to define parameters already when creating a script















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Dominik Bartholdi



Components:


scriptler



Created:


30/Jul/14 9:27 AM



Description:


When creating a new script with the web UI, please already allow to define parameters there. Currently, one has to first create the script without parameters, then edit the script to add parameters.




Project:


Jenkins



Priority:


Major



Reporter:


Sebastian Schuberth

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [scriptler] (JENKINS-24034) Clarify meaning of Id and Name fields

2014-07-30 Thread sschube...@gmail.com (JIRA)















































Sebastian Schuberth
 created  JENKINS-24034


Clarify meaning of Id and Name fields















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Dominik Bartholdi



Components:


scriptler



Created:


30/Jul/14 9:30 AM



Description:


As a new user, when creating a script via the web UI for the first time, it's quite unclear what the "Id" and "Name" fields are about. If seems "Id" is supposed to be the file name, and "Name" the name as displayed to the user. Please add according descriptions below those two fields.




Project:


Jenkins



Priority:


Major



Reporter:


Sebastian Schuberth

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map] (JENKINS-23734) (our case 11569 )Memory map plugin does not allow to enter absolute or relative path

2014-07-30 Thread jbrej...@praqma.net (JIRA)















































Jens  Brejner
 updated  JENKINS-23734


(our case 11569 )Memory map plugin does not allow to enter absolute or relative path
















Change By:


Jens  Brejner
(30/Jul/14 9:32 AM)




Summary:


(ourcase11569)
Memorymapplugindoesnotallowtoenterabsoluteorrelativepath



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ftppublisher] (JENKINS-24035) Publish over FTP plugin throws exception while uploading to goDaddy

2014-07-30 Thread rak...@indsp.com (JIRA)















































Rakesh Prasad
 created  JENKINS-24035


Publish over FTP plugin throws exception while uploading to goDaddy















Issue Type:


Bug



Affects Versions:


current



Assignee:


benjaminjaton



Components:


ftppublisher



Created:


30/Jul/14 9:48 AM



Description:


Authentication works, directories can be created, but while uploading files, it suddenly throws an exception as follows, and disconnects. Retry also fails always. I'm trying to upload to godaddy ftp site. I can do with FileZilla without problems, so its not about filenames or permissions. 


ERROR: Failed to upload files
java.net.SocketException: Software caused connection abort: socket write error
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(Unknown Source)
	at java.net.SocketOutputStream.write(Unknown Source)
	at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
	at java.io.BufferedOutputStream.flush(Unknown Source)
	at org.apache.commons.net.telnet.TelnetClient._flushOutputStream(TelnetClient.java:77)
	at org.apache.commons.net.telnet.TelnetOutputStream.flush(TelnetOutputStream.java:137)
	at java.io.FilterOutputStream.flush(Unknown Source)
	at sun.nio.cs.StreamEncoder.implFlush(Unknown Source)
	at sun.nio.cs.StreamEncoder.flush(Unknown Source)
	at java.io.OutputStreamWriter.flush(Unknown Source)
	at java.io.BufferedWriter.flush(Unknown Source)
	at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:442)
	at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:520)
	at org.apache.commons.net.ftp.FTP.port(FTP.java:849)
	at org.apache.commons.net.ftp.FTPClient.openDataConnection(FTPClient.java:477)
	at org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:388)
	at org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1388)
	at com.zanox.hudson.plugins.FTPSite.upload(FTPSite.java:358)
	at com.zanox.hudson.plugins.EntryCopier.copyFile(EntryCopier.java:87)
	at com.zanox.hudson.plugins.EntryCopier.copy(EntryCopier.java:77)
	at com.zanox.hudson.plugins.FTPPublisher.perform(FTPPublisher.java:179)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685)
	at hudson.model.Run.execute(Run.java:1757)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:234)




Environment:


Windows 7, Java JDK 1.7, Jenkins 1.574, Publish over FTP 1.11, goDaddy ftp




Project:


Jenkins



Labels:


plugin
jenkins
exception




Priority:


Blocker



Reporter:


Rakesh Prasad

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit

[JIRA] [github-sqs] (JENKINS-24036) github sqs plugin: SQS Endpoint needs to be set for regions other than us-east-1

2014-07-30 Thread jo...@inodes.org (JIRA)















































John Ferlito
 created  JENKINS-24036


github sqs plugin: SQS Endpoint needs to be set for regions other than us-east-1















Issue Type:


Bug



Assignee:


Unassigned


Components:


github-sqs



Created:


30/Jul/14 10:08 AM



Description:


I was trying to talk to a queue out side of us-east-1 and needed to set the endpoint to get it working.

I've created a pull request at https://github.com/jenkinsci/github-sqs-plugin/pull/3




Project:


Jenkins



Priority:


Major



Reporter:


John Ferlito

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace

2014-07-30 Thread iwbb....@gmail.com (JIRA)















































Craig Phillips
 created  JENKINS-24037


CPPCheck Plugin: You need worspace message instead of workspace















Issue Type:


Bug



Assignee:


Gregory Boissinot



Components:


cppcheck



Created:


30/Jul/14 10:09 AM



Description:


The message output when a user is not logged in says "worspace" instead of "worKspace".  




Project:


Jenkins



Priority:


Trivial



Reporter:


Craig Phillips

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-16109) Slave hung archiving artifacts















































Jan Hudec
 commented on  JENKINS-16109


Slave hung archiving artifacts















I am not sure it is the same cause, but I've got such hang. There is nothing in the job itself, but the system log has some relevant logs. The first seems to be:

{{
VII 30, 2014 3:25:23 DOP. INFO hudson.model.Run
Navigation-Proposed-Updates » iPhone #28 main build action completed: SUCCESS
VII 30, 2014 3:25:26 DOP. SEVERE hudson.remoting.Channel
Failed to execute command Pipe.EOF(10) (channel macos-builder)
java.lang.NullPointerException
	at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177)
	at hudson.remoting.Channel$2.handle(Channel.java:461)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)

VII 30, 2014 3:25:26 DOP. SEVERE hudson.remoting.Channel
This command is created here
Command Pipe.EOF(10) created at
	at hudson.remoting.Command.init(Command.java:67)
	at hudson.remoting.Command.init(Command.java:50)
	at hudson.remoting.ProxyWriter$EOF.init(ProxyWriter.java:169)
	at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124)
	at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132)
	at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
	at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101)
	at java.lang.ref.Finalizer.access$100(Finalizer.java:32)
	at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190)
}}

Then some logs that are not related to the slave in question until

{{
VII 30, 2014 3:50:25 DOP. INFO hudson.slaves.ChannelPinger
Ping failed. Terminating the channel.
java.util.concurrent.TimeoutException: Ping started on 1406684785389 hasn't completed at 1406685025407
	at hudson.remoting.PingThread.ping(PingThread.java:120)
	at hudson.remoting.PingThread.run(PingThread.java:81)
}}

which is then followed by several instances of

{{
VII 30, 2014 4:12:30 DOP. WARNING hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor
Failed to monitor macos-builder for Response Time
hudson.remoting.ChannelClosedException: channel is already closed
	at hudson.remoting.Channel.send(Channel.java:524)
	at hudson.remoting.Request.callAsync(Request.java:208)
	at hudson.remoting.Channel.callAsync(Channel.java:749)
	at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76)
	at hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:57)
	at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:280)
Caused by: java.io.IOException
	at hudson.remoting.Channel.close(Channel.java:1003)
	at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110)
	at hudson.remoting.PingThread.ping(PingThread.java:120)
	at hudson.remoting.PingThread.run(PingThread.java:81)
Caused by: java.util.concurrent.TimeoutException: Ping started on 1406684785389 hasn't completed at 1406685025407
	... 2 more
}}

with different X in "for X" in the first line and then

{{
VII 30, 2014 8:12:31 DOP. WARNING hudson.node_monitors.ResponseTimeMonitor
Making macos-builder offline because it’s not responding
VII 30, 2014 8:13:23 DOP. INFO hudson.slaves.RetentionStrategy$Demand
Launching computer macos-builder as it has been in demand for 9 hr 8 min
}}

after which the slave never came back up. There were however these two errors:

{{
VII 30, 2014 9:14:32 DOP. WARNING hudson.ExpressionFactory2$JexlExpression
Caught exception evaluating: it.oSDescription in /jenkins/computer/macos-builder/systemInfo. Reason: java.lang.reflect.InvocationTargetException
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.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
	at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
	at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
	at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
	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

[JIRA] [core] (JENKINS-19465) OSX Slave hangs while being launched













































 
Jan Hudec
 edited a comment on  JENKINS-19465


OSX Slave hangs while being launched
















For me in case of such problem it always worked to mark the slave offline, which gives up the current connection attempt and then try to connect it.

Except, well, not this time.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-16109) Slave hung archiving artifacts













































 
Jan Hudec
 edited a comment on  JENKINS-16109


Slave hung archiving artifacts
















I am not sure it is the same cause, but I've got such hang. There is nothing in the job itself, but the system log has some relevant logs. The first seems to be:


VII 30, 2014 3:25:23 DOP. INFO hudson.model.Run
Navigation-Proposed-Updates » iPhone #28 main build action completed: SUCCESS
VII 30, 2014 3:25:26 DOP. SEVERE hudson.remoting.Channel
Failed to execute command Pipe.EOF(10) (channel macos-builder)
java.lang.NullPointerException
	at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177)
	at hudson.remoting.Channel$2.handle(Channel.java:461)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)

VII 30, 2014 3:25:26 DOP. SEVERE hudson.remoting.Channel
This command is created here
Command Pipe.EOF(10) created at
	at hudson.remoting.Command.init(Command.java:67)
	at hudson.remoting.Command.init(Command.java:50)
	at hudson.remoting.ProxyWriter$EOF.init(ProxyWriter.java:169)
	at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124)
	at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132)
	at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
	at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101)
	at java.lang.ref.Finalizer.access$100(Finalizer.java:32)
	at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190)



Then some logs that are not related to the slave in question until


VII 30, 2014 3:50:25 DOP. INFO hudson.slaves.ChannelPinger
Ping failed. Terminating the channel.
java.util.concurrent.TimeoutException: Ping started on 1406684785389 hasn't completed at 1406685025407
	at hudson.remoting.PingThread.ping(PingThread.java:120)
	at hudson.remoting.PingThread.run(PingThread.java:81)



which is then followed by several instances of


VII 30, 2014 4:12:30 DOP. WARNING hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor
Failed to monitor macos-builder for Response Time
hudson.remoting.ChannelClosedException: channel is already closed
	at hudson.remoting.Channel.send(Channel.java:524)
	at hudson.remoting.Request.callAsync(Request.java:208)
	at hudson.remoting.Channel.callAsync(Channel.java:749)
	at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76)
	at hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:57)
	at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:280)
Caused by: java.io.IOException
	at hudson.remoting.Channel.close(Channel.java:1003)
	at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110)
	at hudson.remoting.PingThread.ping(PingThread.java:120)
	at hudson.remoting.PingThread.run(PingThread.java:81)
Caused by: java.util.concurrent.TimeoutException: Ping started on 1406684785389 hasn't completed at 1406685025407
	... 2 more



with different X in "for X" in the first line and then


VII 30, 2014 8:12:31 DOP. WARNING hudson.node_monitors.ResponseTimeMonitor
Making macos-builder offline because it’s not responding
VII 30, 2014 8:13:23 DOP. INFO hudson.slaves.RetentionStrategy$Demand
Launching computer macos-builder as it has been in demand for 9 hr 8 min



after which the slave never came back up. There were however these two errors:


VII 30, 2014 9:14:32 DOP. WARNING hudson.ExpressionFactory2$JexlExpression
Caught exception evaluating: it.oSDescription in /jenkins/computer/macos-builder/systemInfo. Reason: java.lang.reflect.InvocationTargetException
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.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
	at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
	at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
	at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
	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

[JIRA] [core] (JENKINS-16109) Slave hung archiving artifacts















































Jan Hudec
 commented on  JENKINS-16109


Slave hung archiving artifacts















Here an OS X slave, launched via ssh, is doing this. The other slave running on Win8 (and launched as service installed via JNLP) never had this problem so far.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-7025) Workspace permissions don't work with Project-based Matrix Authorization Strategy
















































Ulli Hafner
 resolved  JENKINS-7025 as Fixed


Workspace permissions dont work with Project-based Matrix Authorization Strategy
















Fixed in latest Jenkins and task scanner plugin.





Change By:


Ulli Hafner
(30/Jul/14 10:39 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24038) Header and Footer layout has fixed width















































Ulli Hafner
 created  JENKINS-24038


Header and Footer layout has fixed width















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


Bildschirmfoto 2014-07-30 um 12.47.10.png, Bildschirmfoto 2014-07-30 um 12.47.56.png



Components:


core



Created:


30/Jul/14 10:48 AM



Description:


The header and footer of the new Jenkins layout (1.574) seem to have a fixed width. If there is a view that does not fit on the current screen (e.g. source code listing) then the header and footer are cut off. The breadcrumb works as expected.  




Project:


Jenkins



Labels:


UI




Priority:


Minor



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-24011) Filtering of compiler warnings by regexp not working well















































Ulli Hafner
 commented on  JENKINS-24011


Filtering of compiler warnings by regexp not working well















Did you try 
{nofromat}
./log4cxx/source/.


? 
The patterns are Java regular expressions (and not ant patterns). 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-24011) Filtering of compiler warnings by regexp not working well













































 
Ulli Hafner
 edited a comment on  JENKINS-24011


Filtering of compiler warnings by regexp not working well
















Did you try 

.*/log4cxx/source/.*

? 
The patterns are Java regular expressions (and not ant patterns). 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-24011) Filtering of compiler warnings by regexp not working well













































 
Ulli Hafner
 edited a comment on  JENKINS-24011


Filtering of compiler warnings by regexp not working well
















Did you try 

.*log4cxx/source/.*

? 
The patterns are Java regular expressions (and not ant patterns). 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-24011) Filtering of compiler warnings by regexp not working well

2014-07-30 Thread jpsch...@mtu.net (JIRA)















































jpschewe
 commented on  JENKINS-24011


Filtering of compiler warnings by regexp not working well















Yes, I realize that they are not ant expressions, but given the problems I have been having I figured I would try all options. Here are the expressions that I have tried:

log4cxx/source
.*/log4cxx/source
.*/log4cxx/source/.*
log4cxx/source/**
.*log4cxx.*source.*
.*log4cxx.source.*






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [extended-choice-parameter] (JENKINS-24039) Cannot always deselect multi level parameters once selected

2014-07-30 Thread richiereyno...@ntlworld.com (JIRA)

Richard Reynolds
created JENKINS-24039

Cannot always deselect multi level parameters once selected

Issue Type:

Bug

Affects Versions:

current

Assignee:

vimil

Components:

extended-choice-parameter

Created:

30/Jul/14 11:00 AM

Description:

1. Multi level single select never shows a "remove" button to facilitate deselection. And, if you "deselect" by going back to the "select a ..." option, then the value of the parameter is "select a ..." rather than blank. It should be blank as if nothing had ever been selected. Or at least a remove button should appear to achieve deselection.
2. Multi level multi select doesn't show a remove button when there is only one selection. When you make a second selection via the "select other" button, then a remove button appears against both selections.
3. Multi level multi select has similar issues to single select with respect to deselecting i.e. if there is only one selection, going back to the "select a ..." option does not blank the parameter, and there is no remove button.

Environment:

jenkins 1.509.4, chrome Version 36.0.1985.125 m, extended choice parameter 0.34

Fix Versions:

current

Project:

Jenkins

Priority:

Minor

Reporter:

Richard Reynolds

[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated

2014-07-30 Thread belic_bo...@yahoo.com (JIRA)















































Bojan Belic
 commented on  JENKINS-20941


Stored git credentials not used when submodule is updated















Currently also experiencing this issue on our OSX build server. Tried some of the workarounds suggested but to no avail yet. Currently best option might be to actually update the submodules manually with:

git submodule init
git submodule update

If anyone does have a valid workaround for this with a Jenkins - Stash combination, feel free to let me know.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [matrix-project] (JENKINS-24020) Fail-fast Matrix builds, as soon some configuration fail

2014-07-30 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-24020


Fail-fast Matrix builds, as soon some configuration fail















How about aborting other child builds when a child build fails?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

iPhone/Android Application Development !!

2014-07-30 Thread Partick


  
  
Hi,   
 
I am Patrick– Marketing Executive (iPhone  Android Apps)  

we are a web development company specializing in development of iPhone and Android applications. We have more than 3 year of experience in developing custom mobile applications. Each application is reviewed and designed especially for each customer to fit the specific requirements and objectives. 

We help your business combine two modern business directions: wireless devices with web-based applications. High quality and customer-oriented approach are guaranteed.

Why iPhone Apps?
 
· Instant gratification
 
· Ease of use as it can be accessed anywhere
 
· Attracting new customers
 
· Increasing Revenue
 

For business, finding the right iPhone apps developer could be a key factor to adapting their product to the marketplace and for the right audience.
 
Give us an opportunity to serve you. I assure you would like our solution and services
 

 

  Thanks
 
Patrick       
 Based India
  




-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated

2014-07-30 Thread andre.ghes...@googlemail.com (JIRA)















































andre ghessen
 commented on  JENKINS-20941


Stored git credentials not used when submodule is updated















Yeah, this issue is a real pain for us too.

The only way we could get it working for our Stash/Jenkins setup was to create a read-only user and to hard code this user's credentials in the reference to the submodule.
Although bad practise, all users working on the git repo already have at least read-only access, so we didn't feel it was too much of a security concern.

e.g. in the parent repo .gitmodules file:

[submodule "shared-library"]
	path = shared-library
	url = "" class="code-comment">//username:passw...@stash.yourcompany.com/scm/project/shared-library.git


and then the Jenkins job has "Recursively update submodules" selected.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24026) Exposing Labels via the JSON API endpoint via GET/POST















































Daniel Beck
 commented on  JENKINS-24026


Exposing Labels via the JSON API endpoint via GET/POST















Some of that is implemented here, but not merged: https://github.com/jenkinsci/jenkins/pull/1166



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24032) Jenkins offers restart even though its Lifecycle does not support it















































Daniel Beck
 updated  JENKINS-24032


Jenkins offers restart even though its Lifecycle does not support it
















Clarified title as this error does not constitute a crash (abort of the software).





Change By:


Daniel Beck
(30/Jul/14 11:58 AM)




Summary:


Crashwhilerestartwhen
Jenkins
isntinstalledasaWindowsservice
offersrestarteventhoughitsLifecycledoesnotsupportit



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24038) Header and Footer layout has fixed width















































Daniel Beck
 commented on  JENKINS-24038


Header and Footer layout has fixed width















Not a regression AFAIK it has always behaved that way.

Not sure this is a real layout bug; plugins should not exceed window width or specify overflow behavior.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24032) Jenkins offers restart even though its Lifecycle does not support it
















































Daniel Beck
 assigned  JENKINS-24032 to Daniel Beck



Jenkins offers restart even though its Lifecycle does not support it
















Change By:


Daniel Beck
(30/Jul/14 12:02 PM)




Assignee:


DanielBeck



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24040) Excessive network load during build

2014-07-30 Thread s.cra...@tue.nl (JIRA)

Sjoerd Cranen
created JENKINS-24040

Excessive network load during build

Issue Type:

Bug

Assignee:

Unassigned

Components:

core

Created:

30/Jul/14 12:03 PM

Description:

We have a setup with 3 Ubuntu servers and a Mac mini, running jenkins JNLP clients. The ubuntu servers are running KVM, adding another 4 Windows VMs, and 2 linux VMs, each running jenkins JNLP clients. When building, each of those clients produces a constant network load of about 1MiB/s up and down.

I suspect the frequently occurring network connection problems in our build system (RequestAbortedException during the build, SVN not being able to check out sometimes) are due to this heavy load.

Is there any way to minimize the network traffic, or to at least figure out what is causing this load?

Environment:

Jenkins version 1.554.2

Servers: Ubuntu server 14.04, with KVM clients

Project:

Jenkins

Priority:

Major

Reporter:

Sjoerd Cranen

[JIRA] [core] (JENKINS-24038) Header and Footer layout has fixed width















































Ulli Hafner
 commented on  JENKINS-24038


Header and Footer layout has fixed width















In previous versions this was not so obvious because of the footer and breadcrumb color (white). 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-build-step] (JENKINS-24041) plugin depends on java 7

2014-07-30 Thread jenk...@aiko.sh (JIRA)















































Aiko Mastboom
 created  JENKINS-24041


plugin depends on java 7















Issue Type:


Bug



Assignee:


vjuranek



Components:


docker-build-step, plugin



Created:


30/Jul/14 12:19 PM



Description:


using this jenkins image:

docker pull orchardup/jenkins



FATAL: java.lang.System.lineSeparator()Ljava/lang/String;
java.lang.NoSuchMethodError: java.lang.System.lineSeparator()Ljava/lang/String;
	at org.jenkinsci.plugins.dockerbuildstep.util.PortUtils.parsePorts(PortUtils.java:52)
	at org.jenkinsci.plugins.dockerbuildstep.cmd.StartCommand.execute(StartCommand.java:72)
	at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder.perform(DockerBuilder.java:65)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
	at hudson.model.Build$BuildExecution.build(Build.java:199)
	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
	at hudson.plugins.project_inheritance.projects.InheritanceBuild$InheritanceBuildExecution.doRun(InheritanceBuild.java:111)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566)
	at hudson.model.Run.execute(Run.java:1678)
	at hudson.plugins.project_inheritance.projects.InheritanceBuild.run(InheritanceBuild.java:96)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)





Project:


Jenkins



Priority:


Major



Reporter:


Aiko Mastboom

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-build-step] (JENKINS-24042) unable to pass arguments to run command

2014-07-30 Thread jenk...@aiko.sh (JIRA)















































Aiko Mastboom
 created  JENKINS-24042


unable to pass arguments to run command















Issue Type:


Improvement



Assignee:


vjuranek



Components:


docker-build-step, plugin



Created:


30/Jul/14 12:26 PM



Description:


Create Container:
Command: /usr/sbin/sshd -D

error:


Jul 29, 2014 8:15:37 PM com.sun.jersey.api.client.filter.LoggingFilter log
INFO: 2 * Client out-bound request
2  GET http://172.17.42.1:2375/v1.11/containers/71256bc4697d3476c28f6816748cf5fe50f2d606055d6f56cc005c052617be83/json
2  Accept: application/json

Jul 29, 2014 8:15:37 PM com.sun.jersey.api.client.filter.LoggingFilter log
INFO: 2 * Client in-bound response
2  200
2  Content-Type: application/json
2  Date: Tue, 29 Jul 2014 20:15:37 GMT
2  Content-Length: 1351
2 
{"ID":"71256bc4697d3476c28f6816748cf5fe50f2d606055d6f56cc005c052617be83","Created":"2014-07-29T20:15:37.090659003Z","Path":"/usr/sbin/sshd -D","Args":[],"Config":{"Hostname":"71256bc4697d","Domainname":"","User":"","Memory":0,"MemorySwap":0,"CpuShares":0,"Cpuset":"","AttachStdin":false,"AttachStdout":false,"AttachStderr":false,"PortSpecs":null,"ExposedPorts":{"22/tcp":{}},"Tty":false,"OpenStdin":false,"StdinOnce":false,"Env":HOME=/,PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin,"Cmd":/usr/sbin/sshd -D,"Image":"jenkins-slave","Volumes":null,"WorkingDir":"","Entrypoint":null,"NetworkDisabled":false,"OnBuild":null},"State":{"Running":false,"Paused":false,"Pid":0,"ExitCode":0,"StartedAt":"0001-01-01T00:00:00Z","FinishedAt":"0001-01-01T00:00:00Z"},"Image":"293c8de174d33993d96b8672f03c70bcd65b0f330fdc6774c332b18f603147fa","NetworkSettings":{"IPAddress":"","IPPrefixLen":0,"Gateway":"","Bridge":"","PortMapping":null,"Ports":null},"ResolvConfPath":"","HostnamePath":"","HostsPath":"","Name":"/evil_brown","Driver":"aufs","ExecDriver":"native-0.2","MountLabel":"","ProcessLabel":"","Volumes":null,"VolumesRW":null,"HostConfig":{"Binds":null,"ContainerIDFile":"","LxcConf":null,"Privileged":false,"PortBindings":null,"Links":null,"PublishAllPorts":false,"Dns":null,"DnsSearch":null,"VolumesFrom":null,"NetworkMode":""}}

Jul 29, 2014 8:15:41 PM com.nirima.jenkins.plugins.docker.DockerRetentionStrategy check
INFO: Checking DockerComputer{name=51979187aead@docker-1, slave=DockerSlave{name=51979187aead@docker-1, containerId=51979187aead0a500f35cc7c3fb2cd94313ae4417e68225a3254b4cf07507540, template=DockerTemplate{image=jenkins-slave, parent=DockerCloud{name=docker-1, serverUrl=http://172.17.42.1:2375
Jul 29, 2014 8:15:41 PM com.nirima.jenkins.plugins.docker.DockerRetentionStrategy check
INFO: currentlyChecking: false
Jul 29, 2014 8:15:51 PM com.sun.jersey.api.client.filter.LoggingFilter log
INFO: 3 * Client out-bound request
3  POST http://172.17.42.1:2375/v1.11/containers/71256bc4697d3476c28f6816748cf5fe50f2d606055d6f56cc005c052617be83/start
3  Accept: text/plain

Jul 29, 2014 8:15:51 PM com.sun.jersey.api.client.filter.LoggingFilter log
INFO: 3 * Client in-bound response
3  500
3  Content-Type: application/json; charset=utf-8
3  Date: Tue, 29 Jul 2014 20:15:51 GMT
3  Content-Length: 166
3 
Cannot start container 71256bc4697d3476c28f6816748cf5fe50f2d606055d6f56cc005c052617be83: exec: "/usr/sbin/sshd -D": stat /usr/sbin/sshd -D: no such file or directory




Environment:


docker pull orchardup/jenkins




Project:


Jenkins



Priority:


Major



Reporter:


Aiko Mastboom

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA,

[JIRA] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later

2014-07-30 Thread stevengbr...@java.net (JIRA)
















































stevengbrown
 resolved  JENKINS-23867 as Fixed


Incompatibility with Jenkins 1.572 or later
















Change By:


stevengbrown
(30/Jul/14 12:33 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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [android-emulator] (JENKINS-23736) Emulator plugin can not run emulator if user is not logged on to desktop

2014-07-30 Thread os...@smsgrupp.se (JIRA)















































Oskar Danielsson
 commented on  JENKINS-23736


Emulator plugin can not run emulator if user is not logged on to desktop















How do I solve this?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [matrix-combinations-parameter] (JENKINS-24023) Matrix unformatted

2014-07-30 Thread roger.tulio.si...@gmail.com (JIRA)















































Roger Silva
 commented on  JENKINS-24023


Matrix unformatted















Sorry for that, I thought I'd been clear enough.

I just posted the screenshot.

I think would be better formatted if you use a table, such as when there are more combinations.


Regards.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later

2014-07-30 Thread arkconfu...@hotmail.com (JIRA)















































A. Kirby
 commented on  JENKINS-23867


Incompatibility with Jenkins 1.572 or later















I downloaded the 1.5.14-SNAPSHOT package and installed it on my Jenkins test server.  I am still not seeing the timestamper.  I'm still seeing the same issue where the timestamp span isn't being rendered on the page causing the jquery code to not bind.  Even if I use jquery to insert the missing span, timestamper still doesn't want to render the timestamps in the console output.  I have tried uninstalling, rebooting the server, manually deleting the plugin and downgrading the plugin.  With the rollout of 1.572 this plugin has completely stopped working for me.  I am using 1.574 and I keep upgrading hoping that either a newer Jenkins or a newer plugin will resolve the problem.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-build-step] (JENKINS-24043) envvars not resolved for 'wait for ports' field

2014-07-30 Thread jenk...@aiko.sh (JIRA)















































Aiko Mastboom
 created  JENKINS-24043


envvars not resolved for wait for ports field















Issue Type:


Bug



Assignee:


vjuranek



Components:


docker-build-step, plugin



Created:


30/Jul/14 1:17 PM



Description:


Trying to start a container providing the following:

Docker command: Start Containers(s)
Container ID(s): $DOCKER_CONTAINER_IDS
Wait for ports: $DOCKER_CONTAINER_IDS 22

error:

Docker INFO: started container id df65196e50c8b48963d0f3cd8c1f3e548effe03d2b3b1ad4e36564985f6a1cf6
Docker ERROR: command 'Start container(s)' failed: No such container $DOCKER_CONTAINER_IDS
ERROR: No such container $DOCKER_CONTAINER_IDS
ERROR: Publisher com.nirima.jenkins.plugins.docker.publisher.DockerPublisherControl aborted due to exception
java.lang.NullPointerException
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685)
	at hudson.model.Run.execute(Run.java:1757)
	at hudson.plugins.project_inheritance.projects.InheritanceBuild.run(InheritanceBuild.java:96)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:234)


NOTE: I am not sure how to break down DOCKER_CONATAINER_IDS into individual ids when used in wait for ports field. At the moment I only create one container so problem yet.




Environment:


docker pull orchardup/jenkins

+

RUN apt-get install -y apt-transport-https

RUN apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9

RUN echo deb https://get.docker.io/ubuntu docker main  /etc/apt/sources.list.d/docker.list

RUN apt-get update

RUN apt-get install -y net-tools lxc-docker-1.0.1



# upgrade and workaround JENKINS-24041

RUN apt-get install -y jenkins=1.574 openjdk-7-jre



# manual?? pick jdk7

## update-alternatives --config java




Project:


Jenkins



Priority:


Major



Reporter:


Aiko Mastboom

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [matrix-project] (JENKINS-24020) Fail-fast Matrix builds, as soon some configuration fail

2014-07-30 Thread br...@meneguello.com (JIRA)















































Bruno Meneguello
 commented on  JENKINS-24020


Fail-fast Matrix builds, as soon some configuration fail















My boss give me the same idea. My point is this must be an opt-in feature, because I want to know all failures (to map my correction actions). But allowing the build stop after the first failure should be very useful in some scenarios.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows loading jobs..

2014-07-30 Thread benja...@herbert.cc (JIRA)















































Benjamin Herbert
 commented on  JENKINS-23620


The periodic refresh shows loading jobs.. 















I was suffering from this bug, I had to go back to 0.6.21.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23810) Create a div based alternative tot he l:pane tag
















































Tom FENNELLY
 resolved  JENKINS-23810 as Fixed


Create a div based alternative tot he l:pane tag
















Pushed upstream in bced2c7





Change By:


Tom FENNELLY
(30/Jul/14 1:45 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-9576) java.net.SocketException: Socket closed

2014-07-30 Thread s.cra...@tue.nl (JIRA)















































Sjoerd Cranen
 commented on  JENKINS-9576


java.net.SocketException: Socket closed















I'm getting this problem as well. It happens to my Windows VMs about 2/3 times. When there is a queue, new jobs can start right after the socket exception happens; could it be a timeout that has been set too strict? I think it might also be related to the high network traffic that Jenkins is creating (see JENKINS-24040).


FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed
hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed
	at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41)
	at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34)
	at hudson.remoting.Request.call(Request.java:174)
	at hudson.remoting.Channel.call(Channel.java:722)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167)
	at com.sun.proxy.$Proxy47.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:955)
	at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:140)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.Build$BuildExecution.build(Build.java:199)
	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585)
	at hudson.model.Run.execute(Run.java:1684)
	at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed
	at hudson.remoting.Request.abort(Request.java:299)
	at hudson.remoting.Channel.terminate(Channel.java:782)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
Caused by: java.net.SocketException: Socket closed
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:152)
	at java.net.SocketInputStream.read(SocketInputStream.java:122)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
	at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:77)
	at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293)
	at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2586)
	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
	at hudson.remoting.Command.readFrom(Command.java:92)
	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [memory-map] (JENKINS-23734) (our case 11569 )Memory map plugin does not allow to enter absolute or relative path

2014-07-30 Thread jbrej...@praqma.net (JIRA)















































Jens  Brejner
 commented on  JENKINS-23734


(our case 11569 )Memory map plugin does not allow to enter absolute or relative path















I will work with Per on this.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-24044) WORKSPACE Environment Variable Set to the first module on the list

Shawn Cole
created JENKINS-24044

WORKSPACE Environment Variable Set to the first module on the list

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

subversion

Created:

30/Jul/14 2:03 PM

Description:

When using multiple SVN Url's in one project, with each set to the following:

Repository URL: http://svnserver/repo/Project/module1/trunk/src
Local Module Directory: module1

Repository URL: http://svnserver/repo/Project/module2/trunk/src
Local Module Directory: module2

...

$WORKSPACE in this case is set to C:\Jenkins\Jobs\Project\Workspace.
Instead, workspace is being set to C:\Jenkins\Jobs\Project\Workspace\module1.

Not having the working directory set correctly is a big issue for my downstream steps.

Environment:

Windows Server 2008

Project:

Jenkins

Labels:

scm
subversion
modules

Priority:

Critical

Reporter:

Shawn Cole

[JIRA] [subversion] (JENKINS-24044) WORKSPACE Environment Variable Set to the first module on the list















































Shawn Cole
 updated  JENKINS-24044


WORKSPACE Environment Variable Set to the first module on the list
















Change By:


Shawn Cole
(30/Jul/14 2:14 PM)




Description:


WhenusingmultipleSVNUrlsinoneproject,witheachsettothefollowing:RepositoryURL:http://svnserver/repo/Project/module1/trunk/srcLocalModuleDirectory:module1RepositoryURL:http://svnserver/repo/Project/module2/trunk/srcLocalModuleDirectory:module2...$WORKSPACEinthiscase
is
ShouldBe
settoC:\Jenkins\Jobs\Project\Workspace.Instead,workspaceisbeingsettoC:\Jenkins\Jobs\Project\Workspace\module1.Nothavingtheworkingdirectorysetcorrectlyisabigissueformydownstreamsteps.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [coverity] (JENKINS-20632) Conditionally execute Coverity plugin fails during publish.

2014-07-30 Thread de...@ikedam.jp (JIRA)















































ikedam
 updated  JENKINS-20632


Conditionally execute Coverity plugin fails during publish.
















Change By:


ikedam
(30/Jul/14 2:17 PM)




Component/s:


flexible-publish



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes

2014-07-30 Thread philipp.sere...@edstrom.com (JIRA)













































 
Phil Seremin
 edited a comment on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes
















I can't say I understood half of what the doc said, sorry. Would it be possible for you to explain how I need to configure my job? Currently my "Branches to build" says "master" and all works fine. I tried prepending it with  "refs/heads/" and the build failed (ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.).

I use Jenkins 1.570, git-client-plugin 1.10.0.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes

2014-07-30 Thread philipp.sere...@edstrom.com (JIRA)















































Phil Seremin
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















I can't say I understood half of what you said, sorry. Would it be possible for you to explain how I need to configure my job? Currently my "Branches to build" says "master" and all works fine. I tried prepending it with  "refs/heads/" and the build failed (ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.).

I use Jenkins 1.570, git-client-plugin 1.10.0.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later

2014-07-30 Thread stevengbr...@java.net (JIRA)















































stevengbrown
 reopened  JENKINS-23867


Incompatibility with Jenkins 1.572 or later
















A. Kirby,

Could you clarify what problems you are experiencing? I think that your timestamps are not appearing, and also something else went wrong that prompted you to uninstall the plugin?





Change By:


stevengbrown
(30/Jul/14 2:46 PM)




Resolution:


Fixed





Status:


Resolved
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes

2014-07-30 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















I constructed a test job and set "Branches to build" to refs/remotes/origin/master.  I believe that is an unambiguous declaration of the branch I usually would call "origin/master".



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24040) Excessive network load during build















































Daniel Beck
 commented on  JENKINS-24040


Excessive network load during build















Is this a bug report, or a request for assistance?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-build-publish] (JENKINS-24045) Allow multiple repository login

2014-07-30 Thread k...@goyman.com (JIRA)















































Nicolas Goy
 created  JENKINS-24045


Allow multiple repository login















Issue Type:


Improvement



Assignee:


Michael Neale



Components:


docker-build-publish



Created:


30/Jul/14 3:11 PM



Description:


In the plugin description, it is stated that the docker-build-publish-plugin can be used with private registries. But only the credentials for the official public registry can be set.

The command line is:

docker login -u user -p pass -e email  registryaddress

Registry address cannot be set at this time.




Project:


Jenkins



Priority:


Major



Reporter:


Nicolas Goy

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later

2014-07-30 Thread arkconfu...@hotmail.com (JIRA)

A. Kirby
commented on JENKINS-23867

Incompatibility with Jenkins 1.572 or later

Steve,

I had timestamper installed and working for a while, then I upgraded jenkins to 1.572 and it stopped working. I tried uninstalling timestamp, installing it again, upgrading to the latest and upgrading jenkins to 1.573 and now 1.574. I have the latest version of timestamper installed; the 1.5.14 snapshot and it's still not working. The first thing I have noticed is the span.timestamp tag isn't being inserted into the side panel. In script.js it looks for this to bind to, but the plugin isn't inserting it into the DOM. If I use a little jquery to create the span myself, it does render the radio buttons and even binds the events. However, it still doesn't render the information in the console output. It seems like although the plugin is installed, and is enabled, it's not being executed correctly if at all. I do see the settings in the Manage Jenkins - Configure System - Timestamper section.

[JIRA] [matrix-project] (JENKINS-24020) Fail-fast Matrix builds, as soon some configuration fail

2014-07-30 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-24020


Fail-fast Matrix builds, as soon some configuration fail















I got what you want. Let's find a good approach to get the failure result in advance but leave the build running.

What do you exactly mean with "the overall project status"?
If you mean ball icons of projects, you can change its behavior by overriding MatrixBuild#getIconColor.
The current behavior is defined in Run#getIconColor. It uses an animating icon of the result of the last completed build if the current build is running.
How about using an animating failure icon if the current build is running but a child build have failed?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23560) Slave hung in startup phase with missing logging in the GUI

2014-07-30 Thread aszos...@partner.eso.org (JIRA)















































Artur Szostak
 commented on  JENKINS-23560


Slave hung in startup phase with missing logging in the GUI















This is starting to become a blocker. It is happening regularly (2-3 times a week) and forcing a restart of Jenkins. I have updated to Jenkins version 1.554.3 with no improvement.

I think I managed to catch the problem at a slightly earlier moment this time also. After a restart of Jenkins, a number of hours later a job was stuck on one of the build slaves and was aborted. When logging into the machine there was no sign of the Jenkins slave Java process running. However, in the Jenkins GUI the slave appeared to be running or at least starting. About 10 minutes before the stuck job another job ran and failed with the build log following messages:

Started by upstream project "admin-validate-slave-configs" build number 456
originally caused by:
 Started by timer
EnvInject - Loading node environment variables.
EnvInject - ERROR - SEVERE ERROR occurs: java.lang.InterruptedException

Deleting project workspace... 
Collecting metadata...
Metadata collection done.
Finished: FAILURE



The thread stack dumps that I believe are relevant:

"Channel reader thread: ma016213" Id=23008 Group=main WAITING on com.trilead.ssh2.channel.Channel@1d6e8511
	at java.lang.Object.wait(Native Method)

	waiting on com.trilead.ssh2.channel.Channel@1d6e8511
	at java.lang.Object.wait(Object.java:503)
	at com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212)
	at com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127)
	at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:946)
	at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58)
	at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79)
	at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:77)
	at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293)
	at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2586)
	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1706)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1344)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
	at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:500)
	at java.lang.Throwable.readObject(Throwable.java:914)
	at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1017)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1893)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
	at hudson.remoting.Command.readFrom(Command.java:92)
	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)




"Executor #0 for ma016213 : executing admin-validate-slave-configs » ma016213 #456 / waiting for hudson.remoting.Channel@21fb7f0a:ma016213" Id=254 Group=main TIMED_WAITING on hudson.remoting.UserRequest@e493bde
	at java.lang.Object.wait(Native Method)

	waiting on hudson.remoting.UserRequest@e493bde
	at

[JIRA] [subversion] (JENKINS-24044) WORKSPACE Environment Variable Set to the first module on the list















































Daniel Beck
 updated  JENKINS-24044


WORKSPACE Environment Variable Set to the first module on the list
















Reducing priority as this does not result in crash or data loss, and seems to have an easy workaround in using the parent directory of the provided WORKSPACE.

Please provide a sample job config.xml file.

Please specify the version of Jenkins and Subversion plugin (we're not using the Jira version fields).





Change By:


Daniel Beck
(30/Jul/14 3:14 PM)




Priority:


Critical
Minor



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-24044) WORKSPACE Environment Variable Set to the first module on the list















































Shawn Cole
 updated  JENKINS-24044


WORKSPACE Environment Variable Set to the first module on the list
















Change By:


Shawn Cole
(30/Jul/14 3:46 PM)




Attachment:


config.xml





Description:


VERSION:Jenkins1.573SubversionPlugin2.4.1
WhenusingmultipleSVNUrlsinoneproject,witheachsettothefollowing:RepositoryURL:http://svnserver/repo/Project/module1/trunk/srcLocalModuleDirectory:module1RepositoryURL:http://svnserver/repo/Project/module2/trunk/srcLocalModuleDirectory:module2...$WORKSPACEinthiscaseShouldBesettoC:\Jenkins\Jobs\Project\Workspace.Instead,workspaceisbeingsettoC:\Jenkins\Jobs\Project\Workspace\module1.Nothavingtheworkingdirectorysetcorrectlyisabigissueformydownstreamsteps.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace

2014-07-30 Thread damien.no...@gmail.com (JIRA)















































Damien Nozay
 commented on  JENKINS-20843


build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace















build-flow v. 0.12 can now use a workspace back again.
https://github.com/jenkinsci/build-flow-plugin/commit/00b7ad56eca41eebcfd19bd3e54de0ace66ae0be

Corey, could you please verify you are now able to use it as you intended?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23842) Wrap icon images in an l:icon tag
















































Tom FENNELLY
 resolved  JENKINS-23842 as Fixed


Wrap icon images in an l:icon tag
















Pushed upstream in 42190ed





Change By:


Tom FENNELLY
(30/Jul/14 4:09 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-24044) WORKSPACE Environment Variable Set to the first module on the list















































Daniel Beck
 commented on  JENKINS-24044


WORKSPACE Environment Variable Set to the first module on the list















Cannot reproduce the issue (haven't used your config exactly of course, but still, two locations checked out, both in subdirs, 'echo $WORKSPACE' in the shell...

Do you have env-inject installed? If so, what version? What happens when you disable it, or could you set up a pristine Jenkins instance and try to reproduce the issue there?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23829) Layout: Job history may overlap main job status
















































Tom FENNELLY
 resolved  JENKINS-23829 as Fixed


Layout: Job history may overlap main job status
















Fixed in bced2c7





Change By:


Tom FENNELLY
(30/Jul/14 4:09 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24027) Null Pointer Exception when trying to update workspace

2014-07-30 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-24027


Null Pointer Exception when trying to update workspace















Code changed in jenkins
User: Paul Allen
Path:
 src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java
 src/main/java/org/jenkinsci/plugins/p4/workspace/Workspace.java
 src/test/java/org/jenkinsci/plugins/p4/client/ConnectionTest.java
http://jenkins-ci.org/commit/p4-plugin/2a449f988c5921a7fdb8773236e115069c6c12fc
Log:
  Clone Workspace as Build Matrix was using the same object.

https://issues.jenkins-ci.org/browse/JENKINS-24027





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24022) Running 'files' command for multiple hours with a label
















































Paul Allen
 closed  JENKINS-24022 as Fixed


Running files command for multiple hours with a label
















Release 1.0.8

Limit to 50 files and number of reported changes on first build.





Change By:


Paul Allen
(30/Jul/14 4:39 PM)




Status:


Open
Closed





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















































Paul Allen
 closed  JENKINS-24028 as Fixed


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















Release 1.0.8

Replace "/" "=" and "," with "-" as per old plugin





Change By:


Paul Allen
(30/Jul/14 4:40 PM)




Status:


Open
Closed





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24027) Null Pointer Exception when trying to update workspace
















































Paul Allen
 closed  JENKINS-24027 as Fixed


Null Pointer Exception when trying to update workspace
















Release 1.0.8

Shared Workshop object was not cloned for Matrix Builds and not required for non client functions like p4 changes/p4 files.

Should fix this issue; please reopen if required. 





Change By:


Paul Allen
(30/Jul/14 4:43 PM)




Status:


Open
Closed





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23560) Slave hung in startup phase with missing logging in the GUI

2014-07-30 Thread aszos...@partner.eso.org (JIRA)















































Artur Szostak
 commented on  JENKINS-23560


Slave hung in startup phase with missing logging in the GUI















Additional thread dumps that could be relevant to the previous comment:

"Computer.threadPoolForRemoting 144" Id=22726 Group=main WAITING on java.util.concurrent.FutureTask@497a56f6
at sun.misc.Unsafe.park(Native Method)

	waiting on java.util.concurrent.FutureTask@497a56f6
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:425)
at java.util.concurrent.FutureTask.get(FutureTask.java:187)
at java.util.concurrent.AbstractExecutorService.invokeAll(AbstractExecutorService.java:243)
at java.util.concurrent.Executors$DelegatedExecutorService.invokeAll(Executors.java:648)
at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:691)
	locked hudson.plugins.sshslaves.SSHLauncher@f4631f7
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)



Number of locked synchronizers = 1

	java.util.concurrent.ThreadPoolExecutor$Worker@451047f5




"Computer.threadPoolForRemoting 744" Id=38276 Group=main BLOCKED on hudson.plugins.sshslaves.SSHLauncher@f4631f7 owned by "Computer.threadPoolForRemoting 144" Id=22726
at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1152)

	blocked on hudson.plugins.sshslaves.SSHLauncher@f4631f7
at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:547)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)



Number of locked synchronizers = 1

	java.util.concurrent.ThreadPoolExecutor$Worker@3bd8d3ab




"Computer.threadPoolForRemoting 823" Id=40700 Group=main BLOCKED on hudson.plugins.sshslaves.SSHLauncher@f4631f7 owned by "Computer.threadPoolForRemoting 144" Id=22726
at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:639)

	blocked on hudson.plugins.sshslaves.SSHLauncher@f4631f7
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)



Number of locked synchronizers = 1

	java.util.concurrent.ThreadPoolExecutor$Worker@5f27ca48




"Computer.threadPoolForRemoting 849" Id=41501 Group=main BLOCKED on hudson.plugins.sshslaves.SSHLauncher@f4631f7 owned by "Computer.threadPoolForRemoting 144" Id=22726
at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:639)

	blocked on hudson.plugins.sshslaves.SSHLauncher@f4631f7
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)



Number of locked synchronizers = 1

	java.util.concurrent.ThreadPoolExecutor$Worker@36a88ffe





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more

[JIRA] [p4] (JENKINS-24004) dev and main branch versions are out of sync
















































Paul Allen
 closed  JENKINS-24004 as Fixed


dev and main branch versions are out of sync
















Done





Change By:


Paul Allen
(30/Jul/14 4:52 PM)




Status:


Open
Closed





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sonar] (JENKINS-24044) WORKSPACE Environment Variable Set to the first module on the list















































Shawn Cole
 updated  JENKINS-24044


WORKSPACE Environment Variable Set to the first module on the list
















Change By:


Shawn Cole
(30/Jul/14 4:53 PM)




Description:


VERSION:Jenkins1.573SubversionPlugin2.4.1WhenusingmultipleSVNUrlsinoneproject,witheachsettothefollowing:RepositoryURL:http://svnserver/repo/Project/module1/trunk/srcLocalModuleDirectory:module1RepositoryURL:http://svnserver/repo/Project/module2/trunk/srcLocalModuleDirectory:module2...
$WORKSPACE
Mysonar.ProjectBaseDirisbeingsetimproperly,causingbuildstofail.Wheretheproperty
inthiscase
ShouldBe
shouldbe
settoC:\Jenkins\Jobs\Project\Workspace
.Instead
,
workspace
it
is
instead
beingsettoC:\Jenkins\Jobs\Project\Workspace\module1
.Nothavingtheworkingdirectorysetcorrectlyisabigissueformydownstreamsteps.





Component/s:


sonar



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-23881) Too much changelog
















































Paul Allen
 closed  JENKINS-23881 as Fixed


Too much changelog
















Resolved in 1.0.8 (perhaps even 1.0.7)





Change By:


Paul Allen
(30/Jul/14 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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24024) Opt-out of pulling changelist info for Build Changes















































Paul Allen
 commented on  JENKINS-24024


Opt-out of pulling changelist info for Build Changes















Should the opt-out be global or configured for each Jenkins Build Job?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24024) Opt-out of pulling changelist info for Build Changes

2014-07-30 Thread rhum...@ravensoftware.com (JIRA)















































Ryan Hummer
 commented on  JENKINS-24024


Opt-out of pulling changelist info for Build Changes















opt-out per-job



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sonar] (JENKINS-24044) SonarQube's sonar.ProjectBaseDir Set to the first module on the list















































Shawn Cole
 commented on  JENKINS-24044


SonarQubes sonar.ProjectBaseDir Set to the first module on the list















Sorry Daniel, thanks for your troubleshooting, it seems the problem isn't related the to Workspace Environment Variable, but rather the sonar plugin. The Env-Inject Plugin is not installed on this instance.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24025) Unable to set line ending format for stream workspace















































Paul Allen
 commented on  JENKINS-24025


Unable to set line ending format for stream workspace















I can add this to the 'Stream' option for generating streams workspaces.

Are you able to use the 'Manual', 'Spec', or 'Static' workspace options?  I guess that they are not as easy for matrix builds as you would have to set them up individually.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sonar] (JENKINS-24044) SonarQube's sonar.ProjectBaseDir Set to the first module on the list















































Shawn Cole
 updated  JENKINS-24044


SonarQubes sonar.ProjectBaseDir Set to the first module on the list
















Change By:


Shawn Cole
(30/Jul/14 5:01 PM)




Summary:


WORKSPACEEnvironmentVariable
SonarQubessonar.ProjectBaseDir
Settothefirstmoduleonthelist





Labels:


modulesscm
sonar
subversion





Priority:


Minor
Major





Description:


VERSION:Jenkins1.573SubversionPlugin2.4.1
SonarPlugin2.1


WhenusingmultipleSVNUrlsinoneproject,witheachsettothefollowing:RepositoryURL:http://svnserver/repo/Project/module1/trunk/srcLocalModuleDirectory:module1RepositoryURL:http://svnserver/repo/Project/module2/trunk/srcLocalModuleDirectory:module2...Mysonar.ProjectBaseDirisbeingsetimproperly,causingbuildstofail.WherethepropertyinthiscaseshouldbesettoC:\Jenkins\Jobs\Project\Workspace,itisinsteadbeingsettoC:\Jenkins\Jobs\Project\Workspace\module1
Whentryingtosetthepropertymanuallywithsonar.ProjectBaseDir=$WORKSPACEitcomesoutas-Dsonar.projectBaseDir=D:JenkinsjobsProjectNameworkspace(Noslashes)Anyattemptstobackreferencesonarpropertiestotheworkspaceparentfolderhaveprovenunsuccessful



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion















































Paul Allen
 commented on  JENKINS-24005


Pin build at Perforce Label does not support variable expansion















Interesting uses case; I had not thought of that option.  Out of interest what sort of variables do you use?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-23890) Error on build with SCM changes















































Paul Allen
 commented on  JENKINS-23890


Error on build with SCM changes 















Please can you check this with the 1.0.8 release.  I have not been able to reproduce this issue, it seems that Jetty swallows up the error.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-23974) Private maven repo got wipe out every build















































Paul Allen
 commented on  JENKINS-23974


Private maven repo got wipe out every build















Should I close this issue?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion

2014-07-30 Thread rhum...@ravensoftware.com (JIRA)















































Ryan Hummer
 commented on  JENKINS-24005


Pin build at Perforce Label does not support variable expansion















We default the build variable to a known label.  So by default we build against the label we want.  But in the case that the label isn't updated that day or we want to make a build on demand.  We can kick a build using a specific changelist or by leaving it blank it will be built against head.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24025) Unable to set line ending format for stream workspace

2014-07-30 Thread glimb...@gmail.com (JIRA)















































Grant Limberg
 commented on  JENKINS-24025


Unable to set line ending format for stream workspace















I could use one of the other options, but it's nowhere near as convenient as the Stream option on matrix builds.

My temporary workaround is to just update the workspaces manually once Jenkins creates them, but that will need to be done each time a new build node comes online, or any time a new project in Jenkins is created.  A bit of a PITA.  I'd appreciate having the option



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion

2014-07-30 Thread rhum...@ravensoftware.com (JIRA)













































 
Ryan Hummer
 edited a comment on  JENKINS-24005


Pin build at Perforce Label does not support variable expansion
















We use the paramaterized build options, and default the build variable to a known label.  So by default we build against the label we want.  But in the case that the label isn't updated that day or we want to make a build on demand.  We can kick a build using a specific changelist or by leaving it blank it will be built against head.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-23974) Private maven repo got wipe out every build

2014-07-30 Thread dant...@gmail.com (JIRA)















































dan tran
 commented on  JENKINS-23974


Private maven repo got wipe out every build















please do



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-23890) Error on build with SCM changes

2014-07-30 Thread dant...@gmail.com (JIRA)















































dan tran
 commented on  JENKINS-23890


Error on build with SCM changes 















Just tested with latest p4jenkins at your dev branch, the problem still around.  



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-23884) Git/GitHub Enterprise (GHE) SCM Polling creates builds with No Changes when there are two similarly named branches present

2014-07-30 Thread michelene.c...@am.sony.com (JIRA)















































M Chon
 commented on  JENKINS-23884


Git/GitHub Enterprise (GHE) SCM Polling creates builds with No Changes when there are two similarly named branches present















Confirmed fixed! Thank you!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sonar] (JENKINS-24044) SonarQube's sonar.ProjectBaseDir Set to the first module on the list















































Daniel Beck
 updated  JENKINS-24044


SonarQubes sonar.ProjectBaseDir Set to the first module on the list
















And you even had echo %WORKSPACE% in there...

FWIW it's almost sure SCM.getModuleRoot returning the first checked out module directory being used to set Sonar base directory. I observed the same braindead behavior with the Gradle plugin.





Change By:


Daniel Beck
(30/Jul/14 6:01 PM)




Labels:


modulesscm
sonar
subversion





Affects Version/s:


current





Component/s:


subversion



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24046) Updating a WAR should unpin a plugin which is now older than the bundled plugin















































Jesse Glick
 created  JENKINS-24046


Updating a WAR should unpin a plugin which is now older than the bundled plugin















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


30/Jul/14 6:06 PM



Description:


If you have some pinned plugins, and start running a new WAR file with different set/versions of bundled plugins, the current behavior of Jenkins is to unconditionally trust your pinned plugins and never use the bundled versions. But this can be very bad, if you have pinned an old version of a plugin and some other bundled plugins depend on a newer version. So Jenkins should prefer a bundled plugin (removing the pin) if it is newer than the pinned version.




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cloudbees-enterprise-plugins] (JENKINS-24047) More conservative installation mode

Jesse Glick
created JENKINS-24047

More conservative installation mode

Issue Type:

New Feature

Assignee:

Unassigned

Components:

cloudbees-enterprise-plugins

Created:

30/Jul/14 6:14 PM

Description:

A customer tried to explore JEbC using this metaplugin but found that it (a) installed every JEbC plugin, which he did not necessarily want; (b) forced installation/upgrade of all OSS plugins that JEbC currently happens to bundle, even those which he already had installed in a version he had tested and liked.

It would be better when installing the metaplugin to explicitly ask what you want to do. One option would be the current behavior, which is to add/upgrade everything, similar to what would happen if you started running the JEbC WAR file on the same $JENKINS_HOME (though not identical, since that would currently leave your pinned plugins alone: JENKINS-24046). But another option would be much more conservative:

1. Download async-http-client from the OSS update center and schedule for installation after restart, unless you have it already in a sufficiently new version. If you have it installed but it is too old, download the current version and schedule for update after restart.
1. Download versions of the cloudbees-license and nectar-license plugins from the JEbC update center matching your core version, and schedule them for installation after restart.
1. Restart Jenkins, which should automatically switch your default update center to the correct JEbC one.

At that point you could install or update any other plugins on your own schedule.

Project:

Jenkins

Priority:

Critical

Reporter:

Jesse Glick

[JIRA] [cloudbees-enterprise-plugins] (JENKINS-24047) More conservative installation mode















































Jesse Glick
 commented on  JENKINS-24047


More conservative installation mode















Would also suggest somehow letting cloudbees-enterprise-plugins let you set up your license in advance of the restart, so that there is no window during which you are blocked from using Jenkins. Not sure how best to do this while offering the full functionality of both EvaluationRegistrar and EnterpriseRegistrar. Perhaps just display the instance ID, offer a link to licenses.cloudbees.com, and suggest you register via the web and manually copy back your details to Jenkins, using the equivalent of ManualRegistrar?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client] (JENKINS-22400) Git timeout on other actions than fetch/clone

2014-07-30 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-22400


Git timeout on other actions than fetch/clone















Timeout API implementation for checkout is available in git-client-plugin 1.10.0.

Access to that API is not yet implemented for the git plugin.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client] (JENKINS-22119) Fail to update git repository with stored credential

2014-07-30 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 updated  JENKINS-22119


Fail to update git repository with stored credential
















Change By:


Mark Waite
(30/Jul/14 6:40 PM)




Summary:


Failtoupdate
update
gitrepositorywithstoredcredential



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-monitor] (JENKINS-24048) Ability to set default column count and font size in configure page

2014-07-30 Thread klei...@gmail.com (JIRA)















































Kyle Leinen
 created  JENKINS-24048


Ability to set default column count and font size in configure page















Issue Type:


New Feature



Affects Versions:


current



Assignee:


Unassigned


Components:


build-monitor



Created:


30/Jul/14 7:09 PM



Description:


Since a clearing of the browser cache or reload of the browser seems to clear these settings, it makes viewing the page on automated build screens somewhat hard to manage.

It would be nice if the default values for the column count and font size could be defined in the Jenkins view configuration page.  That would allow automated screens to be easy to setup without removing the ability for each person to customize per their browser.




Project:


Jenkins



Priority:


Major



Reporter:


Kyle Leinen

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [other] (JENKINS-2551) Option to compress build logs
















































Jesse Glick
 resolved  JENKINS-2551 as Fixed


Option to compress build logs
















Sounds like that would suffice. Nice work!





Change By:


Jesse Glick
(30/Jul/14 7:14 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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-14538) Separate configure tools page