[JIRA] [artifactory-plugin] (JENKINS-23794) Artifactory Plugin guava dependency problem
Title: Message Title Sven K commented on JENKINS-23794 Re: Artifactory Plugin guava dependency problem The Problem still persists. (Jenkins LTS 1.616, Maven Plugin 2.12, Artifactory Plugin 2.3.1) In gradle, this workaround works https://github.com/JFrogDev/build-info/issues/39 but it would certainly be nicer if it could be solved on the Jenkins-side/Artifactory-Plugin-side. Are there any news/fixes for this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29909) New method to force setResult
Title: Message Title Jochen A. Fürbacher commented on JENKINS-29909 Re: New method to force setResult I know that there are many other job types. Unfortunately using some of them would result in a very big complexity. So if this method won't get integrated in the official jenkins branch, we have to create our own jenkins fork with this method. That would be very sad, even though this one additonal method wouldn't hurt anyone. People using that forced method should know what they do. Especially when there's a "force" infix in the name. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [active-directory-plugin] (JENKINS-28857) "Automatic" group lookup strategy is not so automatic
Title: Message Title Karthik Durairajan commented on JENKINS-28857 Re: "Automatic" group lookup strategy is not so automatic Hey guys, Just stumbled across this page by chance. I've been trying to resolve this issue but with no luck so far. As frustrating as it is, the issue is intermittent and there doesn't appear to be a pattern (at least not that I know of). Would be of great help if you could please get someone on it and look into. Thanks. Karthik Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29387) Cannot sync into workspaces with '@' in their path
Title: Message Title Paul "TBBle" Hampson commented on JENKINS-29387 Re: Cannot sync into workspaces with '@' in their path A workaround is mentioned in JENKINS-14354 , referenced from JENKINS-25242, is to change a system property to use a different specifier for the extra workspaces: -Dhudson.slaves.WorkspaceList=_. The current discussion in JENKINS-25242 indicates that this problem is also the reason for that issue, so when that is resolved, this issue will either be resolved or turn out to be a workflow-plugin issue (if it doesn't honour that system property for some reason). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-30080) Possible deadlock between scheduleBuild() and NodeProvisioner updates
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-30080 Possible deadlock between scheduleBuild() and NodeProvisioner updates We decided on making 1.625 the next LTS baseline. Change By: Daniel Beck Labels: deadlock lts-candidate queue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29060) Jenkins incorrectly reports timestamps are inconsistent
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-29060 Jenkins incorrectly reports timestamps are inconsistent Change By: Daniel Beck Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title Ronald Pomeroy edited a comment on JENKINS-30252 Re: Provide easy access to git branch name in multibranch workflow scripts env.JOB_NAME (I assume) is static. If new branches are indexed (in the multibranch plugin case) how can the JOB_NAME contain the git branch name . ? Am I missing something?RegardsRon Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title Ronald Pomeroy commented on JENKINS-30252 Re: Provide easy access to git branch name in multibranch workflow scripts env.JOB_NAME (I assume) is static. If new branches are indexed how can the JOB_NAME contain the git branch name. Am I missing something? Regards Ron Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title Ronald Pomeroy updated an issue Jenkins / JENKINS-30252 Provide easy access to git branch name in multibranch workflow scripts Change By: Ronald Pomeroy Comment: I tried to log out the env.JOB_NAMEwith echo " *** ${env.JOB_NAME} *** "and got...Running: Print Message*** ${env.JOB_NAME} *** ... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Patrick Ryan commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job +1 I tried downgrading to 1.4.5 without success. If I have job A manually trigger job B, when I click the arrow to start job B, I would expect a build with parameters screen when I can choose things that will affect the rest of the pipeline. My example is a manual test that we may not want to run every time. When the pipeline gets to that point, I want it to be up to the user whether or not to spin up the env and run the tests. Therefore when they start that job, there will be a true/false that the user can pick which will decide the output. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [negotiate-sso-plugin] (JENKINS-30116) NegSecFilter should not secure notifyCommit URLs
Title: Message Title pmv commented on JENKINS-30116 Re: NegSecFilter should not secure notifyCommit URLs Before you release - we also use the cli to issue commands to Jenkins. Do you happen to know if that will work with your filter, or will it have the same problem? I should be able to get this tested before the 5th, but just wanted to give you a heads up. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [robot-plugin] (JENKINS-29353) Configurable number of builds for trends generation
Title: Message Title Nickolay Rumyantsev resolved as Fixed Fixed and merged in https://github.com/jenkinsci/robot-plugin/pull/10. Jenkins / JENKINS-29353 Configurable number of builds for trends generation Change By: Nickolay Rumyantsev Status: Open Resolved Assignee: jpiironen Nickolay Rumyantsev Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title Mirko Friedenhagen commented on JENKINS-22252 Re: Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Going back to maven plugin version 2.10 did the trick for us as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-25475) Jenkins is not aware of personal builds, personal build failures mark Jenkins job status as failed
Title: Message Title Krishna Kishore assigned an issue to Krishna Kishore Jenkins / JENKINS-25475 Jenkins is not aware of personal builds, personal build failures mark Jenkins job status as failed Change By: Krishna Kishore Assignee: Krishna Kishore Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-25475) Jenkins is not aware of personal builds, personal build failures mark Jenkins job status as failed
Title: Message Title Krishna Kishore commented on JENKINS-25475 Re: Jenkins is not aware of personal builds, personal build failures mark Jenkins job status as failed 366924: Add option to disable personal builds from triggering Jenkins builds Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30255) Publicly disclosed security issue on Jenkins suggested to affect latest version
Title: Message Title intan alip commented on JENKINS-30255 Re: Publicly disclosed security issue on Jenkins suggested to affect latest version Thanks a lot! Creating a security report for followups. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Alexander Komarov edited a comment on JENKINS-30271 Re: Jenkins job hangs and cannot be killed after aborting DSL job This may not be the plugin's fault.The following code is enough to hang the job:{code:java}def testvar = [:]def itemname = 'something'println "I am trying to print a nonexistent item: ${testvar[itemname]}"{code}This code runs fine on one of my Jenkins masters, but hangs on the other. In fact, the hash element doesn't even need to be non-existent. However, since this only occurs after a run of the DSL plugin, it may still be an issue with job-dsl-plugin. I also made a job with two steps: # Execute Groovy (using Groovy 2.4.3)# Process Job DSL... and used the code above in both steps. #1 worked and #2 hung Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19145) Builds fail because of "slave went offline during the build"
Title: Message Title Ganga Ram edited a comment on JENKINS-19145 Re: Builds fail because of "slave went offline during the build" Seen in Jenkins ver. 1.609.1{code}13:47:30 Slave went offline during the build13:47:31 ERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@6ed75b03[name=jenkins-win-slave1]13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208)13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628)13:47:31 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)13:47:31 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)13:47:31 at java.util.concurrent.FutureTask.run(FutureTask.java:266)13:47:31 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)13:47:31 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)13:47:31 at java.lang.Thread.run(Thread.java:745)13:47:31 Caused by: java.io.IOException: Connection reset by peer13:47:31 at sun.nio.ch.FileDispatcherImpl.read0(Native Method)13:47:31 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)13:47:31 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)13:47:31 at sun.nio.ch.IOUtil.read(IOUtil.java:197)13:47:31 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)13:47:31 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136)13:47:31 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306)13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561)13:47:31 ... 6 more13:47:31 13:47:31 Build step 'Invoke Ant' marked build as failure13:47:31 ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception13:47:31 hudson.AbortException: no workspace for 1010-unit-tests #36413:47:31 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:72)13:47:31 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721)13:47:31 at hudson.model.Build$BuildExecution.post2(Build.java:183)13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670)13:47:31 at hudson.model.Run.execute(Run.java:1766)13:47:31 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)13:47:31 at hudson.model.ResourceController.execute(ResourceController.java:98)13:47:31 at hudson.model.Executor.run(Executor.java:374){code}Jenkins master stacktrace:{code}Sep 02, 2015 1:47:29 PM org.jenkinsci.remoting.nio.NioChannelHub runWARNING: Communication problemjava.io.IOException: Connection reset by peerat sun.nio.ch.FileDispatcherImpl.read0(Native Method)at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)at sun.nio.ch.IOUtil.read(IOUtil.java:197)at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136)at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306)at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561)at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java
[JIRA] [jira-plugin] (JENKINS-30155) Cannot get jira plugin to validate my login/password and comments are not added to issues in jira
Title: Message Title Radek Antoniuk commented on JENKINS-30155 Re: Cannot get jira plugin to validate my login/password and comments are not added to issues in jira The version 2.0 of the plugin has been released. Can you try upgrading and see if you still have an issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [slack-plugin] (JENKINS-27935) Slack plugin 1.7 fails to post to channel; had to revert to 1.2
Title: Message Title M Chon commented on JENKINS-27935 Re: Slack plugin 1.7 fails to post to channel; had to revert to 1.2 Seems to be resolved in 1.8. Thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19145) Builds fail because of "slave went offline during the build"
Title: Message Title Ganga Ram edited a comment on JENKINS-19145 Re: Builds fail because of "slave went offline during the build" Seen in Jenkins ver. 1.609.1{code}13:47:30 Slave went offline during the build13:47:31 ERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@6ed75b03[name=jenkins-win-slave1]13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208)13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628)13:47:31 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)13:47:31 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)13:47:31 at java.util.concurrent.FutureTask.run(FutureTask.java:266)13:47:31 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)13:47:31 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)13:47:31 at java.lang.Thread.run(Thread.java:745)13:47:31 Caused by: java.io.IOException: Connection reset by peer13:47:31 at sun.nio.ch.FileDispatcherImpl.read0(Native Method)13:47:31 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)13:47:31 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)13:47:31 at sun.nio.ch.IOUtil.read(IOUtil.java:197)13:47:31 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)13:47:31 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136)13:47:31 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306)13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561)13:47:31 ... 6 more13:47:31 13:47:31 Build step 'Invoke Ant' marked build as failure13:47:31 ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception13:47:31 hudson.AbortException: no workspace for 1010-unit-tests #36413:47:31 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:72)13:47:31 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721)13:47:31 at hudson.model.Build$BuildExecution.post2(Build.java:183)13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670)13:47:31 at hudson.model.Run.execute(Run.java:1766)13:47:31 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)13:47:31 at hudson.model.ResourceController.execute(ResourceController.java:98)13:47:31 at hudson.model.Executor.run(Executor.java:374){code} Jenkins master stacktrace:{code}Sep 02, 2015 1:47:29 PM org.jenkinsci.remoting.nio.NioChannelHub runWARNING: Communication problemjava.io.IOException: Connection reset by peerat sun.nio.ch.FileDispatcherImpl.read0(Native Method)at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)at sun.nio.ch.IOUtil.read(IOUtil.java:197)at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136)at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306)at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561)at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.jav
[JIRA] [core] (JENKINS-19145) Builds fail because of "slave went offline during the build"
Title: Message Title Ganga Ram commented on JENKINS-19145 Re: Builds fail because of "slave went offline during the build" Seen in Jenkins ver. 1.609.1 13:47:30 Slave went offline during the build 13:47:31 ERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@6ed75b03[name=jenkins-win-slave1] 13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) 13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) 13:47:31 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 13:47:31 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 13:47:31 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 13:47:31 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 13:47:31 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 13:47:31 at java.lang.Thread.run(Thread.java:745) 13:47:31 Caused by: java.io.IOException: Connection reset by peer 13:47:31 at sun.nio.ch.FileDispatcherImpl.read0(Native Method) 13:47:31 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) 13:47:31 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) 13:47:31 at sun.nio.ch.IOUtil.read(IOUtil.java:197) 13:47:31 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) 13:47:31 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) 13:47:31 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) 13:47:31 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) 13:47:31 ... 6 more 13:47:31 13:47:31 Build step 'Invoke Ant' marked build as failure 13:47:31 ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception 13:47:31 hudson.AbortException: no workspace for 1010-unit-tests #364 13:47:31 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:72) 13:47:31 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) 13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) 13:47:31 at hudson.model.Build$BuildExecution.post2(Build.java:183) 13:47:31 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) 13:47:31 at hudson.model.Run.execute(Run.java:1766) 13:47:31 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 13:47:31 at hudson.model.ResourceController.execute(ResourceController.java:98) 13:47:31 at hudson.model.Executor.run(Executor.java:374) Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-30271 Jenkins job hangs and cannot be killed after aborting DSL job Change By: Alexander Komarov Running job-dsl-plugin off the master branch (78ae0c67c3d0b3ce630cca0987c5fba869c8dfb1) plus 3 of my outstanding pull requests folded in. I don't think that this issue is related to my changes (which are about adding new DSL configuration options for plugins)Steps to reproduce:# Run a job with a Process DSL Script task (ideally long-running)# Abort job while it's executing. Job will not stop, but will finish normally.# Run the job again. Job will hang and cannot be aborted. Interestingly, Thread.interrupt() from the script console will not kill it. Using Monitoring plugin's kill feature does kill the job, but the next run will still hang. Only a restart of the Jenkins master fixes the problem.UPDATE: also happens without aborting jobs, making this more than minor. BTW, I am running this on two masters and it happened only once on one and a lot on the other.Stacktrace for the stuck job:{quote}Executor # 0 1 for master : executing DSL Job Builder # 96 108 sun.misc.Unsafe.park(Native Method)java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)org.codehaus.groovy.util.LockableObject.lock(LockableObject.java:34)org.codehaus.groovy.reflection.ClassInfo.lock(ClassInfo.java:268)org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:193)org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.getMetaClass(MetaClassRegistryImpl.java:231)org.codehaus.groovy.runtime.InvokerHelper.getMetaClass(InvokerHelper.java:747)org.codehaus.groovy.runtime.callsite.CallSiteArray.createPojoSite(CallSiteArray.java:109)org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(CallSiteArray.java:150)org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) javaposse.jobdsl.dsl.helpers.BuildParametersContext.checkParameterName(BuildParametersContext.groovy:270)javaposse.jobdsl.dsl.helpers.BuildParametersContext.simpleParam(BuildParametersContext.groovy:187)javaposse.jobdsl.dsl.helpers.BuildParametersContext.this$3$simpleParam(BuildParametersContext.groovy)javaposse.jobdsl.dsl.helpers.BuildParametersContext$this$3$simpleParam.callCurrent(Unknown Source)org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)javaposse.jobdsl.dsl.helpers.BuildParametersContext$this$3$simpleParam.callCurrent(Unknown Source)javaposse.jobdsl.dsl.helpers.BuildParametersContext.stringParam(BuildParametersContext.groovy:179)javaposse.jobdsl.dsl.helpers.BuildParametersContext.stringParam(BuildParametersContext.groovy)sun.reflect.GeneratedMethodAccessor459.invoke(Unknown Source)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
[JIRA] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Axel Moussard commented on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error Same here, Jenkins 1.627 and Plugin 1.1.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title Ronald Pomeroy edited a comment on JENKINS-30252 Re: Provide easy access to git branch name in multibranch workflow scripts In a JenkinsFile should I tried to log out the env.JOB_NAME with echo " *** ** ${env.JOB_NAME} *** ** " return something interesting? and got Currently it yeilds: ... Running: Print Message *** ** ${env.JOB_NAME} *** ** In the log ... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title Ronald Pomeroy edited a comment on JENKINS-30252 Re: Provide easy access to git branch name in multibranch workflow scripts In a JenkinsFile should echo " * ${env.JOB_NAME} * "return something interesting? Currently it yeilds:Running: Print Message * ${env.JOB_NAME} * In the log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title Ronald Pomeroy edited a comment on JENKINS-30252 Re: Provide easy access to git branch name in multibranch workflow scripts In a JenkinsFile should {{ echo " * ${env.JOB_NAME} * " }} return something interesting? Currently it yeilds: {{ Running: Print Message * ${env.JOB_NAME} * }} In the log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title Ronald Pomeroy commented on JENKINS-30252 Re: Provide easy access to git branch name in multibranch workflow scripts In a JenkinsFile should {{echo " * $ {env.JOB_NAME} * "}} return something interesting? Currently it yeilds: {{Running: Print Message * ${env.JOB_NAME} * }} In the log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [saml-plugin] (JENKINS-30274) ADFS Integration - What claims to use?
Title: Message Title Sijis Aviles created an issue Jenkins / JENKINS-30274 ADFS Integration - What claims to use? Issue Type: Bug Assignee: Ben McCann Components: saml-plugin Created: 02/Sep/15 8:09 PM Priority: Minor Reporter: Sijis Aviles We are trying to saml-plugin working with ADFS 2.0. Unfortunately there isn't much documentation on how to configure it or what claims and formats to use. After some trial and error we got the following claims to work (below) and are able to login and logout: Userid = (not configured) NameID = (windows account name) (eg. \) However, changing NameID to something like Common Name, breaks with "javax.servlet.ServletException:org.pac4j.saml.exceptions.SamlException: Subject NameID cannot be null". Also trying other settings for NameID would break with identical error, which leads me to believe it cannot handle spaces? Is there a list of what claims are required and what are optional that need to be sent to Jenkins? Thanks, Sijis
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-30273) Issue with Jenkins and ALM11.52 integration
Title: Message Title Thiyagarajan Aramudhan updated an issue Jenkins / JENKINS-30273 Issue with Jenkins and ALM11.52 integration Change By: Thiyagarajan Aramudhan We are trying to integrate Jenkins with HP ALM 11.52.I have added Plugin “hp-application-automation-tools-plugin” to Jenkins to connect HP ALM.When i try to build the job from Jenkin, i am getting below error message in Jenkin Console Output. How to resolve or what is the next steps? Run mode is set to: RUN_LOCALThe OTA version is not compatible with the current version of the Application Lifecycle Management server:OTA version: 11.52, OTA build number: 341. Server version: 11.52, server build number: 536.Error: Cannot Login to QC: Authorization failed.Build step 'Execute HP functional tests from HP ALM' changed build result to FAILURERun condition [Always] enabling perform for step [[Publish HP tests result]]Finished: FAILUREWe have tried below but we couldn’t fix this issue: * Tried Cleaning up with HP Clean Utility tool to clean up old artifacts.* I have opened the HP ticket. HP suggested as below : “ " In this case, this is out of our support, we don’t have any information about how to perform this, because ALM is not design to be integrate with Jenkins””: Below links are from HP Support:http://support.openview.hp.com/selfsolve/document/KM00413897https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00491230 How to resolve or what is the next steps? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you a
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-30273) Issue with Jenkins and ALM11.52 integration
Title: Message Title Thiyagarajan Aramudhan updated an issue Jenkins / JENKINS-30273 Issue with Jenkins and ALM11.52 integration Change By: Thiyagarajan Aramudhan We are trying to integrate Jenkins with HP ALM 11.52.I have added Plugin “hp-application-automation-tools-plugin” to Jenkins to connect HP ALM.When i try to build the job from Jenkin, i am getting below error message in Jenkin Console Output.How to resolve or what is the next steps?Run mode is set to: RUN_LOCALThe OTA version is not compatible with the current version of the Application Lifecycle Management server:OTA version: 11.52, OTA build number: 341. Server version: 11.52, server build number: 536.Error: Cannot Login to QC: Authorization failed.Build step 'Execute HP functional tests from HP ALM' changed build result to FAILURERun condition [Always] enabling perform for step [[Publish HP tests result]]Finished: FAILUREWe have tried below but we couldn’t fix this issue:I have opened the HP ticket. HP suggested as below :“In this case, this is out of our support, we don’t have any information about how to perform this, because ALM is not design to be integrate with Jenkins””: Below links are from HP Support:http://support.openview.hp.com/selfsolve/document/KM00413897https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00491230 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-30273) Issue with Jenkins and ALM11.52 integration
Title: Message Title Thiyagarajan Aramudhan created an issue Jenkins / JENKINS-30273 Issue with Jenkins and ALM11.52 integration Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 02/Sep/15 7:47 PM Environment: Integration Priority: Blocker Reporter: Thiyagarajan Aramudhan We are trying to integrate Jenkins with HP ALM 11.52. I have added Plugin “hp-application-automation-tools-plugin” to Jenkins to connect HP ALM. When i try to build the job from Jenkin, i am getting below error message in Jenkin Console Output. How to resolve or what is the next steps? Run mode is set to: RUN_LOCAL The OTA version is not compatible with the current version of the Application Lifecycle Management server: OTA version: 11.52, OTA build number: 341. Server version: 11.52, server build number: 536. Error: Cannot Login to QC: Authorization failed. Build step 'Execute HP functional tests from HP ALM' changed build result to FAILURE Run condition [Always] enabling perform for step [[Publish HP tests result]] Finished: FAILURE We have tried below but we couldn’t fix this issue: I have opened the HP ticket. HP suggested as below : “In this
[JIRA] [build-pipeline-plugin] (JENKINS-30272) Build Pipeline Manual Trigger job is running automatically
Title: Message Title Patrick Ryan created an issue Jenkins / JENKINS-30272 Build Pipeline Manual Trigger job is running automatically Issue Type: Bug Assignee: bap Components: build-pipeline-plugin, flexible-publish-plugin Created: 02/Sep/15 7:02 PM Environment: Jenkins 1.610, build-pipeline 1.47, flexible-publish 0.152 Priority: Major Reporter: Patrick Ryan If I have flexible publish set up to call a downstream job with a manual trigger (in my case only if the build is successful) it just calls the job automatically, no "play" button. If I do it without flexible publish, it will show the "play" triangle on the job and wait for me to trigger it. Also: Is it possible have that play button take you to a screen where you can change parameters? I have a boolean defined and I want the user to be able to set that to true or false before running the job.
[JIRA] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Alexander Komarov edited a comment on JENKINS-30271 Re: Jenkins job hangs and cannot be killed after aborting DSL job This may not be the plugin's fault.The following code is enough to hang the job:{code:java}def testvar = [:]def itemname = 'something'println "I am trying to print a nonexistent item: ${testvar[itemname]}"{code}This code runs fine on one of my Jenkins masters, but hangs on the other. In fact, the hash element doesn't even need to be non-existent. However, since this only occurs after a run of the DSL plugin, it may still be an issue with job-dsl-plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Alexander Komarov edited a comment on JENKINS-30271 Re: Jenkins job hangs and cannot be killed after aborting DSL job This may not be the plugin's fault.The following code is enough to hang the job:{code:java}def testvar = [:]def itemname = 'something'println "I am trying to print a nonexistent item: ${testvar[itemname]}"{code} (this This code runs fine outside on one of my Jenkins masters, but hangs on the job though) other. In fact, the hash element doesn't even need to be non-existent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30247) Xvfb is not launched on master node in a multi-configuration job
Title: Message Title zregvart closed an issue as Not A Defect Jenkins build wrappers do not run in the post build actions, but in Xvfb plugin there is an option you can check called "Shutdown Xvfb with whole job, not just with the main build action" that should help you have the Xvfb running in the post build steps. Jenkins / JENKINS-30247 Xvfb is not launched on master node in a multi-configuration job Change By: zregvart Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Alexander Komarov commented on JENKINS-30271 Re: Jenkins job hangs and cannot be killed after aborting DSL job This may not be the plugin's fault. The following code is enough to hang the job: def testvar = [:] def itemname = 'something' println "I am trying to print a nonexistent item: ${testvar[itemname]}" (this code runs fine outside of the job though) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cmakebuilder-plugin] (JENKINS-30070) Automatic download and installation of cmake from cmake.org
Title: Message Title Martin Weber assigned an issue to Martin Weber Jenkins / JENKINS-30070 Automatic download and installation of cmake from cmake.org Change By: Martin Weber Assignee: Martin Weber Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-26173) Nested buildflow ignore instructions are not working
Title: Message Title stefan thomasson commented on JENKINS-26173 Re: Nested buildflow ignore instructions are not working You forgot to wrap the ignore in curly braces. This works for me, parallel( { build("job1") } , { ignore(FAILURE) { build("IdoNotExist") } }, { build("job2") } ) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-30271 Jenkins job hangs and cannot be killed after aborting DSL job Change By: Alexander Komarov Running job-dsl-plugin off the master branch (78ae0c67c3d0b3ce630cca0987c5fba869c8dfb1) plus 3 of my outstanding pull requests folded in. I don't think that this issue is related to my changes (which are about adding new DSL configuration options for plugins) Steps to reproduce:# Run a job with a Process DSL Script task (ideally long-running)# Abort job while it's executing. Job will not stop, but will finish normally.# Run the job again. Job will hang and cannot be aborted. Interestingly, Thread.interrupt() from the script console will not kill it. Using Monitoring plugin's kill feature does kill the job, but the next run will still hang. Only a restart of the Jenkins master fixes the problem.UPDATE: also happens without aborting jobs, making this more than minor. BTW, I am running this on two masters and it happened only once on one and a lot on the other.Stacktrace for the stuck job:{quote}Executor #0 for master : executing DSL Job Builder #96sun.misc.Unsafe.park(Native Method)java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)org.codehaus.groovy.util.LockableObject.lock(LockableObject.java:34)org.codehaus.groovy.reflection.ClassInfo.lock(ClassInfo.java:268)org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:193)org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.getMetaClass(MetaClassRegistryImpl.java:231)org.codehaus.groovy.runtime.InvokerHelper.getMetaClass(InvokerHelper.java:747)org.codehaus.groovy.runtime.callsite.CallSiteArray.createPojoSite(CallSiteArray.java:109)org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(CallSiteArray.java:150)org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)PipelineJobsBuilder$_run_closure1_closure9_closure10.doCall(PipelineJobsBuilder.groovy:620)sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:497)org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)groovy.lang.Closure.call(Closure.java:415)groovy.lang.Closure.call(Closure.java:428)org.codehaus.groovy.runtime.DefaultGroovyMethods.with(DefaultGroovyMethods.java:196)org.codehaus.groovy.runtime.dgm$926.invoke(Unknown Source)org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoMet
[JIRA] [p4-plugin] (JENKINS-29387) Cannot sync into workspaces with '@' in their path
Title: Message Title Joel Brown commented on JENKINS-29387 Re: Cannot sync into workspaces with '@' in their path Somewhat related: JENKINS-25242. Same issue with "@" in the path. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-30271) Jenkins job hangs and cannot be killed after aborting DSL job
Title: Message Title Alexander Komarov created an issue Jenkins / JENKINS-30271 Jenkins job hangs and cannot be killed after aborting DSL job Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 02/Sep/15 5:20 PM Priority: Major Reporter: Alexander Komarov Steps to reproduce: Run a job with a Process DSL Script task (ideally long-running) Abort job while it's executing. Job will not stop, but will finish normally. Run the job again. Job will hang and cannot be aborted. Interestingly, Thread.interrupt() from the script console will not kill it. Using Monitoring plugin's kill feature does kill the job, but the next run will still hang. Only a restart of the Jenkins master fixes the problem. UPDATE: also happens without aborting jobs, making this more than minor. BTW, I am running this on two masters and it happened only once on one and a lot on the other. Stacktrace for the stuck job: Executor #0 for master : executing DSL Job B
[JIRA] [analysis-collector-plugin] (JENKINS-30270) Disable other trend graphs does not work for warnings plug-in
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-30270 Disable other trend graphs does not work for warnings plug-in Issue Type: Bug Assignee: Ulli Hafner Components: analysis-collector-plugin, warnings-plugin Created: 02/Sep/15 4:57 PM Priority: Minor Reporter: Ulli Hafner The option to disable the other trend graphs does not work for the parser specific trend graphs of the warnings plug-in. Add Comment This message was sent
[JIRA] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking
Title: Message Title Nigel Harniman updated an issue Jenkins / JENKINS-30269 Add workflow support for resource locking Change By: Nigel Harniman Add support to use this plugin from workflow to manage concurrent consumption of resources.Similar to how {{stage}} step works as blocked scoped to control concurrency of other builds for this job running this step at the same time, it would be useful to be able to do this for resources across jobs.Continue to allow the resources to be set up in the Jenkins configuration.Consumption of resources should be controlled with a syntax along these lines:For a single resource:resource (name: db-a-1, reservedVariable: DB_RESOURCE) \ { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE”} For a pool of resources sharing a label: resource (label: db-a, quantity: 2, reservedVariable: DB_RESOURCE) \ { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE”} Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking
Title: Message Title Nigel Harniman updated an issue Jenkins / JENKINS-30269 Add workflow support for resource locking Change By: Nigel Harniman Add support to use this plugin from workflow to manage concurrent consumption of resources.Similar to how {{stage}} step works as blocked scoped to control concurrency of other builds for this job running this step at the same time, it would be useful to be able to do this for resources across jobs.Continue to allow the resources to be set up in the Jenkins configuration.Consumption of resources should be controlled with a syntax along these lines:For a single resource:resource (name: db-a-1, reservedVariable: DB_RESOURCE) { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE”}For a pool of resources sharing a label:resource (label: db-a, quantity: 2, reservedVariable: DB_RESOURCE) { // Do something here that uses the resourceecho “DB Resource(s) used = $DB_RESOURCE”} Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [performance-plugin] (JENKINS-27373) Performance Plugin fails with java.lang.ArithmeticException: / by zero (divide by zero)
Title: Message Title Nick Jones reopened an issue The current released version of the Performance Plugin (1.13) still has this issue. The pull request needs to be merged and the plugin re-released. Jenkins / JENKINS-27373 Performance Plugin fails with java.lang.ArithmeticException: / by zero (divide by zero) Change By: Nick Jones Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [performance-plugin] (JENKINS-27373) Performance Plugin fails with java.lang.ArithmeticException: / by zero (divide by zero)
Title: Message Title Nick Jones commented on JENKINS-27373 Re: Performance Plugin fails with java.lang.ArithmeticException: / by zero (divide by zero) Also affected by it. Running Performance Plugin 1.13 on Jenkins 1.609.2 LTS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-30242 Update to 1.13.2 breaks global configuration submission Change By: Kirill Merkushev Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev edited a comment on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission Workaround until jira merged PR with fix: https://github.com/jenkinsci/github-plugin/pull/81 https://jenkins.ci.cloudbees.com/job/plugins/job/github-plugin/275/com.coravy.hudson.plugins.github$github/artifact/com.coravy.hudson.plugins.github/github/1.14.0-SNAPSHOT/github-1.14.0-SNAPSHOT.hpiI'll think about merging and releasing this because of it a bug in jira plugin and not in github-plugin, which uses standard stapler ability to convert json to bean Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-30269 Add workflow support for resource locking Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 02/Sep/15 4:17 PM Labels: workflow Priority: Major Reporter: Nigel Harniman Add support to use this plugin from workflow to manage concurrent consumption of resources. Similar to how stage step works as blocked scoped to control concurrency of other builds for this job running this step at the same time, it would be useful to be able to do this for resources across jobs. Continue to allow the resources to be set up in the Jenkins configuration. Consumption of resources should be controlled with a syntax along these lines: For a single resource: resource (name: db-a-1, reservedVariable: DB_RESOURCE) { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE” } For a pool of resources sharing a label: resource (label: db-a, quantity: 2, reservedVariable: DB_RESOURCE) { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE” }
[JIRA] [github-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev commented on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission Workaround until jira merged PR with fix: https://github.com/jenkinsci/github-plugin/pull/81 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Antonio Muñiz stopped work on JENKINS-30166 Change By: Antonio Muñiz Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title George Bloggs edited a comment on JENKINS-22252 Re: Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap We had similar issues with Jenkins 1.627 & /Apache Maven 3.3.3/Maven Integration plugin 2.12. The solution was to move the Maven Integration plugin back to 2.11 and all worked well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title George Bloggs commented on JENKINS-22252 Re: Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap We had similar issues with Jenkins 1.627 & Maven Integration plugin 2.12. The solution was to move the Maven Integration plugin back to 2.11 and all worked well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Title: Message Title Sascha Retter edited a comment on JENKINS-17431 Re: 500 Internal Server Error on attempt to run a build Most probably this is neither a Jenkins / SVN Plugin nor an SVNKIT issue. It seems to be an issue of the SVN server. We are getting the following output in jenkins console:{code}14:25:13 Checking out https://XXX at revision '2015-09-02T14:25:12.558 +0200'14:25:13 ERROR: Failed to check out XXX14:25:13 org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT of '/svn/YYY/!svn/vcc/default': 500 Internal Server Error (https://XYZ)14:25:13 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)14:25:13 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)14:25:13 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:202)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:178)14:25:13 at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:187)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:756)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)14:25:13 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)14:25:13 at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)14:25:13 at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)14:25:13 at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:170)14:25:13 at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:134)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948)14:25:13 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688)14:25:13 at hudson.remoting.UserRequest.perform(UserRequest.java:121)14:25:13 at hudson.remoting.UserRequest.perform(UserRequest.java:49)14:25:13 at hudson.remoting.Request$2.run(Request.java:325)14:25:13 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)14:25:13 at java.util.concurrent.FutureTask.run(FutureTask.java:262)14:25:13 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)14:25:13 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)14:25:13 at java.lang.Thread.run(Thread.java:745)14:25:13 java.io.IOException: remote file operation failed: /a/file/system/location at hudson.remoting.Channel@704e71df:a_hostname: hudson.remoting.ProxyException: java.io.IOException: Failed to check out XXX{code}If we try to checkout using svnkit or native svn by HEAD or revisionnumber everything works as expected. But as soon as we are using the timestamp to checkout as Jenkins does we are getting an error. Example with native svn (svn, Version 1.8.13 (r1667537)){code}svn --username auser co https://XXX -r {"2015-09-02 09:00:00"} svn: E175002: Unerwarteter HTTP-Status 500 »Internal Server Error« auf »/svn/CONCARDEV/!svn/me«svn: E175002: Zusätzliche Fe
[JIRA] [subversion-plugin] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Title: Message Title Sascha Retter edited a comment on JENKINS-17431 Re: 500 Internal Server Error on attempt to run a build Most probably this is not neither a Jenkins / SVN Plugin nor an SVNKIT issue. It seems to be an issue of the SVN server. We are getting the following output in jenkins console:{code}14:25:13 Checking out https://XXX at revision '2015-09-02T14:25:12.558 +0200'14:25:13 ERROR: Failed to check out XXX14:25:13 org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT of '/svn/YYY/!svn/vcc/default': 500 Internal Server Error (https://XYZ)14:25:13 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)14:25:13 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)14:25:13 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:202)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:178)14:25:13 at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:187)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:756)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)14:25:13 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)14:25:13 at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)14:25:13 at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)14:25:13 at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:170)14:25:13 at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:134)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948)14:25:13 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688)14:25:13 at hudson.remoting.UserRequest.perform(UserRequest.java:121)14:25:13 at hudson.remoting.UserRequest.perform(UserRequest.java:49)14:25:13 at hudson.remoting.Request$2.run(Request.java:325)14:25:13 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)14:25:13 at java.util.concurrent.FutureTask.run(FutureTask.java:262)14:25:13 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)14:25:13 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)14:25:13 at java.lang.Thread.run(Thread.java:745)14:25:13 java.io.IOException: remote file operation failed: /a/file/system/location at hudson.remoting.Channel@704e71df:a_hostname: hudson.remoting.ProxyException: java.io.IOException: Failed to check out XXX{code}If we try to checkout using svnkit or native svn by HEAD or revisionnumber everything works as expected. But as soon as we are using the timestamp to checkout as Jenkins does we are getting an error. Example with native svn (svn, Version 1.8.13 (r1667537)){code}svn --username auser co https://XXX -r {"2015-09-02 09:00:00"} svn: E175002: Unerwarteter HTTP-Status 500 »Internal Server Error« auf »/svn/CONCARDEV/!svn/me«svn: E175002: Zusätzl
[JIRA] [subversion-plugin] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Title: Message Title Sascha Retter edited a comment on JENKINS-17431 Re: 500 Internal Server Error on attempt to run a build Most probably this is neither a Jenkins / SVN Plugin nor an SVNKIT issue. It seems to be an issue of the SVN server. We are getting the following output in jenkins console:{code}14:25:13 Checking out https://XXX at revision '2015-09-02T14:25:12.558 +0200'14:25:13 ERROR: Failed to check out XXX14:25:13 org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT of '/svn/YYY/!svn/vcc/default': 500 Internal Server Error (https://XYZ)14:25:13 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)14:25:13 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)14:25:13 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:202)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:178)14:25:13 at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:187)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:756)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11)14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)14:25:13 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)14:25:13 at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)14:25:13 at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)14:25:13 at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:170)14:25:13 at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:134)14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972)14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948)14:25:13 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688)14:25:13 at hudson.remoting.UserRequest.perform(UserRequest.java:121)14:25:13 at hudson.remoting.UserRequest.perform(UserRequest.java:49)14:25:13 at hudson.remoting.Request$2.run(Request.java:325)14:25:13 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)14:25:13 at java.util.concurrent.FutureTask.run(FutureTask.java:262)14:25:13 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)14:25:13 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)14:25:13 at java.lang.Thread.run(Thread.java:745)14:25:13 java.io.IOException: remote file operation failed: /a/file/system/location at hudson.remoting.Channel@704e71df:a_hostname: hudson.remoting.ProxyException: java.io.IOException: Failed to check out XXX{code}If we try to checkout using svnkit or native svn by HEAD or revisionnumber everything works as expected. But as soon as we are using the timestamp to checkout as Jenkins does we are getting an error. Example with native svn (svn, Version 1.8.13 (r1667537)){code}svn --username auser co https://XXX -r {"2015-09-02 09:00:00"} svn: E175002: Unerwarteter HTTP-Status 500 »Internal Server Error« auf »/svn/ CONCARDEV XYZ /!svn/me«svn: E175002: Zusätzli
[JIRA] [subversion-plugin] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Title: Message Title Sascha Retter commented on JENKINS-17431 Re: 500 Internal Server Error on attempt to run a build Most probably this is not a Jenkins / SVN Plugin nor an SVNKIT issue. It seems to be an issue of the SVN server. We are getting the following output in jenkins console: 14:25:13 Checking out https://XXX at revision '2015-09-02T14:25:12.558 +0200' 14:25:13 ERROR: Failed to check out XXX 14:25:13 org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT of '/svn/YYY/!svn/vcc/default': 500 Internal Server Error (https://XYZ) 14:25:13 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) 14:25:13 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) 14:25:13 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:202) 14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:178) 14:25:13 at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:187) 14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) 14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:756) 14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26) 14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11) 14:25:13 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) 14:25:13 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) 14:25:13 at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) 14:25:13 at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) 14:25:13 at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115) 14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) 14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:170) 14:25:13 at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:134) 14:25:13 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) 14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) 14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) 14:25:13 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) 14:25:13 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) 14:25:13 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 14:25:13 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 14:25:13 at hudson.remoting.Request$2.run(Request.java:325) 14:25:13 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 14:25:13 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 14:25:13 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 14:25:13 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 14:25:13 at java.lang.Thread.run(Thread.java:745) 14:25:13 java.io.IOException: remote file operation failed: /a/file/system/location at hudson.remoting.Channel@704e71df:a_hostname: hudson.remoting.ProxyException: java.io.IOException: Failed to check out XXX If we try to checkout using svnkit or native svn by HEA
[JIRA] [core] (JENKINS-30268) Thread is dead
Title: Message Title Yunus Dawji created an issue Jenkins / JENKINS-30268 Thread is dead Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Sep/15 2:50 PM Environment: OS MAC OSX 10.10.4 Version 1.627 Priority: Major Reporter: Yunus Dawji I keep getting that the executor is dead Sep 02, 2015 6:19:13 AM SEVERE hudson.model.Executor run Unexpected executor death java.lang.IllegalStateException: cannot create a build with number 225 since that (or higher) is already in use among [207, 229, 230] at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361) at hudson.model.RunMap.put(RunMap.java:192) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at hudson.model.AbstractProject.newBuild(AbstractProject.java:1021) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1211) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145) at hudson.model.Executor$1.call(Executor.java:362) at hudson.model.Executor$1.call(Executor.java:344) at hudson.model.Queue._withLock(Queue.java:1345) at hudson.model.Queue.withLock(Queue.java:1210) at hudson.model.Executor.run(Executor.java:344)
[JIRA] [zephyr-for-jira-test-management-plugin] (JENKINS-30266) Can't add JIRA server to Zephyr for JIRA Test Management plugin
Title: Message Title Vladimir Luschik updated an issue Jenkins / JENKINS-30266 Can't add JIRA server to Zephyr for JIRA Test Management plugin Change By: Vladimir Luschik I can't add any JIRA servers to my Jenkins (we have Zephyr for JIRA 2 . 5.4 there) I tried different JIRA account but all the time I receive errors, even NPE. Using my work JIRA account I receive the following ERROR : Test Configuration ERRORA problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilt
[JIRA] [envinject-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title Marcin Zajączkowski commented on JENKINS-30042 Re: EnvInject doesn't see GIT_COMMIT even after SCM phase I ended up with dumping Git commit to file in a shell build step and inject it in the next step using EnvInject (but it could work out-of-box). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [envinject-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title Marcin Zajączkowski commented on JENKINS-30042 Re: EnvInject doesn't see GIT_COMMIT even after SCM phase Manuel Jesús Recena Soto I don't know. It was the new feature and I haven't changed it with the previous version. If it is important to find a reason I could give it a try. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [template-project-plugin] (JENKINS-27317) Support matrix aggregation with ProxyPublisher
Title: Message Title Sverre Moe commented on JENKINS-27317 Re: Support matrix aggregation with ProxyPublisher I have hope for a fix to be included within an early 1.5.x bug release. I myself have no experience in programming Jenkins plugins, but if no one picks up this soon, then I might try to fix it myself. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [envinject-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title Theodore Pak commented on JENKINS-30042 Re: EnvInject doesn't see GIT_COMMIT even after SCM phase Thanks to brendon wilder my build's EnvInject Groovy script works now. The critical detail is that: System.getenv() != Thread.currentThread()?.executable.parent.builds[0].properties.get('envVars') I'mont sure why. But you should use the latter to get all environment vars, as Brendon does in the script he provided. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev edited a comment on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission https://github.com/jenkinsci/jira-plugin/pull/60 - fix for the problem. Try to install jira plugin from build https://jenkins.ci.cloudbees.com/job/plugins/job/jira-plugin/83/org.jenkins-ci.plugins$jira/ Trying to create workaround in gh plugin... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-30242 Update to 1.13.2 breaks global configuration submission Change By: Kirill Merkushev Environment: Jenkins 1.609.2 jira-plugin, github-plugin, any jenkins core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Kirill Merkushev closed an issue as Fixed Jenkins / JENKINS-30223 Migrator for Credential.java is failing Change By: Kirill Merkushev Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [sectioned-view-plugin] (JENKINS-26818) Test result trends not showing in sectioned dashboard view
Title: Message Title Andrey Adamovich assigned an issue to Andrey Adamovich Jenkins / JENKINS-26818 Test result trends not showing in sectioned dashboard view Change By: Andrey Adamovich Assignee: Timothy Bingaman Andrey Adamovich Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [repository-connector-plugin] (JENKINS-30267) Maven repository artifact does not showing newly updated version from Nexus Maven Repository
Title: Message Title ravi aare updated an issue Jenkins / JENKINS-30267 Maven repository artifact does not showing newly updated version from Nexus Maven Repository Change By: ravi aare Environment: Jenkins ver. 1.554.3 Repository Connector plugin 1.1.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [repository-connector-plugin] (JENKINS-30267) Maven repository artifact does not showing newly updated version from Nexus Maven Repository
Title: Message Title ravi aare created an issue Jenkins / JENKINS-30267 Maven repository artifact does not showing newly updated version from Nexus Maven Repository Issue Type: Bug Assignee: Unassigned Attachments: param.png, repo.png Components: repository-connector-plugin Created: 02/Sep/15 1:40 PM Environment: Jenkins ver. 1.554.3 Priority: Major Reporter: ravi aare Newly updated artifact version is not showing through Jenkins build parameter 'Maven repository artifact'.we observed that it is showing newly updated versions after 10 to 12 hours later. Could you please help to resolve this issue to display the newly added artifact version as well immediately . Thanks and Regards Ravi
[JIRA] [envinject-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title brendon wilder commented on JENKINS-30042 Re: EnvInject doesn't see GIT_COMMIT even after SCM phase Workaround cobbled together from various sources on the interwebs: def env = System.getenv() env.each{ println it } def thr = Thread.currentThread() def build = thr?.executable def envVarsMap = build.parent.builds[0].properties.get("envVars") envVarsMap.each{ println it } def map = [HASH: envVarsMap['GIT_COMMIT']] return map Props to folks uncited... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [zephyr-for-jira-test-management-plugin] (JENKINS-30266) Can't add JIRA server to Zephyr for JIRA Test Management plugin
Title: Message Title Vladimir Luschik updated an issue Jenkins / JENKINS-30266 Can't add JIRA server to Zephyr for JIRA Test Management plugin Change By: Vladimir Luschik I can't add any JIRA servers to my Jenkins. I tried different JIRA account but all the time I receive errors, even NPE. Using my work JIRA account I receive the following ERROR : Test Configuration ERRORA problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationF
[JIRA] [zephyr-for-jira-test-management-plugin] (JENKINS-30266) Can't add JIRA server to Zephyr for JIRA Test Management plugin
Title: Message Title Vladimir Luschik updated an issue Jenkins / JENKINS-30266 Can't add JIRA server to Zephyr for JIRA Test Management plugin Change By: Vladimir Luschik I can't add any JIRA server servers to my Jenkins. I tried different JIRA account but all the time I receive errors, even NPE. Using my work JIRA account I receive the following ERROR : Test Configuration ERRORA problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIn
[JIRA] [zephyr-for-jira-test-management-plugin] (JENKINS-30266) Can't add JIRA server to Zephyr for JIRA Test Management plugin
Title: Message Title Vladimir Luschik created an issue Jenkins / JENKINS-30266 Can't add JIRA server to Zephyr for JIRA Test Management plugin Issue Type: Bug Assignee: Zephyr Developer Attachments: JIRA.png Components: zephyr-for-jira-test-management-plugin Created: 02/Sep/15 1:25 PM Priority: Blocker Reporter: Vladimir Luschik I can't add any JIRA server to my Jenkins. I tried different JIRA account but all the time I receive errors, even NPE. Using my work JIRA account I receive the following ERROR : Test Configuration ERROR A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.
[JIRA] [github-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev commented on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission https://github.com/jenkinsci/jira-plugin/pull/60 - fix for the problem. Trying to create workaround in gh plugin... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [maven-plugin] (JENKINS-30249) Jenkins 1.580.1 with jdk 5 build fails
Title: Message Title Steffen Breitbach commented on JENKINS-30249 Re: Jenkins 1.580.1 with jdk 5 build fails Have you tried Maven Project Plugin 2.11? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-12543) CliAuthenticator (username/password) called too late to parse arguments (like job names)
Title: Message Title Amit Ron commented on JENKINS-12543 Re: CliAuthenticator (username/password) called too late to parse arguments (like job names) I'm getting this failure on get-job windows environment + ldap + Jenkins v1.600 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [websphere-deployer-plugin] (JENKINS-30265) Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment)
Title: Message Title Josu Bengoa created an issue Jenkins / JENKINS-30265 Jenkins Plugin for WebSphere Deployer Not deploying to WAS85ND ( Remote deployment) Issue Type: Bug Assignee: Unassigned Components: websphere-deployer-plugin Created: 02/Sep/15 11:46 AM Environment: Jenkins 1.627 Windows WAS ND 8.5.5.4 iSeries WebSphere Deployer Plugin 1.3.4 Labels: websphere-deployer-plugin Priority: Major Reporter: Josu Bengoa The EAR is deployed, but it doesn't start. Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Failed to updated artifact: Failure uploading archive to server at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.updateArtifact(WebSphereDeploymentService.java:278) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.updateArtifact(WebSphereDeployerPlugin.java:252) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.
[JIRA] [simple-parameterized-builds-report-plugin] (JENKINS-30264) Merge code to jenkinsci
Title: Message Title evernat assigned an issue to Nalin Makar Jenkins / JENKINS-30264 Merge code to jenkinsci Change By: evernat Assignee: Nalin Makar Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [simple-parameterized-builds-report-plugin] (JENKINS-30264) Merge code to jenkinsci
Title: Message Title evernat created an issue Jenkins / JENKINS-30264 Merge code to jenkinsci Issue Type: Task Assignee: Unassigned Components: simple-parameterized-builds-report-plugin Created: 02/Sep/15 11:40 AM Priority: Minor Reporter: evernat In the wiki page, the github links go to https://github.com/jenkinsci/simple-parameterized-builds-report-plugin But this repo does not contain the latest source and is one year late. The latest source is not easy to find. Please merge the latest changes in https://github.com/jenkinsci/simple-parameterized-builds-report-plugin so that everyone can: check license issues, check security issues, fix bugs and enhance the plugin... By the way, what is the license of the plugin? MIT like many other plugins? It would be better to add a license in pom.xml and in a LICENSE file. https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites
[JIRA] [warnings-plugin] (JENKINS-29959) Make Warnings Plugin compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto resolved as Fixed Jenkins / JENKINS-29959 Make Warnings Plugin compatible with Workflow Change By: Manuel Jesús Recena Soto Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-29959) Make Warnings Plugin compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto stopped work on JENKINS-29959 Change By: Manuel Jesús Recena Soto Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-29959) Make Warnings Plugin compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-29959 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [zephyr-for-jira-test-management-plugin] (JENKINS-30091) Null pointer exception when importing xml containing only passing test cases
Title: Message Title Knut Karlsen commented on JENKINS-30091 Re: Null pointer exception when importing xml containing only passing test cases The above error is likely to be due to plugin mismatch on the JIRA server side, to be updated. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [promoted-builds-plugin] (JENKINS-29132) Deleted promotion steps keep executing
Title: Message Title Christian Meyer commented on JENKINS-29132 Re: Deleted promotion steps keep executing When I run Jenkins in the version 1.554.2, which is the minimum required core version for the plugin, the issue doesn't occur. But when I run it with a newer version 1.596.3 the issue is there. So it seems that there is a change in the core, which produce this problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [clearcase-ucm-plugin] (JENKINS-30259) Random test failure on test (poll child) (case 13493)
Title: Message Title Mads Nielsen resolved as Fixed Jenkins / JENKINS-30259 Random test failure on test (poll child) (case 13493) Change By: Mads Nielsen Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30223) Migrator for Credential.java is failing
Title: Message Title Ignacio Fuertes commented on JENKINS-30223 Re: Migrator for Credential.java is failing Great, Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-30085) SVN- Authentication Fails
Title: Message Title Loganathan C commented on JENKINS-30085 Re: SVN- Authentication Fails Hi, any update on this issue, can I get temporary workaround. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-30085) SVN- Authentication Fails
Title: Message Title Loganathan C updated an issue Jenkins / JENKINS-30085 SVN- Authentication Fails Change By: Loganathan C Comment: https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=recenaany update on this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-30085) SVN- Authentication Fails
Title: Message Title Loganathan C commented on JENKINS-30085 Re: SVN- Authentication Fails https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=recena any update on this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [zephyr-for-jira-test-management-plugin] (JENKINS-30091) Null pointer exception when importing xml containing only passing test cases
Title: Message Title Knut Karlsen commented on JENKINS-30091 Re: Null pointer exception when importing xml containing only passing test cases I think we get the same issue in our Zephyr>Jira job: [xUnit] [INFO] - Check 'Failed Tests' threshold. [xUnit] [INFO] - The total number of tests for this category exceeds the specified 'unstable' threshold value. [xUnit] [INFO] - Setting the build status to UNSTABLE [xUnit] [INFO] - Stopping recording. Build step 'Publish xUnit test result report' changed build result to UNSTABLE [ZapiTestResultReporter] [INFO] Examining test results... Build result is UNSTABLE Total Test Cases : 478ERROR: Build step failed with exception java.lang.NullPointerException at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.assignTests(TestCaseUtil.java:218) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:411) at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:98) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Build step 'Publish test result to Zephyr for JIRA' marked build as failure Finished: FAILURE It fails at a different point though: TestCaseUtil.java:218 Knut Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this
[JIRA] [github-plugin] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Xavier Morales commented on JENKINS-18079 Re: GitHub Push always builds if workspace is on offline slave node Two years after is still reproducing. Is there any possibility to look at this bug? I'm working with docker-plugin starting slaves and is an ugly thing to launch a build of the same revision anytime a push is done to other branches. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev commented on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission I'll try to create fix or workaround in a few hours Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev edited a comment on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission Think the problem is the integration with jira plugin.Reproduced successfully with installed Jira Plugin {noformat}ClassCastException: java.net.URL cannot be cast to java.lang.Stringat hudson.plugins.jira.JiraProjectProperty$DescriptorImpl$1.convert(JiraProjectProperty.java:122)at org.kohsuke.stapler.RequestImpl.copyProperty(RequestImpl.java:840)at org.kohsuke.stapler.RequestImpl.fill(RequestImpl.java:500)at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:414)at org.jenkinsci.plugins.github.config.GitHubPluginConfig.configure(GitHubPluginConfig.java:159){noformat}https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraProjectProperty.java#L122 It changes the global default URL converter Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev edited a comment on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission Think the problem is the integration with jira plugin.Reproduced successfully with installed Jira Plugin {noformat}ClassCastException: java.net.URL cannot be cast to java.lang.Stringat hudson.plugins.jira.JiraProjectProperty$DescriptorImpl$1.convert(JiraProjectProperty.java:122)at org.kohsuke.stapler.RequestImpl.copyProperty(RequestImpl.java:840)at org.kohsuke.stapler.RequestImpl.fill(RequestImpl.java:500)at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:414)at org.jenkinsci.plugins.github.config.GitHubPluginConfig.configure(GitHubPluginConfig.java:159){noformat} https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraProjectProperty.java#L122 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev commented on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission Think the problem is the integration with jira plugin. Reproduced successfully with installed Jira Plugin ClassCastException: java.net.URL cannot be cast to java.lang.String at hudson.plugins.jira.JiraProjectProperty$DescriptorImpl$1.convert(JiraProjectProperty.java:122) at org.kohsuke.stapler.RequestImpl.copyProperty(RequestImpl.java:840) at org.kohsuke.stapler.RequestImpl.fill(RequestImpl.java:500) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:414) at org.jenkinsci.plugins.github.config.GitHubPluginConfig.configure(GitHubPluginConfig.java:159) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-30242 Update to 1.13.2 breaks global configuration submission Change By: Kirill Merkushev Component/s: jira-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [promoted-builds-plugin] (JENKINS-29638) Build promotion will allow running of a job a user doesn't have permission to start
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-29638 Build promotion will allow running of a job a user doesn't have permission to start Probably promoted-builds plugin needs to be integrated with QueueItemAuthenticator extension in Jenkins core, which has been integrated into parameterized trigger ( JENKINS-16956 ). I have not tested if such integration works now (depends on Authorize project implementation). BTW QueueItemAuthenticator does not change the default behavior. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [promoted-builds-plugin] (JENKINS-16144) JOB_NAME var displays wrong path
Title: Message Title Oleg Nenashev commented on JENKINS-16144 Re: JOB_NAME var displays wrong path In the current version of the plugin (2.22), "Test/promotion/QA" is the right link. I didn't dig into the history, but IMO this issue is not a defect. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [promoted-builds-plugin] (JENKINS-16144) JOB_NAME var displays wrong path
Title: Message Title Oleg Nenashev resolved as Not A Defect Jenkins / JENKINS-16144 JOB_NAME var displays wrong path Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.