[JIRA] [core] (JENKINS-24000) Jenkins $WORKSPACE variable override project internal properties "workspace"
Mathieu BODIN commented on JENKINS-24000 Jenkins $WORKSPACE variable override project internal properties "workspace" Thank you for the quick answer, even a bit disappointing (a little, just saying ) but I do understand. For the record, it's a Maven build. There's a lot of modules, I won't have time to switch to another project type. I'll just rename my variable, as I should practice what I suggested : It's a good practice to use namespace on properties, even if it length their names. This message is automatically generated by JIRA. 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
Dirk Kuypers commented on JENKINS-23867 Incompatibility with Jenkins 1.572 or later Steven, good Job! It works again. Thanks! This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-22186) ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Brian May resolved JENKINS-22186 as Fixed ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Appears to be ok in latest version. Change By: Brian May (29/Jul/14 6:08 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22186) ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Brian May commented on JENKINS-22186 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Apologies for the delay in responding. It appears to be working fine in the latest version. This message is automatically generated by JIRA. 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] [export-params] (JENKINS-23849) Relative path "/../" in "File path" are ignored
rin_ne stopped work on JENKINS-23849 Relative path "/../" in "File path" are ignored Change By: rin_ne (29/Jul/14 6:00 AM) Status: In Progress Open This message is automatically generated by JIRA. 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] [export-params] (JENKINS-23849) Relative path "/../" in "File path" are ignored
SCM/JIRA link daemon commented on JENKINS-23849 Relative path "/../" in "File path" are ignored Code changed in jenkins User: rinrinne Path: src/main/java/org/jenkinsci/plugins/exportparams/ExportParametersBuilder.java http://jenkins-ci.org/commit/export-params-plugin/f094c0203ee37952b221bbba7b2ec517b4bc622a Log: Fix wrong implementation for remote files JENKINS-23849: Relative path "/../" in "File path" are ignored Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-23849 This message is automatically generated by JIRA. 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] [export-params] (JENKINS-23849) Relative path "/../" in "File path" are ignored
rin_ne started work on JENKINS-23849 Relative path "/../" in "File path" are ignored Change By: rin_ne (29/Jul/14 5:58 AM) Status: Open In Progress This message is automatically generated by JIRA. 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] [export-params] (JENKINS-23849) Relative path "/../" in "File path" are ignored
rin_ne updated JENKINS-23849 Relative path "/../" in "File path" are ignored Change By: rin_ne (29/Jul/14 5:58 AM) Assignee: rin_ne This message is automatically generated by JIRA. 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-23607) BuildGraph page doesn't load if some builds are queued
stuart rowe assigned JENKINS-23607 to Nicolas De Loof BuildGraph page doesn't load if some builds are queued Change By: stuart rowe (29/Jul/14 5:53 AM) Assignee: Nicolas De Loof This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-24012) Messages in RabbitMQ's queue was consumed but unacknowledged
rin_ne stopped work on JENKINS-24012 Messages in RabbitMQ's queue was consumed but unacknowledged Change By: rin_ne (29/Jul/14 3:29 AM) Status: In Progress Open This message is automatically generated by JIRA. 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-auth] (JENKINS-20208) Separate privilege of project configuration
Dennys Hsieh
commented on JENKINS-20208
Separate privilege of project configuration
The above patch doesn't work because if user doesn't see the configuration and he submit the configuration, the privilege will be cleared.
This is my current solution
Modify src\main\resources\hudson\security\AuthorizationMatrixProperty\config.jelly
xmlns:j="jelly:core" xmlns:st="jelly:stapler" xmlns:d="jelly:define" xmlns:l="/lib/layout" xmlns:t="/lib/hudson" xmlns:f="/lib/form">
"${h.hasPermission(app.ADMINISTER)}">
"useProjectSecurity" title="${%Enable project-based security}" checked="${instance!=null}" xmlns:local="local">
"hudson.security.GlobalMatrixAuthorizationStrategy" page="config.jelly"/>
"${!h.hasPermission(app.ADMINISTER)}">
"useProjectSecurity" title="${%Enable project-based security}" checked="${instance!=null}" xmlns:local="local">
"hudson.security.GlobalMatrixAuthorizationStrategy" page="config_readonly.jelly"/>
Clone a file from src\main\resources\hudson\security\GlobalMatrixAuthorizationStrategy\config.jelly to config_readonly.jelly
1. Modify line 36 to disable checkbox click
"[${p.id}]" checked="${instance.hasExplicitPermission(attrs.sid,p)}" _onclick_="return false" />
2. Delete line 41~50 to remove button
This message is automatically generated by JIRA.
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-23248) CLI calls are causing file descriptor leaks.
dogfood commented on JENKINS-23248 CLI calls are causing file descriptor leaks. Integrated in jenkins_main_trunk #3560 [FIXED JENKINS-23248] (Revision 5b7d59a71aa01d0c430d98d0b6879c3662a6248b) Result = SUCCESS kohsuke : 5b7d59a71aa01d0c430d98d0b6879c3662a6248b Files : changelog.html pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-pipeline] (JENKINS-21181) Build pipeline creating stack trace after logging on as non-admin user
Anthony Yeong commented on JENKINS-21181 Build pipeline creating stack trace after logging on as non-admin user Same issue encountered with Jenkins 1.571 and plugin 1.4.2 This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-24012) Messages in RabbitMQ's queue was consumed but unacknowledged
rin_ne started work on JENKINS-24012 Messages in RabbitMQ's queue was consumed but unacknowledged Change By: rin_ne (29/Jul/14 1:49 AM) Status: Open In Progress This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-24012) Messages in RabbitMQ's queue was consumed but unacknowledged
rin_ne commented on JENKINS-24012 Messages in RabbitMQ's queue was consumed but unacknowledged When message was consumed, Jenkins made warning in log: org.jenkinsci.plugins.rabbitmqconsumer.channels.ConsumeRMQChannel$MessageConsumer handleDelivery WARN: caught exception in delivery handler java.lang.ClassCastException: com.rabbitmq.client.impl.LongStringHelper$ByteArrayLongString cannot be cast to java.lang.String at com.sonyericsson.hudson.plugins.gerrit.trigger.impls.RabbitMQMessageListenerImpl.onReceive(RabbitMQMessageListenerImpl.java:93) at org.jenkinsci.plugins.rabbitmqconsumer.extensions.MessageQueueListener.fireOnReceive(MessageQueueListener.java:83) at org.jenkinsci.plugins.rabbitmqconsumer.channels.ConsumeRMQChannel$MessageConsumer.handleDelivery(ConsumeRMQChannel.java:135) at com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDispatcher.java:140) at com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable.run(ConsumerWorkService.java:76) 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) This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-24012) Messages in RabbitMQ's queue was consumed but unacknowledged
rin_ne created JENKINS-24012 Messages in RabbitMQ's queue was consumed but unacknowledged Issue Type: Bug Affects Versions: current Assignee: rin_ne Components: gerrit-trigger Created: 29/Jul/14 1:40 AM Description: Using gerrit-trigger with RabbitMQ, messages in consumed queue was received but message itself was not acknowledged. In addition, No triggered jobs Environment: Jenkins 1.509.3 gerrit-trigger 2.12.0-beta-4 Project: Jenkins Priority: Critical Reporter: rin_ne This message is automatically generated by JIRA. 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] [gerrit-trigger] (JENKINS-23883) GERRIT_BRANCH not honoured in gerrit trigger config
rin_ne commented on JENKINS-23883 GERRIT_BRANCH not honoured in gerrit trigger config GERRIT_BRANCH is provided by a event. So it cannot be used before triggering an event. Is it your requirement that "Use my own parameters in branch field"? This message is automatically generated by JIRA. 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-23248) CLI calls are causing file descriptor leaks.
SCM/JIRA link daemon commented on JENKINS-23248 CLI calls are causing file descriptor leaks. Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/5b7d59a71aa01d0c430d98d0b6879c3662a6248b Log: [FIXED JENKINS-23248] Integrated remoting.jar that fixes 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] [cli] (JENKINS-23572) Repeated calls to jenkins cli results in Too many open files exception on the master
Kohsuke Kawaguchi resolved JENKINS-23572 as Duplicate Repeated calls to jenkins cli results in Too many open files exception on the master Duplicate of JENKINS-23248. Change By: Kohsuke Kawaguchi (29/Jul/14 1:03 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23248) CLI calls are causing file descriptor leaks.
Kohsuke Kawaguchi updated JENKINS-23248 CLI calls are causing file descriptor leaks. Updated title to reflect the real problem. Change By: Kohsuke Kawaguchi (29/Jul/14 1:02 AM) Summary: CLI : get-job calls are causing file descriptor leaks. This message is automatically generated by JIRA. 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-23248) CLI: get-job calls are causing file descriptor leaks.
SCM/JIRA link daemon commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ChunkedInputStream.java src/main/java/hudson/remoting/ChunkedOutputStream.java http://jenkins-ci.org/commit/remoting/fc5cf1a6a91d255333eff4ec936d55e5719e773c Log: JENKINS-23248 ChunkcedInputStream.close() wasn't closing the underlying stream This message is automatically generated by JIRA. 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-23248) CLI: get-job calls are causing file descriptor leaks.
SCM/JIRA link daemon resolved JENKINS-23248 as Fixed CLI: get-job calls are causing file descriptor leaks. Change By: SCM/JIRA link daemon (29/Jul/14 1:00 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-23248) CLI: get-job calls are causing file descriptor leaks.
SCM/JIRA link daemon commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/SocketChannelStream.java http://jenkins-ci.org/commit/remoting/c90fc463923cc7f4a8907a0b352204f3d561cc55 Log: [FIXED JENKINS-23248] Seeing strange "Transport endpoint is not connected" exception s.shutdownInput() fails with the following exception, even though s.isInputShutdown() is reporting false: java.net.SocketException: Transport endpoint is not connected at sun.nio.ch.SocketChannelImpl.shutdown(Native Method) at sun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:667) at sun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:378) at hudson.remoting.SocketChannelStream$1.close(SocketChannelStream.java:39) at sun.nio.ch.ChannelInputStream.close(ChannelInputStream.java:113) at javax.crypto.CipherInputStream.close(CipherInputStream.java:296) at java.io.BufferedInputStream.close(BufferedInputStream.java:468) at hudson.remoting.FlightRecorderInputStream.close(FlightRecorderInputStream.java:112) at hudson.remoting.ChunkedInputStream.close(ChunkedInputStream.java:102) at hudson.remoting.ChunkedCommandTransport.closeRead(ChunkedCommandTransport.java:50) at hudson.remoting.Channel.terminate(Channel.java:795) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:951) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) This bug report may be related: http://bugs.java.com/view_bug.do?bug_id=4516760 If we fail to call s.close(), a socket will leak, so swallowing this exception and have the code execute "s.close()" Compare: https://github.com/jenkinsci/remoting/compare/d1905acf329e...c90fc463923c This message is automatically generated by JIRA. 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-23248) CLI: get-job calls are causing file descriptor leaks.
SCM/JIRA link daemon commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/SocketChannelStream.java http://jenkins-ci.org/commit/remoting/6c7d4d110362106cf897fef6485b80dbd3755d4c Log: JENKINS-23248 Making the close method more robust Unlike the usual close() method, shutdownInput/Output throws an exception for the 2nd invocation. It's better to silently do nothing instead of dying with IOException. This message is automatically generated by JIRA. 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-parameter] (JENKINS-23473) empty tags / revisions list when using Folders - NullPointerException - getParentProject()
Steven Christou commented on JENKINS-23473 empty tags / revisions list when using Folders - NullPointerException - getParentProject() I created a pull request to fix 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] [www] (JENKINS-10649) remote api node action: get/set labels
Sam Xiao commented on JENKINS-10649 remote api node action: get/set labels +1 May I know why this important feature is still not implemented? Thanks, Sam. This message is automatically generated by JIRA. 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-7414) Git submodules support does not work with relative url path
Mark Mielke commented on JENKINS-7414 Git submodules support does not work with relative url path Update for the scenario I was looking at: It turns out the job was configured to use "Repository / Name" of something specific to the plan. Once I reset it to "origin" it got past this problem. So, a work-around for people experiencing this problem may be to limit yourself to a "Repository / Name" of "origin"... I still think this is a real problem, in that if you do configure "Repository / Name", then submodules with relative URL break, but at least it isn't critical for us any more... This message is automatically generated by JIRA. 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-23971) NumberFormatException when tailing node log (ssh unix slave, ec2)
Craig Ringer commented on JENKINS-23971 NumberFormatException when tailing node log (ssh unix slave, ec2) Thanks for the tip Daniel. I'm using Chrome 35.0.1916.27 at the moment. I'll keep an eye on the dev console. This message is automatically generated by JIRA. 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-23248) CLI: get-job calls are causing file descriptor leaks.
Kohsuke Kawaguchi commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Confirmed. Based on the output from lsof, TCP connections are leaking. This message is automatically generated by JIRA. 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-23248) CLI: get-job calls are causing file descriptor leaks.
Kohsuke Kawaguchi assigned JENKINS-23248 to Kohsuke Kawaguchi CLI: get-job calls are causing file descriptor leaks. Change By: Kohsuke Kawaguchi (29/Jul/14 12:03 AM) Assignee: Kohsuke Kawaguchi This message is automatically generated by JIRA. 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-parameter] (JENKINS-23473) empty tags / revisions list when using Folders - NullPointerException - getParentProject()
Steven Christou commented on JENKINS-23473 empty tags / revisions list when using Folders - NullPointerException - getParentProject() The problem is GitParameterDefinition.java#L186. According to the documentation for Jenkins.getItems, it states that it gets just the immediate children of Jenkins, which would fail with folders. This message is automatically generated by JIRA. 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-23248) CLI: get-job calls are causing file descriptor leaks.
Kanstantsin Shautsou commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. It maybe useful to wrote a test case and run automated bisect http://java.dzone.com/articles/automated-bug-finding-git ... This message is automatically generated by JIRA. 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-23971) NumberFormatException when tailing node log (ssh unix slave, ec2)
Daniel Beck commented on JENKINS-23971 NumberFormatException when tailing node log (ssh unix slave, ec2) If this happens fairly often (what web browser(s)?), try to keep the web developer console open, logging all requests. The following happens when viewing the log of a build in progress/slave log/promotion log: The browser sends AJAX requests to Jenkins with the POST parameter 'start' to only load data that hasn't been received yet. Jenkins response contains a HTTP header named 'X-Text-Size' which serves as the new starting point The cause for the issue is a garbled value sent by the client (it appears to be two values concatenated). It would be interesting to see where it goes wrong, so if it happens, check the log of past requests. Is it first the client to fail, or the server? This message is automatically generated by JIRA. 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-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) no, i don't, this is what i have in the logs verbatim. the same 5 blocks of messages/traces appear together a few times in the jenkins logs. This message is automatically generated by JIRA. 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-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect Very interesting. Can you attach the job definition of the job which shows that behavior (~jenkins/jobs//config.xml) and the steps you used to create that job? The source code definitely refers to "commits" rather than "commit". This message is automatically generated by JIRA. 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-23971) NumberFormatException when tailing node log (ssh unix slave, ec2)
Scott Roberts commented on JENKINS-23971 NumberFormatException when tailing node log (ssh unix slave, ec2) We're running Jenkins version 1.564 and we just saw this for the first time today as well. Error while serving http://build.rctanalytics.com/job/Connection%20Broker/41/promotion/Production/promotionBuild/6/logText/progressiveHtml ... Caused by: java.lang.NumberFormatException: For input string: "1251start=24" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Long.parseLong(Long.java:438) at java.lang.Long.parseLong(Long.java:478) at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:256) at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:91) Our version is 1.564, but we have updated plugins if those might be the cause: Active Directory plugin This plugin enables authentication through Active Directory on Windows environment. 1.38 Downgrade to 1.37 Ant Plugin This plugin adds Apache Ant support to Jenkins. 1.2 Artifactory Plugin This plugin allows deploying maven artifacts and build info to Artifactory. 2.2.3 Downgrade to 2.2.1 Copy Artifact Plugin Adds a build step to copy artifacts from another project. 1.31 Downgrade to 1.30 Credentials Plugin This plugin allows you to store credentials in Jenkins. 1.15 Downgrade to 1.15 Unpin CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.12 Downgrade to 2.11 Unpin Deploy to container Plugin This plugin allows you to deploy a war to a container after a successful build. Glassfish 3.x remote deployment 1.10 Downgrade to 1.9 External Monitor Job Type Plugin Adds the ability to monitor the result of externally executed jobs. 1.2 Downgrade to 1.1 Unpin GIT client plugin Shared library plugin for other Git related Jenkins plugins. 1.10.0 Downgrade to 1.9.2 GIT plugin This plugin integrates GIT with Jenkins. 2.2.2 Downgrade to 2.2.1 Git server plugin Allows Jenkins to act as a Git server. 1.3 Downgrade to 1.2 Gradle plugin This plugin allows Jenkins to invoke Gradle build scripts directly. 1.24 Downgrade to 1.23 Grails plugin This plugin supports building Grails applications from Jenkins. 1.7 Hudson Groovy builder This plugin executes Groovy code. 1.19 Downgrade to 1.18 instant-messaging plugin This plugin provides abstract support for build notification via instant-messaging. 1.29 Downgrade to 1.28 Jabber notifier plugin Sends build notifications to jabber contacts and/or chatrooms. Also allows control of builds via a jabber 'bot'. Note that the instant-messaging plugin 1.24 is a requirement for this plugin. Please make sure that it is installed, too! 1.25 Javadoc Plugin This plugin adds Javadoc support to Jenkins. 1.1 LDAP Plugin Security realm based on LDAP authentication. 1.10.2 Downgrade to 1.8 Unpin Mailer Plugin This plugin allows you to configure email notifications. This is a break-out of the original core based email component. 1.9 Downgrade to 1.8 Unpin MapDB API Plugin This plugin provides a shared dependency on the MapDB library so that other plugins can co-operate when using this library. 1.0.1.0 Matrix Authorization Strategy Plugin Offers matrix-based security authorization strategies (global and per-project). 1.2 Downgrade to 1.1 Unpin Matrix Project Plugin Multi-configuration (matrix) project type. 1.3 Downgrade to 1.2 Unpin Maven Integration plugin Jenkins plugin for building Maven 2/3 jobs via a special project type. 2.5 Downgrade to 2.3 Unpin OWASP Markup Formatter Plugin Uses the OWASP Java HTML Sanitizer to allow safe-seeming HTML markup to be entered in project descriptions and the like. 1.2 Downgrade to 1.1 Unpin PAM Authentication plugin Adds Unix Pluggable Authentication Module (PAM) support to Jenkins. 1.1 Downgrade to 1.0 Unpin promoted builds plugin This plugin implements a "promoted build" feature where a build of one job can be marked as "promoted" when it passes certain criteria. 2.17 Downgrade to 2.13 S3 publisher plugin This is a plugin to upload files to Amazon S3 buckets. 0.6 Downgrade to 0.5 SCM API Plugin This plugin provides a new enhanced API for interacting with SCM systems. 0.2 Scriptler Scriptler allows you to store/edit/execute groovy scripts on any of the slaves/nodes... no need for copy paste groovy code anymore. Beside administer your scripts, Scritpler also pro
[JIRA] [warnings] (JENKINS-24011) Filtering of compiler warnings by regexp not working well
jpschewe created JENKINS-24011 Filtering of compiler warnings by regexp not working well Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 28/Jul/14 9:49 PM Description: I see that under the advanced section of the compiler warnings module there is an option to ignore files based on their absolute file path. I have a directory at the top of my workspace named "log4cxx/source". I don't want to be notified of any warnings in that directory. The warnings are found in the console output. I have tried the following filters, all without success log4cxx/source ./log4cxx/source/. log4cxx/source/** When I look at the compiler output I see output like this: 14:45:01 /bin/sh /d/workspace-jnlp/workspace/log4cxx/label/windigo-jnlp/log4cxx/source/apr-1.4.6/libtool --silent --mode=compile gcc -g -O2 -DHAVE_CONFIG_H -DWIN32 -D_MSVCRT_ -D_LARGEFILE64_SOURCE -I./include -I/d/workspace-jnlp/workspace/log4cxx/label/windigo-jnlp/log4cxx/source/apr-1.4.6/include/arch/win32 -I./include/arch/unix -I/d/workspace-jnlp/workspace/log4cxx/label/windigo-jnlp/log4cxx/source/apr-1.4.6/include/arch/unix -I/d/workspace-jnlp/workspace/log4cxx/label/windigo-jnlp/log4cxx/source/apr-1.4.6/include -o atomic/win32/apr_atomic.lo -c atomic/win32/apr_atomic.c && touch atomic/win32/apr_atomic.lo 14:45:01 atomic/win32/apr_atomic.c:31:5: warning: 'dllimport' attribute ignored [-Wattributes] 14:45:01 (apr_uint32_t volatile *); 14:45:01 ^ 14:45:01 atomic/win32/apr_atomic.c:34:6: warning: 'dllimport' attribute ignored [-Wattributes] 14:45:01 apr_uint32_t); 14:45:01 ^ 14:45:01 atomic/win32/apr_atomic.c:37:6: warning: 'dllimport' attribute ignored [-Wattributes] 14:45:01 apr_uint32_t, apr_uint32_t); 14:45:01 ^ 14:45:01 atomic/win32/apr_atomic.c:40:6: warning: 'dllimport' attribute ignored [-Wattributes] 14:45:01 void *, const void *); 14:45:01 ^ 14:45:01 atomic/win32/apr_atomic.c:43:6: warning: 'dllimport' attribute ignored [-Wattributes] 14:45:01 void *); 14:45:01 ^ If I list "atomic/win32/apr_atomic.c" in the excludes, then these warnings are ignored by the warnings plugin. However I would much rather be able to specify "./log4cxx/source/." to make sure I only exclude warnings from that subdirectory. The full path information must be available because the links that the plugin creates for the warnings link to the actual file in the workspace. I'm using Jenkins 1.532.2 with Warnings plugin 4.39. Environment: Jenkins 1.532.2 with Warnings plugin 4.39 Project: Jenkins Priority: Major Reporter: jpschewe This message is automatically generated by JIRA. 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] [github-oauth] (JENKINS-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'
Matthew Thode created JENKINS-24010 github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' Issue Type: Improvement Affects Versions: current Assignee: Sam Kottler Components: github-oauth Created: 28/Jul/14 9:30 PM Description: We have private repos and currently the only way to use the buildstatus plugin is to allow read to anonymous. This means that anyone can read the work dir for instance. What I'd like to see is another option to allow Anonymous access to just the ViewStatus permission Project: Jenkins Priority: Major Reporter: Matthew Thode This message is automatically generated by JIRA. 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-reloaded] (JENKINS-24009) Incorrect result status after Matrix rebuild
Bruno Meneguello updated JENKINS-24009 Incorrect result status after Matrix rebuild Change By: Bruno Meneguello (28/Jul/14 9:16 PM) Assignee: Nicolas De Loof Praqma Support Component/s: matrix-reloaded Component/s: naginator This message is automatically generated by JIRA. 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] [naginator] (JENKINS-24009) Incorrect result status after Matrix rebuild
Bruno Meneguello created JENKINS-24009 Incorrect result status after Matrix rebuild Issue Type: Bug Assignee: Nicolas De Loof Components: naginator Created: 28/Jul/14 9:13 PM Description: When rebuilding a matrix job, if some configurations result are "UNSTABLE" or "FAILED" but are not selected for rebuild, and the selected ones finished with "SUCCESS", the build result become "SUCCESS" even with non successful configurations. I think the new build should be never better then the worst result of non run status of original build. Project: Jenkins Priority: Major Reporter: Bruno Meneguello This message is automatically generated by JIRA. 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-23248) CLI: get-job calls are causing file descriptor leaks.
Carl Molinari edited a comment on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. We are seeing an issue when calls to the jenkins-cli.jar from node leave a socket open each time it is called. We use these calls to update the external resource plugin and this can lead to hundreds of file descriptors leaked every day. The only way to free them up is to restart Jenkins. lsof shows the unclosed socket as: java 4222 tomcat6 804u sock0,60t0 230747605 can't identify protocol This is with Version 1.573 This message is automatically generated by JIRA. 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-23248) CLI: get-job calls are causing file descriptor leaks.
Carl Molinari commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. We are seeing an issue when calls to the jenkins-cli.jar from node leave a socket open each time it is called. We use these calls to update the external resource plugin and this can lead to hundreds of file descriptors leaked every day. The only way to free them up is to restart Jenkins. lsof shows the unclosed socket as: java 4222 tomcat6 804u sock0,60t0 230747605 can't identify protocol This message is automatically generated by JIRA. 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-24008) Jobs stuck while waiting for an executor (and executors are available)
Daniel Beck commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) Do you have strack traces for the SEVERE messages? This message is automatically generated by JIRA. 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] [tap] (JENKINS-23296) TAP Plugin not communicating with other plugins
Bruno P. Kinoshita commented on JENKINS-23296 TAP Plugin not communicating with other plugins No worries, it is really confusing. The plug-in itself started with TAP and a custom interface. Later, after user requests, we added support to Jenkins built-in Test Results pages. Some of the methods/classes you're looking at were (probably) adapted from the TestNG plug-in, and others were part of the old codebase. I'll leave the issue open and will try to find a way to make code simpler. Feel free to comment here too if you have any suggestions. All the best Bruno This message is automatically generated by JIRA. 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-7414) Git submodules support does not work with relative url path
Mark Mielke commented on JENKINS-7414 Git submodules support does not work with relative url path I just looked into this and here is what I found: If you use "git clone" it works fine. However, if I follow the exact sequence that Jenkins does, it fails. This is because of two things working against us: 1) Jenkins is running "git fetch", but Jenkins is not configuring HEAD to point to a real branch at this point of the execution. 2) Jenkins is using a remote name other than "origin". The implementation of "git submodule init" does this with relative URL: 1) If the URL begins with "./" or "../" it will "resolve relative" as defined in the documentation. 2) To resolve relative, it must determine which "remote" to resolve relative to. 2a) If HEAD is set up, then it looks for the remote tracking branch that HEAD is configured against and uses that remote. 2b) If HEAD is not set up, it uses "origin". So, for most cases it "just works", but in Jenkins, it fails. This is particularly problematic for us as we use both http:// and ssh:// as per designer requirements, and having a submodule that is absolute means that half the designers must use both mechanisms for authentication and we have to choose which ones will "lose". If we could do relative, then it would just use whatever the designer was already using. This works fine from the development environment because the above algorithm generally works. But this configuration fails under Jenkins which makes it a serious problem as if we use the configuration that works for designers, we lose continuous integration builds, or if we use the configuration that works for Jenkins, we upset half the designers. Not a great state to be in... This message is automatically generated by JIRA. 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] [tap] (JENKINS-23296) TAP Plugin not communicating with other plugins
andrew cooke commented on JENKINS-23296 TAP Plugin not communicating with other plugins i am trapped in a twisty maze of classes that all look alike! getResult() returns an Object :o( the other code i am working with returns a subclass of MetaTabulatedResult at that point, whose getFailedTests() returns subclasses of TestResult. TapStreamResult also returns TestResults. so i think things may be consistent? i don't have a patch. we did consider it, but decided it was better to test and handle the code (sorry - short term time pressure). This message is automatically generated by JIRA. 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-21309) Git plugins changes URL for Bitbucket is incorrect
John Dyer edited a comment on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect I am running the latest git and git-client plugin as of today and I still see this problem w/ Bitbucket. just to reiterate the problem is the URL for the commit should be plural, not signaler Current behavior ( incorrect ) http://bitbucket.org/user/project/commit/025e42c873c49b17450c5c10e97e5904d5a9cc2d Expected behavior http://bitbucket.org/user/project/commits/025e42c873c49b17450c5c10e97e5904d5a9cc2d This message is automatically generated by JIRA. 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
SCM/JIRA link daemon commented on JENKINS-17742 Pick Up Committer from Upstream Job Code changed in jenkins User: Christian Galsterer Path: src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java src/main/resources/hudson/plugins/emailext/Messages.properties http://jenkins-ci.org/commit/email-ext-plugin/dacc3e212cd4c95493b5060c2ae07a4885b7eb81 Log: JENKINS-17742 - Pick Up Committer from Upstream Job I18N for display name This message is automatically generated by JIRA. 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
SCM/JIRA link daemon commented on JENKINS-17742 Pick Up Committer from Upstream Job Code changed in jenkins User: Christian Galsterer Path: src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java http://jenkins-ci.org/commit/email-ext-plugin/56896689098d61a3aa79a1f54dff802f26388ff6 Log: JENKINS-17742 - Pick Up Committer from Upstream Job fixed review comments (logging and spacing) This message is automatically generated by JIRA. 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
SCM/JIRA link daemon commented on JENKINS-17742 Pick Up Committer from Upstream Job Code changed in jenkins User: Christian Galsterer Path: src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java src/main/resources/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider/help.html http://jenkins-ci.org/commit/email-ext-plugin/763ecc19519e6d14b35e0be4150f55d99a028850 Log: JENKINS-17742 - Pick Up Committer from Upstream 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
SCM/JIRA link daemon commented on JENKINS-17742 Pick Up Committer from Upstream Job Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java src/main/resources/hudson/plugins/emailext/Messages.properties src/main/resources/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider/help.html http://jenkins-ci.org/commit/email-ext-plugin/58f0a1ef125a361fc9045e05c93b1053932dc337 Log: Merge pull request #91 from christiangalsterer/JENKINS-17742 JENKINS-17742 - Pick Up Committer from Upstream Job Compare: https://github.com/jenkinsci/email-ext-plugin/compare/bfaadca29e5b...58f0a1ef125a This message is automatically generated by JIRA. 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
SCM/JIRA link daemon commented on JENKINS-17742 Pick Up Committer from Upstream Job Code changed in jenkins User: Christian Galsterer Path: src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java http://jenkins-ci.org/commit/email-ext-plugin/303a15e7fe2da246500cec32623b8b858cdbfe57 Log: JENKINS-17742 - Pick Up Committer from Upstream Job fixed review comments (logging and spacing) This message is automatically generated by JIRA. 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-21309) Git plugins changes URL for Bitbucket is incorrect
John Dyer reopened JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect I am running the latest git and git-client plugin as of today and I still see this problem w/ Bitbucket. just to reiterate the problem is the URL for the commit should be plural, not signaler Current behavior ( incorrect ) http://bitbucket.org/voxeolabs/user/project/commit/025e42c873c49b17450c5c10e97e5904d5a9cc2d Expected behavior http://bitbucket.org/user/project/commits/025e42c873c49b17450c5c10e97e5904d5a9cc2d Change By: John Dyer (28/Jul/14 8:40 PM) Resolution: Fixed Status: Closed 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
SCM/JIRA link daemon commented on JENKINS-17742 Pick Up Committer from Upstream Job Code changed in jenkins User: Christian Galsterer Path: src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java src/main/resources/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider/help.html http://jenkins-ci.org/commit/email-ext-plugin/f44a742850de3f133124612dd155a924e4115303 Log: JENKINS-17742 - Pick Up Committer from Upstream 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
SCM/JIRA link daemon commented on JENKINS-17742 Pick Up Committer from Upstream Job Code changed in jenkins User: Christian Galsterer Path: src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java http://jenkins-ci.org/commit/email-ext-plugin/b87a57e244752fe1b9ac965f044b39d96d755862 Log: JENKINS-17742 - Pick Up Committer from Upstream Job fixed review comment on display name This message is automatically generated by JIRA. 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
SCM/JIRA link daemon commented on JENKINS-17742 Pick Up Committer from Upstream Job Code changed in jenkins User: Christian Galsterer Path: http://jenkins-ci.org/commit/email-ext-plugin/4b19e9bfd1ce3d59975be52fd9287793408a2d1a Log: JENKINS-17742 - Pick Up Committer from Upstream Job I18N for display name src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-10567) Error which serving history ajax
Damien Nozay commented on JENKINS-10567 Error which serving history ajax ok, opened JENKINS-24008. This message is automatically generated by JIRA. 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-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay created JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 28/Jul/14 8:32 PM Description: I have some similar trace as JENKINS-10567 (may or may not be related) there are about 10 items queued in /job/runtest/job/DevPrecheckin/: they are all waiting for the same slave (job tied to the slave) the slave has 8 free executors all 10 items are stuck. after removing the first few queued item, was able to recover. I am using the LTS version 1.554.3, and can provide more details upon request (mostly because of sensitive info I would need to scrub). Jul 28, 2014 12:09:41 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: item.getCauseOfBlockage() in /job/runtest/job/DevPrecheckin/buildHistory/ajax. Reason: java.lang.NullPointerException java.lang.NullPointerException Jul 28, 2014 12:09:41 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: item.params in /job/runtest/job/DevPrecheckin/buildHistory/ajax. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) 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 org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) a
[JIRA] [tap] (JENKINS-23296) TAP Plugin not communicating with other plugins
Bruno P. Kinoshita commented on JENKINS-23296 TAP Plugin not communicating with other plugins Hiya Andrew! Sorry for not giving any feedback on this. I've been busy with $work projects and couldn't really push any changes in Jenkins plug-ins. I think I put that getFailedTests2() because I didn't find a simple way to convert a TestResult into a CaseResult? Not sure tho. If you can send a pull request or have any advice on which is the simplest way to fix it that you imagine, I can try to push a new release this week - I'll have meetings/releases till Thursday, but Friday I want to work on some open source stuff. Sorry again Andrew Bruno This message is automatically generated by JIRA. 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] [tap] (JENKINS-23296) TAP Plugin not communicating with other plugins
andrew cooke commented on JENKINS-23296 TAP Plugin not communicating with other plugins Hi. Some more info on this. I have worked around the issue by checking the type returned from AbstractBuild.getResult() and, if it's an instance of TapStreamResult, calling getFailedTests2() instead of getFailedTests(). I have absolutely no idea why you're implementing getFailedTests() to return an empty list! That's how it's implemented in the base class, sure, but other plugins over-ride that to return their results. Anyway, that's the basic issue. I'm no longer waiting on a fix as I have the work-around above. Maybe there's an explanation that I'm missing. Hope this helps. Cheers, Andrew This message is automatically generated by JIRA. 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] [groovy-postbuild] (JENKINS-15210) Add variable resolution to "additional groovy class path"
Kevin Trizna commented on JENKINS-15210 Add variable resolution to "additional groovy class path" I am a contributor to this plugin who plays a slightly smaller role than most, but I see how I could go about coding this. Assuming nobody else has picked this up, I'll go ahead and sponsor 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] [core] (JENKINS-24000) Jenkins $WORKSPACE variable override project internal properties "workspace"
Daniel Beck resolved JENKINS-24000 as Won't Fix Jenkins $WORKSPACE variable override project internal properties "workspace" Either change would be a severe regression in any existing installation relying on the current behavior, so is out of the question. Therefore closing this as Won't Fix. That said, it may depend on how you launch your Maven build: Is it a Maven project? A Maven build step in a freestyle project? What happens when you switch to the other? For advice on how to configure your project, please try IRC or the jenkinsci-users mailing ist. Change By: Daniel Beck (28/Jul/14 7:49 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. 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-24000) Jenkins $WORKSPACE variable override project internal properties "workspace"
Daniel Beck updated JENKINS-24000 Jenkins $WORKSPACE variable override project internal properties "workspace" Change By: Daniel Beck (28/Jul/14 7:46 PM) Component/s: core Component/s: build-environment This message is automatically generated by JIRA. 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-10567) Error which serving history ajax
Daniel Beck resolved JENKINS-10567 as Incomplete Error which serving history ajax Damien: Please file a new issue. It doesn't look like yours has anything to do with this one except where it surfaces. Change By: Daniel Beck (28/Jul/14 7:44 PM) Status: Reopened Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6268) Make checking for modification time of junit results be configurable and off by default
n0mer commented on JENKINS-6268 Make checking for modification time of junit results be configurable and off by default Possible workaround for Gradle: http://www.practicalgradle.org/blog/2011/06/incremental-tests-with-jenkins/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23980) Xvfb doesn't remove /tmp/.X-* locks after a build has finished
zregvart commented on JENKINS-23980 Xvfb doesn't remove /tmp/.X-* locks after a build has finished Hi Stefan, so the executor numbers are assigned on demand from a pool of numbers, the logic behind that is pretty clear here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Computer.java#L715 And from that indeed the number can differ from the one shown in the table, as you have stipulated, I have reproduced this by increasing the number of executors and running consecutive builds. In my case the executor number shown in the UI was 5, and the display number was based on the executor numbered 2 – so the display number was 3. But that still generates unique display numbers with the assumption that the range of display numbers from the minimum to the maximum executor number plus the offset is free for Xvfb to use. That is, no other X servers are using those numbers, no other slaves are run on that physical machine, and that there are no leftover Xvfb processes. This is guaranteed by the way Jenkins adds the executors to the executor list – no executor numbers are reused, as can be seen in the linked 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] [core] (JENKINS-10567) Error which serving history ajax
Damien Nozay reopened JENKINS-10567 Error which serving history ajax I have some similar issue. there are about 10 items queued in /job/runtest/job/DevPrecheckin/ they are all waiting for the same slave (job tied to the slave) the slave has 8 free executors all 10 items are stuck. after removing the first few queued item, was able to recover. I am using the LTS version 1.554.3, and can provide more details upon request (mostly because of sensitive info I would need to scrub). Jul 28, 2014 12:09:21 PM SEVERE hudson.triggers.SafeTimerTask run Timer task hudson.model.Queue$MaintainTask@34a07387 failed java.lang.NullPointerException Jul 28, 2014 12:09:24 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: item.getCauseOfBlockage() in /job/runtest/job/DevPrecheckin/buildHistory/ajax. Reason: java.lang.NullPointerException java.lang.NullPointerException Jul 28, 2014 12:09:24 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: item.params in /job/runtest/job/DevPrecheckin/buildHistory/ajax. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) 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 org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTa
[JIRA] [cppcheck] (JENKINS-24007) Put a warning about report in legacy format to build log
Michal Turek resolved JENKINS-24007 as Fixed Put a warning about report in legacy format to build log Implemented, will be released in version 1.20. Change By: Michal Turek (28/Jul/14 7:22 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-24007) Put a warning about report in legacy format to build log
SCM/JIRA link daemon commented on JENKINS-24007 Put a warning about report in legacy format to build log Code changed in jenkins User: Michal Turek Path: src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckParserResult.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckResult.java src/main/java/org/jenkinsci/plugins/cppcheck/parser/CppcheckParser.java http://jenkins-ci.org/commit/cppcheck-plugin/61e07237bdd4376e216d857ed32d3bdc8a6be3d7 Log: Merge pull request #22 from mixalturek/master JENKINS-24007 Put a warning about report in legacy format to build log Compare: https://github.com/jenkinsci/cppcheck-plugin/compare/756ed9454c66...61e07237bdd4 This message is automatically generated by JIRA. 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-24007) Put a warning about report in legacy format to build log
SCM/JIRA link daemon commented on JENKINS-24007 Put a warning about report in legacy format to build log Code changed in jenkins User: Michal Turek Path: src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckParserResult.java src/main/java/org/jenkinsci/plugins/cppcheck/parser/CppcheckParser.java http://jenkins-ci.org/commit/cppcheck-plugin/5e25a2934af8f15e1d1f7b5c00a21fe75f6052fd Log: JENKINS-24007 Put a warning about report in legacy format to build log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek closed JENKINS-23185 as Fixed Setting build status to FAILURE for new error when errors were fixed Change By: Michal Turek (28/Jul/14 7:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23575) Post-Build-Step "Publish Cppcheck results" not available in job generator project
Michal Turek closed JENKINS-23575 as Fixed Post-Build-Step "Publish Cppcheck results" not available in job generator project Change By: Michal Turek (28/Jul/14 7:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek closed JENKINS-23888 as Fixed Add query parameter support for filtering errors based on new, resolved or unchanged Change By: Michal Turek (28/Jul/14 7:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23891) Redesign of configuration page
Michal Turek closed JENKINS-23891 as Fixed Redesign of configuration page Change By: Michal Turek (28/Jul/14 7:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-17450) "warning" and "performance" not counted
Michal Turek commented on JENKINS-17450 "warning" and "performance" not counted Simple but great idea, JENKINS-24007 created, thanks This message is automatically generated by JIRA. 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] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Kevin Browder commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted My feeling is that this happens for us if we power off a JNLP slave in an ungraceful way (eg pull the virtual power plug), however it doesn't seem to happen every time, again this is similar to Patricia's case. Actually, I'm a bit surprised this doesn't happen at CloudBees since FWIU is that they've got dynamic provisioned VMs too; or maybe they use the LTS? Anyways I'll try to grab the jenkins logs the next time this happens. This message is automatically generated by JIRA. 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-24007) Put a warning about report in legacy format to build log
Michal Turek created JENKINS-24007 Put a warning about report in legacy format to build log Issue Type: New Feature Affects Versions: current Assignee: Michal Turek Components: cppcheck Created: 28/Jul/14 7:06 PM Description: If '--xml-version=2' is not passed to Cppcheck, it will generate the report in legacy format. Build log should contain a warning about that to inform the user. --xml Write results in XML to error stream --xml-version= Select the XML file version. Currently versions 1 and 2 are available. The default version is 1. Environment: All Project: Jenkins Priority: Trivial Reporter: Michal Turek This message is automatically generated by JIRA. 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-failure-analyzer] (JENKINS-16868) Icons are not displayed with a reverse proxy
Walter Kacynski commented on JENKINS-16868 Icons are not displayed with a reverse proxy I used this mod_rewrite rule to add in the mapping for /jenkins/jenkins RewriteRule ^/jenkins/jenkins/(.*)$ http://TSTJENK001.:8080/jenkins/$1 [P] This message is automatically generated by JIRA. 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-failure-analyzer] (JENKINS-16868) Icons are not displayed with a reverse proxy
Patrick Roberts commented on JENKINS-16868 Icons are not displayed with a reverse proxy I am also experiencing the double /jenkins/ path and my Jenkins is installed at http://leeroy.centtech.com/jenkins/ this is of course breaking the images. Is there a interim fix for 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] [junit] (JENKINS-24006) Customize number of Junit test failures that affect weather
Mark Sinclair created JENKINS-24006 Customize number of Junit test failures that affect weather Issue Type: Improvement Assignee: Unassigned Components: junit Created: 28/Jul/14 6:30 PM Description: Currently if 20% or more of tests fail, the weather for a project will be downgraded (cloudy). Some users have a large number of tests and one test failure is a major issue. The request is to allow customization of the % of Junit test failures that will cause a weather downgrade. Users that specify 100% pass require all tests to pass to maintain sunny weather. Project: Jenkins Priority: Minor Reporter: Mark Sinclair This message is automatically generated by JIRA. 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-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek commented on JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed You are welcome This message is automatically generated by JIRA. 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] [clover] (JENKINS-23055) Allow Parameter interpolation for Clover path and file name
Ken Beal commented on JENKINS-23055 Allow Parameter interpolation for Clover path and file name This was fixed in the TestNG plugin fairly quickly. Could that code be reused, possibly? I'd like to put up $20 towards fixing this, but I'm not sure how to go about doing that. This message is automatically generated by JIRA. 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] [mask-passwords] (JENKINS-12502) Variable with consecutive dollar characters not displayed as expected: One doller char is dropped
Doug Stewart commented on JENKINS-12502 Variable with consecutive dollar characters not displayed as expected: One doller char is dropped I am experiencing the same issue. Is there any way around 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] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion
Ryan Hummer
created JENKINS-24005
Pin build at Perforce Label does not support variable expansion
Issue Type:
Bug
Affects Versions:
current
Assignee:
Paul Allen
Components:
p4
Created:
28/Jul/14 5:21 PM
Description:
The 'Pin build at Perforce Label' field does not support expanding ${variables}.
The other Perforce plugin supports this, and we use this quite heavily with some of our buillds. Where we use an input parameter to the job to specify the label to watch. Or to re-kick a build at a specific changelist or if the label is empty the build is ran against #head.
Project:
Jenkins
Priority:
Major
Reporter:
Ryan Hummer
This message is automatically generated by JIRA.
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-24004) dev and main branch versions are out of sync
dan tran created JENKINS-24004 dev and main branch versions are out of sync Issue Type: Task Affects Versions: current Assignee: Unassigned Components: p4 Created: 28/Jul/14 4:40 PM Description: dev is at 1.0.5-SNAPSHOT and main is at 1.0.7-SNAPSHOT this is minor, but annoying since I had to manually edit it at my jenkins job Project: Jenkins Priority: Trivial Reporter: dan tran This message is automatically generated by JIRA. 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
dan tran commented on JENKINS-23890 Error on build with SCM changes unfortunately, the issue is still around in my env. yours works? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23881) Too much changelog
dan tran commented on JENKINS-23881 Too much changelog works for me This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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
dan tran commented on JENKINS-23974 Private maven repo got wipe out every build your suggestion works This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24003) Unable to wipe out workspace
dan tran updated JENKINS-24003 Unable to wipe out workspace Change By: dan tran (28/Jul/14 3:41 PM) Description: looks like perforce set the source as readonly and there fore Jenkins is not able to remove themI endedup ended up the manually remove the workspace from command line here is jenkins errorError: Wipe Out Workspace blocked by SCMThe SCM for this project has blocked this attempt to wipe out the project's workspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-24003) Unable to wipe out workspace
dan tran created JENKINS-24003 Unable to wipe out workspace Issue Type: Bug Assignee: Unassigned Components: p4 Created: 28/Jul/14 3:39 PM Description: looks like perforce set the source as readonly and there fore Jenkins is not able to remove them I endedup the manually remove the workspace from command line Environment: jenkins:1.573, p4jenkens: latest snapshot Project: Jenkins Priority: Major Reporter: dan tran This message is automatically generated by JIRA. 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] [rbenv] (JENKINS-24002) Rbenv plugin fails to remove .rbenv.lock
Joseph Hughes commented on JENKINS-24002 Rbenv plugin fails to remove .rbenv.lock https://github.com/jenkinsci/rbenv-plugin/pull/29 This message is automatically generated by JIRA. 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] [rbenv] (JENKINS-24002) Rbenv plugin fails to remove .rbenv.lock
Joseph Hughes created JENKINS-24002 Rbenv plugin fails to remove .rbenv.lock Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: rbenv Created: 28/Jul/14 2:52 PM Description: In some situations the following command is executed to remove .rbenv.lock bash -c "rmdir \$HOME/.rbenv.lock" This command fails if .rbenv.lock does not exist. I believe a more robust solution would be to use bash -c "rm -rf \$HOME/.rbenv.lock" which will remove the directory if it exists and carry on if it does not. Environment: Ubuntu 14.04 Project: Jenkins Labels: plugin Priority: Minor Reporter: Joseph Hughes This message is automatically generated by JIRA. 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-19222) Update to 1.527 breaks ${NODE_NAME} as node parameter on master
Daniel Beck
commented on JENKINS-19222
Update to 1.527 breaks ${NODE_NAME} as node parameter on master
Is anyone here experiencing this specific problem on recent Jenkins versions and doesn't have env-inject installed? Otherwise this should probably be reassigned to the envinject component.
This message is automatically generated by JIRA.
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] [xvfb] (JENKINS-23980) Xvfb doesn't remove /tmp/.X-* locks after a build has finished
Stefan Schultz updated JENKINS-23980 Xvfb doesn't remove /tmp/.X-* locks after a build has finished This is my job running on executor #10 Change By: Stefan Schultz (28/Jul/14 2:42 PM) Attachment: executor_history.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23980) Xvfb doesn't remove /tmp/.X-* locks after a build has finished
Stefan Schultz updated JENKINS-23980 Xvfb doesn't remove /tmp/.X-* locks after a build has finished This is the display name i get Change By: Stefan Schultz (28/Jul/14 2:43 PM) Attachment: executor_number.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23980) Xvfb doesn't remove /tmp/.X-* locks after a build has finished
Stefan Schultz commented on JENKINS-23980 Xvfb doesn't remove /tmp/.X-* locks after a build has finished That is what I assumed at first but as I mentioned before when the job gets executed by executor (slot) #10 it results in a display number 13 but I only set an offset of 1. Another time I got display :7 on slot #10. So the same slot gets me different executor number. I saw your code and you just get the executor number, so I'm guessing this is happens in the Executor code (if it is a problem at all). I'm attaching 2 more screenshots. This message is automatically generated by JIRA. 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] [xvfb] (JENKINS-23980) Xvfb doesn't remove /tmp/.X-* locks after a build has finished
zregvart commented on JENKINS-23980 Xvfb doesn't remove /tmp/.X-* locks after a build has finished Stefan, executor numbers are the numbers that appear to the left of the job name in the example screenshot that would be the number 1. That executor is running a job called test that was built three times before, and hence it got the build number 4. The build number has no consequence on the Xvfb display number. This message is automatically generated by JIRA. 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] [xvfb] (JENKINS-23980) Xvfb doesn't remove /tmp/.X-* locks after a build has finished
zregvart updated JENKINS-23980 Xvfb doesn't remove /tmp/.X-* locks after a build has finished executor status screenshot Change By: zregvart (28/Jul/14 2:28 PM) Attachment: Screen Shot 2014-07-28 at 16.27.17.png This message is automatically generated by JIRA. 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] [perforce] (JENKINS-20124) Unable to sync to perforce on a MAC
Rob Petti commented on JENKINS-20124 Unable to sync to perforce on a MAC Feel free to close any other issues you feel should be closed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [perforce] (JENKINS-20124) Unable to sync to perforce on a MAC
Rob Petti resolved JENKINS-20124 as Not A Defect Unable to sync to perforce on a MAC Change By: Rob Petti (28/Jul/14 2:16 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. 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.
