[JIRA] [extended-choice-parameter] (JENKINS-23359) Multi-level choice modes do not support URL paths to property files
Oleg Nenashev created JENKINS-23359 Multi-level choice modes do not support URL paths to property files Issue Type: Bug Assignee: vimil Components: extended-choice-parameter Created: 08/Jun/14 9:09 AM Description: Currently, it is not possible to specify the path by URL Environment: extended-choice-0.30 Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10577) Builds fails with JDK_Installed\jdk.exe error in both 1.423 and 1.424 versions
Daniel Beck resolved JENKINS-10577 as Incomplete Builds fails with JDK_Installed\jdk.exe error in both 1.423 and 1.424 versions Resolving: No response to comment asking for clarification in over two weeks. Change By: Daniel Beck (08/Jun/14 2:23 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-23360) Post-build actions are not getting executed in BuildFlow job.
Lokesh Govindu commented on JENKINS-23360 Post-build actions are not getting executed in BuildFlow job. I observed BuildFlow Version 0.10 works fine on Jenkins Version 1.566. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-16868) Icons are not displayed with a reverse proxy
Ignacio Sánchez commented on JENKINS-16868 Icons are not displayed with a reverse proxy I'm experiencing the same issue with the latest version. Not very smart but I used the following apache configuration to temporally solve the problem until a patch is released: ProxyPass /jenkins/jenkins/ http://localhost:7080/jenkins/ nocanon ProxyPassReverse /jenkins/jenkins/ http://localhost:7080/jenkins/ ProxyPass /jenkins/ http://localhost:7080/jenkins/ nocanon ProxyPassReverse /jenkins/ http://localhost:7080/jenkins/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23359) Multi-level choice modes do not support URL paths to property files
Oleg Nenashev started work on JENKINS-23359 Multi-level choice modes do not support URL paths to property files Change By: Oleg Nenashev (08/Jun/14 9:13 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-17262) Remotely triggered build with parameters failing with extended choice parameters
vimil resolved JENKINS-17262 as Fixed Remotely triggered build with parameters failing with extended choice parameters Change By: vimil (08/Jun/14 3:01 AM) Status: Reopened Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-23315) NPE at hudson.plugins.im.tools.BuildHelper.isFix
kutzi edited a comment on JENKINS-23315 NPE at hudson.plugins.im.tools.BuildHelper.isFix Which version of the instant-messaging plugin are you using? This method shouldn't be in use anymore. (edit: sorry, that was wrong - it's still used) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13012) Better Textformat for Not-Found-Infos
Daniel Beck resolved JENKINS-13012 as Incomplete Better Textformat for Not-Found-Infos Resolving: No response to comment asking for clarification in over two weeks. Change By: Daniel Beck (08/Jun/14 2:22 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23092) Config with an Extended Choice Parameter can't be saved
vimil resolved JENKINS-23092 as Fixed Config with an Extended Choice Parameter cant be saved fixed in 0.33 Change By: vimil (08/Jun/14 2:56 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23359) Multi-level choice modes do not support URL paths to property files
Oleg Nenashev updated JENKINS-23359 Multi-level choice modes do not support URL paths to property files Change By: Oleg Nenashev (08/Jun/14 9:10 AM) Assignee: vimil OlegNenashev Description: Currently,itisnotpossibletospecifythepathbyURL .BTW,theoptionworksforcommonmodes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21712) Jenkins Update breaks Subversion credential configuration
Bruno Medeiros commented on JENKINS-21712 Jenkins Update breaks Subversion credential configuration Same problem here, reverting to version 1.54 of subversion plugin was my only option for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23359) Multi-level choice modes do not support URL paths to property files
Oleg Nenashev commented on JENKINS-23359 Multi-level choice modes do not support URL paths to property files https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot] (JENKINS-17379) dynamically join IRC channels defined in jobs
kutzi commented on JENKINS-17379 dynamically join IRC channels defined in jobs I think it's reasonable to be able to specify the channels to notify per job. I also think that the basic configuration of the channels (especially authentication) should remain global. So defining the channels globally and then specifying per job, which channels should be notified, sounds like the way to go. Pull requests are welcome, as I'm currently not using the IRC plugin myself and so am unlikely to change this myself anytime soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23375) After deleting folder, get 404
Jesse Glick started work on JENKINS-23375 After deleting folder, get 404 Change By: Jesse Glick (09/Jun/14 4:31 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23228) Support the range notation for pagination in API
SCM/JIRA link daemon resolved JENKINS-23228 as Fixed Support the range notation for pagination in API Change By: SCM/JIRA link daemon (08/Jun/14 5:17 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-23363) View tabs not visible or accessible after Build Pipeline plugin update to version 1.4.3
Jason Spotswood created JENKINS-23363 View tabs not visible or accessible after Build Pipeline plugin update to version 1.4.3 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 09/Jun/14 2:09 AM Description: After upgrading to Jenkins 1.566, I also updated a number of plugins. After the upgrade the view tabs were no longer visible and attempting to access them directly resulted in the set of exceptions listed below. After a bit of playing around with downgrading and then re-upgrading versions, I found that the Build Pipeline plugin upgrade to version 1.4.3 was the cause of this problem. Reverting back to 1.4.2 fixes this issue. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/master/apache-tomcat-7.0.42/webapps/jenkins/WEB-INF/lib/jenkins-core-1.566.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/master/apache-tomcat-7.0.42/webapps/jenkins/WEB-INF/lib/jenkins-core-1.566.jar!/lib/hudson/projectView.jelly:66:22: d:invokeBody java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) 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:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at
[JIRA] [core] (JENKINS-22758) Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)
Kohsuke Kawaguchi resolved JENKINS-22758 as Fixed Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin) This is fixed in remoting 2.41. Change By: Kohsuke Kawaguchi (09/Jun/14 9:12 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20815) Show Failed Status While the Build is Still In Progress
Danny Staple commented on JENKINS-20815 Show Failed Status While the Build is Still In Progress we are seeing this in our system now - on a master/slave both on linux, and free-style software project both with and without concurreny, on version 1.554.1. THe job appars to continue on the slave, complete and mark the status as passed later. This appeared to be caused by a hiccup that left us with 2 slave instances pointing at the same workspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23250) Failed to inspect ... build.xml warnings in jenkins log
Daniel Beck resolved JENKINS-23250 as Cannot Reproduce Failed to inspect ... build.xml warnings in jenkins log Don't report issues against obsolete core versions. There's a solid chance it's already been fixed, and you're just wasting others' time. This particular issue was mostly resolved in 1.559: Jenkins no longer tries to load non-existing files. Change By: Daniel Beck (09/Jun/14 10:40 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22892) DSL for initial Base ClearCase support
SCM/JIRA link daemon commented on JENKINS-22892 DSL for initial Base ClearCase support Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Job-DSL-Commands.md docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/ScmContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/ClearCaseContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/e7ba5ad10cba62cc01a0468da300e4c4836b48af Log: Merge branch 'JENKINS-22892' Conflicts: docs/Home.md Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/da8a1ee4137f...e7ba5ad10cba This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5650) Wrong charset entry in build.xml after hudson-Upgrade
Daniel Beck resolved JENKINS-5650 as Cannot Reproduce Wrong charset entry in build.xml after hudson-Upgrade Resolving: No response to comment asking for updated information in over two weeks. Due to the age of this issue, please file a new issue if this still occurs on recent Jenkins/Perforce plugin versions. Change By: Daniel Beck (08/Jun/14 2:25 PM) Status: Reopened Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
ciaranj edited a comment on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported As requested by Kohsuke Kawaguchi attached is the stack-trace I'm seeing: Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 197 iota=480 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:277) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:300) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: java.lang.Exception: Object was recently deallocated #197 (ref.0) : hudson.CloseProofOutputStream Created at Wed Jun 04 16:11:05 BST 2014 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:86) at hudson.remoting.ExportTable.export(ExportTable.java:239) at hudson.remoting.Channel.export(Channel.java:592) at hudson.remoting.RemoteOutputStream.writeObject(RemoteOutputStream.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:959) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1480) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at hudson.remoting.UserRequest.init(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:738) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:888) at hudson.Launcher$ProcStarter.start(Launcher.java:355) at hudson.Launcher$ProcStarter.join(Launcher.java:362) at hudson.plugins.msbuild.MsBuildBuilder.perform(MsBuildBuilder.java:180) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Released at Wed Jun 04 16:17:53 BST 2014 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:115) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:303) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.ProxyOutputStream$Unexport$1.run(ProxyOutputStream.java:352) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:270) ... 5 more Caused by: Released at
[JIRA] [git] (JENKINS-23362) Allow RevisionParameterAction To Support Merges
Daniel Brooks created JENKINS-23362 Allow RevisionParameterAction To Support Merges Issue Type: New Feature Assignee: Nicolas De Loof Components: git Created: 08/Jun/14 9:50 PM Description: The RevisionParameterAction needs a way to support git merges by specific the target and source branch. Project: Jenkins Priority: Major Reporter: Daniel Brooks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-23315) NPE at hudson.plugins.im.tools.BuildHelper.isFix
SCM/JIRA link daemon commented on JENKINS-23315 NPE at hudson.plugins.im.tools.BuildHelper.isFix Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/plugins/im/tools/BuildHelper.java http://jenkins-ci.org/commit/instant-messaging-plugin/043049283a7ce610c532df0da62ff299fe70d60c Log: FIXED JENKINS-23315 potential NPE if previous build is still running This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23375) After deleting folder, get 404
SCM/JIRA link daemon commented on JENKINS-23375 After deleting folder, get 404 Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractItem.java test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/34f885b73f3a054c6de3e25f47b0e464d9a4df3f Log: FIXED JENKINS-23375 Incorrect redirect after deleting a folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-23315) NPE at hudson.plugins.im.tools.BuildHelper.isFix
kutzi commented on JENKINS-23315 NPE at hudson.plugins.im.tools.BuildHelper.isFix Which version of the instant-messaging plugin are you using? This method shouldn't be in use anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23375) After deleting folder, get 404
SCM/JIRA link daemon resolved JENKINS-23375 as Fixed After deleting folder, get 404 Change By: SCM/JIRA link daemon (09/Jun/14 5:28 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-23343) Validation of Docker URL
SCM/JIRA link daemon commented on JENKINS-23343 Validation of Docker URL Code changed in jenkins User: Vojtech Juranek Path: src/main/java/org/jenkinsci/plugins/dockerbuildstep/DockerBuilder.java src/main/resources/org/jenkinsci/plugins/dockerbuildstep/DockerBuilder/global.jelly http://jenkins-ci.org/commit/docker-build-step-plugin/6205fac97bb376f73c1551904739f281d5854eb3 Log: FIXED JENKINS-23343 Implement validation button for Docker URL in global config This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Daniel Beck commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break Eric Anker: Improved reverse proxy brokenness detection was added in 1.552. If you have a way to set up a second context with a new versions to see whether it complains would be interesting to learn. That being said, is the following relevant to your setup? http://tomcat.apache.org/connectors-doc/reference/apache.html#Forwarding Try to set JkOptions +ForwardURICompatUnparsed Please report back if you get this fixed, as that'd help us improve the docs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22228) Cannot save setting on configure global security page
Daniel Beck commented on JENKINS-8 Cannot save setting on configure global security page How are you running Jenkins? What's the security realm you selected, and how did you configure it? Could you provide a screenshot of the form before you submit it so we can see the values you're sending, or capture the POST request's parameters from your browser's debug console? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22720) Non-recursive ListViews unnecessarily call owner.getAllItems in getItems
SCM/JIRA link daemon commented on JENKINS-22720 Non-recursive ListViews unnecessarily call owner.getAllItems in getItems Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/ListView.java test/src/test/java/hudson/model/ListViewTest.java http://jenkins-ci.org/commit/jenkins/819c1f1bdad2d83aa8a9033f23e4dd079b10118a Log: FIXED JENKINS-22720 Only call getAllItems in recursive ListView (cherry picked from commit df9adaf8f1e23d57c60ec9fb9313287f6d458c7c) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22892) DSL for initial Base ClearCase support
SCM/JIRA link daemon commented on JENKINS-22892 DSL for initial Base ClearCase support Code changed in jenkins User: Christian Galsterer Path: job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/c55eb755ba1a73d376baa23805fa4549d322bfbc Log: JENKINS-22892 DSL for initial Base ClearCase support fixed pull request comments use system specific line separator instead of \n This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22600) Sub-projects appeared as Static and Other executed recently at job main page
Gosha Frost assigned JENKINS-22600 to huybrechts Sub-projects appeared as Static and Other executed recently at job main page Re-assign to the leader of project Change By: Gosha Frost (08/Jun/14 9:58 AM) Assignee: DominikBartholdi huybrechts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23179) git pre-merge fails with matrix project
Marshall Galbraith commented on JENKINS-23179 git pre-merge fails with matrix project I created a unit test that reproduces the problem, and created a fix. Both are available with this pull request: https://github.com/jenkinsci/git-plugin/pull/235 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7827) Workspace cleared randomly causing jobs to fail
Daniel Beck resolved JENKINS-7827 as Cannot Reproduce Workspace cleared randomly causing jobs to fail Resolving: No response to comment asking for updated information in over two weeks. Due to the age of this issue, please file a new issue if this still occurs on recent Jenkins/Perforce plugin versions. Change By: Daniel Beck (08/Jun/14 2:25 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23373) Stack trace on rename or delete
Patrik Boström commented on JENKINS-23373 Stack trace on rename or delete Looks like this can happen for view with just Regular _expression_ for matching pipelines first jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23364) Rename hudson-dev:run to jenkins-dev:run
Harald Albers commented on JENKINS-23364 Rename hudson-dev:run to jenkins-dev:run updated https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins: use jenkins-dev:run instead of hudson-dev:run This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-23181) NPE caused by copy artifcats while renaming job
ikedam
commented on JENKINS-23181
NPE caused by copy artifcats while renaming job
This means you have a broken "Copy artifacts from another project".
I want to know what broke that configuration (you cannot create that broken configuration in usual ways).
Let me know:
Did you upgrade copyartifact-plugin from a version 1.26 ?
The configuration file format is changed since 1.25. This problem may be caused for the bad migration of configuration files.
Is there any strange logs when you starts Jenkins?
Migration of the configuration files is performed when Jenkins starts up. If some problems happen in the migration process, there would be error logs.
Let me see config.xml of the project with broken "Copy artifacts from another project" if you can find that.
Correct copyartifact configurations are like this in ${JENKINS_HOME}/jobs/PROJECTNAME/config.xml:
...
hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.30"
projectprojectCopiedFrom/project
filterartifact.zip/filter
target/target
selector class="hudson.plugins.copyartifact.StatusBuildSelector"/
doNotFingerprintArtifactsfalse/doNotFingerprintArtifacts
/hudson.plugins.copyartifact.CopyArtifact
...
In your case, it sounds like a project tag does not exist (not only be empty, but not exist).
If there are many projects in your Jenkins, it would be difficult to find out that.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22892) DSL for initial Base ClearCase support
Daniel Spilker resolved JENKINS-22892 as Fixed DSL for initial Base ClearCase support Will be released in 1.24. Change By: Daniel Spilker (09/Jun/14 9:42 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23367) abort reason
Adam Guja created JENKINS-23367 abort reason Issue Type: Improvement Assignee: Unassigned Components: core Created: 09/Jun/14 5:48 AM Description: prompt user for abort reason upon abort and add it to build description Project: Jenkins Priority: Major Reporter: Adam Guja This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-8723) Computing changelog fails: incomplete argument list
Michael Clarke resolved JENKINS-8723 as Fixed Computing changelog fails: incomplete argument list Fixed under version 2.0 of the plugin with move to rlog to build version information Change By: Michael Clarke (08/Jun/14 4:30 PM) Status: Open Resolved Assignee: MichaelClarke Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
SCM/JIRA link daemon commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jenkinsci/remoting/nio/Closeables.java http://jenkins-ci.org/commit/remoting/4bb086e15c88e2756e6c90987466a8af8c593b75 Log: JENKINS-22932 shutdownInput/Output is not idempotent, so attempting to reclose a closed socket fails. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23373) Stack trace on rename or delete
Marcus Philip created JENKINS-23373 Stack trace on rename or delete Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline Created: 09/Jun/14 12:52 PM Description: We get a stack trace on rename or delete since upgrade. Job is renamed/deleted. Plugin Version: 0.7.4 Jenkins Version: 1.565 Rename javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at
[JIRA] [delivery-pipeline] (JENKINS-23353) Using a Delivery Pipeline view as the default view in Jenkins breaks the New Item sidebar link
Patrik Boström resolved JENKINS-23353 as Fixed Using a Delivery Pipeline view as the default view in Jenkins breaks the New Item sidebar link Merged to master Change By: Patrik Boström (09/Jun/14 11:24 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
SCM/JIRA link daemon commented on JENKINS-19310 Incorrect links in build history when view is defined inside a folder Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/ListView.java core/src/main/resources/hudson/model/View/builds.jelly test/src/test/java/jenkins/widgets/BuildListTableTest.java http://jenkins-ci.org/commit/jenkins/00ab6012b8607b5290aa0bf88fc2f55c5cd36caa Log: JENKINS-19310 Reproduced problem in test. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Kohsuke Kawaguchi resolved JENKINS-13995 as Fixed Would like the ability to disable hover-over context menus. 1.513 has the last substantial change on the way context menu is displayed; in this version, a small 'v' icon appears to the next of links, and clicking on it reveals the context menu. This issue was originally reported against 1.464 that had a very different implementation. I consider the change in 1.513 to have sufficiently addressed the original issue of the reporter. Future enhancement requests to the way context menu behaves should be filed as separate tickets. Change By: Kohsuke Kawaguchi (09/Jun/14 9:21 PM) Status: InProgress Resolved Assignee: KohsukeKawaguchi Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-18710) Selected Let Jenkins auto-manage hook URLs, but never adds webhook to enterprise github
SCM/JIRA link daemon commented on JENKINS-18710 Selected Let Jenkins auto-manage hook URLs, but never adds webhook to enterprise github Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/com/cloudbees/jenkins/GitHubWebHook.java http://jenkins-ci.org/commit/github-plugin/e0b8050d78dc836495ef403fec6988a970f6225b Log: FIXED JENKINS-18710 merge pull request #31 Compare: https://github.com/jenkinsci/github-plugin/compare/6553654a7884...e0b8050d78dc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23365) Allow SCM to work with non-AbstractProject
Jesse Glick created JENKINS-23365 Allow SCM to work with non-AbstractProject Issue Type: Task Assignee: Jesse Glick Components: core Created: 09/Jun/14 3:36 AM Description: SCM historically was tied to AbstractProject/AbstractBuild. It is necessary to break that dependency and allow other kinds of Job/Run to use this API (with modest accompanying changes in SCM plugins). Project: Jenkins Labels: api scm workflow Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-23358) Integration with Promoted Builds Plugins
Ignacio Sánchez created JENKINS-23358 Integration with Promoted Builds Plugins Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer Created: 08/Jun/14 12:59 AM Description: Integrate the plugin with the Promoted Builds Plugin so the analysis can also be configured on the promotion output and solutions can be offered to failed promotion processes. Project: Jenkins Priority: Minor Reporter: Ignacio Sánchez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22991) Restart would not properly display username if user was not loaded.
SCM/JIRA link daemon commented on JENKINS-22991 Restart would not properly display username if user was not loaded. Code changed in jenkins User: Nicolas De loof Path: core/src/main/java/hudson/model/Cause.java http://jenkins-ci.org/commit/jenkins/fde98adfd054eb3a73ea5f8997124b1a7d98a3b4 Log: JENKINS-22991 Merge pull request #1167 from christ66/ZD-16606 Fix issue where restart would not properly display username if user was not loaded. (cherry picked from commit 22e64ab7c26313e9336f168020fbd90bd9caabbd) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge] (JENKINS-23371) Manually-triggered integration
Chris Platts created JENKINS-23371 Manually-triggered integration Issue Type: New Feature Affects Versions: current Assignee: Kohsuke Kawaguchi Components: svnmerge Created: 09/Jun/14 9:56 AM Description: Hi, Perhaps this is already available, but I just can't find it! Is there a way to trigger a manual reintegration of a branch job to its parent? I understand that there's the post-build action that can be added to do this automatically after each build of the branch, but I'd prefer to only reintegrate once we've decided to do so. I tried reintegrating the branch as normal via my SVN client, thinking that perhaps the plugin would magically pick that up, but no joy. Project: Jenkins Priority: Minor Reporter: Chris Platts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23365) Allow SCM to work with non-AbstractProject
SCM/JIRA link daemon commented on JENKINS-23365 Allow SCM to work with non-AbstractProject Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Cause.java core/src/main/java/hudson/model/listeners/SCMListener.java core/src/main/java/hudson/scm/AbstractScmTagAction.java core/src/main/java/hudson/scm/ChangeLogAnnotator.java core/src/main/java/hudson/scm/ChangeLogParser.java core/src/main/java/hudson/scm/ChangeLogSet.java core/src/main/java/hudson/scm/SCM.java core/src/main/java/hudson/scm/SCMDescriptor.java core/src/main/java/hudson/triggers/SCMTrigger.java core/src/main/java/jenkins/triggers/SCMTriggerItem.java http://jenkins-ci.org/commit/jenkins/7423d30e9e3599889597547295e1a8a659fb19d5 Log: FIXED JENKINS-23365 Noting merge of #1257. Compare: https://github.com/jenkinsci/jenkins/compare/c95777e47638...7423d30e9e35 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23365) Allow SCM to work with non-AbstractProject
dogfood commented on JENKINS-23365 Allow SCM to work with non-AbstractProject Integrated in jenkins_main_trunk #3444 FIXED JENKINS-23365 Noting merge of #1257. (Revision 7423d30e9e3599889597547295e1a8a659fb19d5) Result = SUCCESS Jesse Glick : 7423d30e9e3599889597547295e1a8a659fb19d5 Files : core/src/main/java/hudson/model/listeners/SCMListener.java core/src/main/java/hudson/scm/ChangeLogAnnotator.java core/src/main/java/hudson/model/Cause.java core/src/main/java/hudson/scm/ChangeLogParser.java core/src/main/java/hudson/triggers/SCMTrigger.java core/src/main/java/jenkins/triggers/SCMTriggerItem.java core/src/main/java/hudson/scm/SCM.java changelog.html core/src/main/java/hudson/scm/SCMDescriptor.java core/src/main/java/hudson/scm/ChangeLogSet.java core/src/main/java/hudson/scm/AbstractScmTagAction.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23238) Single and Multi select multi level choice does not work.
vimil resolved JENKINS-23238 as Fixed Single and Multi select multi level choice does not work. fixed in 0.33. The multilevel parameters are moved to separate section in the config. Change By: vimil (08/Jun/14 2:55 AM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-23343) Validation of Docker URL
SCM/JIRA link daemon resolved JENKINS-23343 as Fixed Validation of Docker URL Change By: SCM/JIRA link daemon (07/Jun/14 9:13 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-23315) NPE at hudson.plugins.im.tools.BuildHelper.isFix
SCM/JIRA link daemon resolved JENKINS-23315 as Fixed NPE at hudson.plugins.im.tools.BuildHelper.isFix Change By: SCM/JIRA link daemon (08/Jun/14 10:29 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-23369) Unable to check-in using bypass mode
Szymon Michna created JENKINS-23369 Unable to check-in using bypass mode Issue Type: Improvement Assignee: Cletus DSouza Components: integrity-plugin Created: 09/Jun/14 9:35 AM Description: I have got an Integrity project that is configured with mandatory change packages, but I want to check in files using bypass mode. I have got such a permission, but I have to pass ItemId as a build parameter. "Bypass" value is not working. In the IntegrityCheckinTask.java file: https://github.com/jenkinsci/integrity-plugin/blob/master/src/main/java/hudson/scm/IntegrityCheckinTask.java there is the invoke method which creates a change package at the beginning. It would be great to have an IF clause, which will check if the parameter equals "bypass" and in this case won't create a change package and check in files using "bypass" mode. Project: Jenkins Labels: ptc integrity Priority: Major Reporter: Szymon Michna This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-22502) Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue
Daniel Beck commented on JENKINS-22502 Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue Matrix parent should use a one-off executor and not block regular tasks. Did you disable flyweight support? What's the output of Jenkins.FLYWEIGHT_SUPPORT in Script Console? Could you provide a screenshot of the queue and executors list when you're "stuck"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23250) Failed to inspect ... build.xml warnings in jenkins log
Daniel Beck updated JENKINS-23250 Failed to inspect ... build.xml warnings in jenkins log Change By: Daniel Beck (09/Jun/14 10:36 AM) Component/s: core Component/s: build-blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23164) Password option is not getting updated in Chrome
Oleg Nenashev assigned JENKINS-23164 to Oleg Nenashev Password option is not getting updated in Chrome Change By: Oleg Nenashev (09/Jun/14 8:38 AM) Assignee: OlegNenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-23376) How to push artifacts in jenkin maven plugin repo ?
Daniel Beck resolved JENKINS-23376 as Not A Defect How to push artifacts in jenkin maven plugin repo ? This is an issue tracker, not a support site. If you have a question you want answered, try the mailing lists, IRC, or Stack Overflow. Change By: Daniel Beck (09/Jun/14 5:13 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18613) Smaller description boxes
Daniel Beck resolved JENKINS-18613 as Incomplete Smaller description boxes Resolving: No response to comment asking for clarification in over two weeks. Change By: Daniel Beck (08/Jun/14 2:34 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22892) DSL for initial Base ClearCase support
SCM/JIRA link daemon commented on JENKINS-22892 DSL for initial Base ClearCase support Code changed in jenkins User: Christian Galsterer Path: docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/ScmContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/ClearCaseContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/cd5cbf9e5487ec356f4c342b0ba4ba19c65afb99 Log: JENKINS-22892 DSL for initial Base ClearCase support fixed pull request comments Added more examples Allow multiple calls for configSpec, loadRules and mkviewOptionalParameter including varargs parameter call validateMulti() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
dogfood commented on JENKINS-19310 Incorrect links in build history when view is defined inside a folder Integrated in jenkins_main_trunk #3447 JENKINS-19310 Reproduced problem in test. (Revision 00ab6012b8607b5290aa0bf88fc2f55c5cd36caa) Result = SUCCESS Jesse Glick : 00ab6012b8607b5290aa0bf88fc2f55c5cd36caa Files : test/src/test/java/jenkins/widgets/BuildListTableTest.java core/src/main/resources/hudson/model/View/builds.jelly core/src/main/java/hudson/model/ListView.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-11550) Configurable path for slave logfiles
Oleg Nenashev resolved JENKINS-11550 as Incomplete Configurable path for slave logfiles No clarification from the submitter. Jenkins slaves can store logs locally, so no idea if the request is actual Change By: Oleg Nenashev (09/Jun/14 12:16 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22760) Request for new slave-specific permission in Jenkins core
Daniel Beck commented on JENKINS-22760 Request for new slave-specific permission in Jenkins core Could you please explain the need for this permission? I have a difficult time coming up with a reason that doesn't start by using Jenkins in really weird ways. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [custom-tools] (JENKINS-18814) Renaming of the tool corrupts jobs (obsolete data)
Oleg Nenashev resolved JENKINS-18814 as Fixed Renaming of the tool corrupts jobs (obsolete data) Fixed in 0.4.2 Change By: Oleg Nenashev (09/Jun/14 12:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-14565) Please add support for Cloudbees folder structure
Octavio Martin commented on JENKINS-14565 Please add support for Cloudbees folder structure I can see my jobs in the pipeline and any chain of automatic jobs works fine, but I cannot execute any manual step in that chain, when button is clicked, it does nothing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23375) After deleting folder, get 404
Jesse Glick created JENKINS-23375 After deleting folder, get 404 Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Jun/14 4:30 PM Description: As of https://github.com/jenkinsci/jenkins/commit/da79f7b (in 1.556), if you delete a folder, you are redirected to its location, which is now a 404, rather than to its parent as expected. Environment: reproduced in 1.562 Project: Jenkins Labels: regression folders Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22786) Jenkins job hangs and can't be killed
Daniel Beck resolved JENKINS-22786 as Cannot Reproduce Jenkins job hangs and cant be killed Issue needs to be reproduced without Netbeans profiler interfering. Resolving as Cannot Reproduce after 4 weeks without updates. Change By: Daniel Beck (09/Jun/14 12:53 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook] (JENKINS-23370) Gitlab web hook fails when Cross Site Request Forgery protection is active
Jean-Christophe Sirot created JENKINS-23370 Gitlab web hook fails when Cross Site Request Forgery protection is active Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: gitlab-hook Created: 09/Jun/14 9:39 AM Description: When the CSRF protection is set, the web hook requests fail with Jun 9, 2014 9:31:58 AM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /gitlab/notify_commit. Returning 403. because the POST request does not use a crumb. The plugin should implement a CrumbExclusion like the gitbucket plugin (see https://github.com/jenkinsci/gitbucket-plugin/blob/master/src%2Fmain%2Fjava%2Forg%2Fjenkinsci%2Fplugins%2Fgitbucket%2FGitBucketWebHook.java) Project: Jenkins Priority: Blocker Reporter: Jean-Christophe Sirot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-19754) Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
Seán Dunne
edited a comment on JENKINS-19754
Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
I have noticed this same issue.
My ${WORKSPACE} variable is set to the slave FS root since I've installed the EnvInject plugin.
However when trying the workaround it doesn't seem to work.
Jenkins version: 1.532.3
Environment Injector Plugin version: 1.89
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
ciaranj commented on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported As requested by Kohsuke Kawaguchi attached is the stack-trace I'm seeing: Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 197 iota=480 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:277) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:300) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: java.lang.Exception: Object was recently deallocated #197 (ref.0) : hudson.CloseProofOutputStream Created at Wed Jun 04 16:11:05 BST 2014 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:86) at hudson.remoting.ExportTable.export(ExportTable.java:239) at hudson.remoting.Channel.export(Channel.java:592) at hudson.remoting.RemoteOutputStream.writeObject(RemoteOutputStream.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:959) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1480) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at hudson.remoting.UserRequest.init(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:738) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:888) at hudson.Launcher$ProcStarter.start(Launcher.java:355) at hudson.Launcher$ProcStarter.join(Launcher.java:362) at hudson.plugins.msbuild.MsBuildBuilder.perform(MsBuildBuilder.java:180) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1710) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Released at Wed Jun 04 16:17:53 BST 2014 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:115) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:303) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.ProxyOutputStream$Unexport$1.run(ProxyOutputStream.java:352) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:270) ... 5 more Caused by: Released at Wed
[JIRA] [core] (JENKINS-18387) Jenkins sometimes fails to restart successfully
Daniel Beck resolved JENKINS-18387 as Incomplete Jenkins sometimes fails to restart successfully Resolving: No response to comment asking for updated information in over two weeks. Due to the age of this issue, please file a new issue if this still occurs on recent (1.558+) Jenkins versions. Change By: Daniel Beck (08/Jun/14 2:33 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23238) Single and Multi select multi level choice does not work.
vimil started work on JENKINS-23238 Single and Multi select multi level choice does not work. Change By: vimil (08/Jun/14 2:53 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23310) Code signing certificate of winp.dll has expired
Oleg Nenashev updated JENKINS-23310 Code signing certificate of winp.dll has expired Kohsuke is an owner of the WinP library project Change By: Oleg Nenashev (09/Jun/14 12:24 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23361) Add CLI commands to add jobs to and remove jobs from views
Oliver Gondža updated JENKINS-23361 Add CLI commands to add jobs to and remove jobs from views Change By: Oliver Gondža (08/Jun/14 7:31 PM) Summary: AddCLIcommandstoadd /remove jobsto / andremovejobs fromviews This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23367) Require user to enter reason for manual build abortion
Daniel Beck updated JENKINS-23367 Require user to enter reason for manual build abortion Change By: Daniel Beck (09/Jun/14 12:34 PM) Summary: abort Requireusertoenter reason formanualbuildabortion Issue Type: Improvement NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Daniel Beck edited a comment on JENKINS-23094 HTTP error 405 when trying to restart ssh host Likely introduced in 1.561 by https://github.com/jenkinsci/jenkins/pull/877/files#diff-a5d5dbfd01aa9be491143dc82df503a6R559 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-22668) Source Code Management section defaults to method that is not in use
Michael Clarke commented on JENKINS-22668 Source Code Management section defaults to method that is not in use Not a CVS issue (CVS is bundled with Jenkins, so would be shown if this was the only SCM option available). Suspect there was an issue that was causing Perforce not to be able to load properly, but can't replicate. Closing issue for now. Please re-open with further details if you can replicate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
SCM/JIRA link daemon resolved JENKINS-22932 as Fixed Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Change By: SCM/JIRA link daemon (09/Jun/14 7:25 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-23360) Post-build actions are not getting executed in BuildFlow job.
Lokesh Govindu created JENKINS-23360 Post-build actions are not getting executed in BuildFlow job. Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow Created: 08/Jun/14 11:14 AM Description: I have upgraded my Jenkins to 1.566 version, after than post-build actions (like set build description, editable email notification) are not getting executed. Environment: OS: Windows 8 64-bit Fix Versions: current Project: Jenkins Priority: Major Reporter: Lokesh Govindu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
Jesse Glick updated JENKINS-19310 Incorrect links in build history when view is defined inside a folder Fix is too risky to be an LTS candidate. Change By: Jesse Glick (09/Jun/14 7:32 PM) Labels: folders lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
SCM/JIRA link daemon
commented on JENKINS-19310
Incorrect links in build history when view is defined inside a folder
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/hudson/model/AbstractItem.java
core/src/main/java/jenkins/model/Jenkins.java
core/src/main/java/jenkins/util/ProgressiveRendering.java
core/src/main/resources/hudson/model/Computer/builds.jelly
core/src/main/resources/hudson/model/User/builds.jelly
core/src/main/resources/hudson/model/View/builds.jelly
core/src/main/resources/lib/hudson/buildListTable.jelly
test/src/test/java/hudson/model/MyViewTest.java
test/src/test/java/jenkins/widgets/BuildListTableTest.java
http://jenkins-ci.org/commit/jenkins/ea95434938b2111d8768528823990a78bdc58d3e
Log:
FIXED JENKINS-19310 Provide correct links for build history inside a folder.
The basic fix is to use ${rootURL} plus full model object URLs rather than relying on ${jobBaseUrl}.
This is made trickier by the fact that the model object URLs are computed inside ProgressiveRendering.compute,
and therefore will not be correct when nondefault views are in the crumb trail unless the original request information is present.
So modifying ProgressiveRendering to preserve a copy of the original request for use during computation.
(This could probably be used to simplify parts of AsynchPeople as well.)
Also improving AbstractItem.getUrl to properly construct a URL including views even when the current page is not inside the item;
it should suffice for some ancestor of the current item (or a view thereof) to be in the ancestor list of this page.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
SCM/JIRA link daemon resolved JENKINS-19310 as Fixed Incorrect links in build history when view is defined inside a folder Change By: SCM/JIRA link daemon (09/Jun/14 10:13 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [artifactory] (JENKINS-20554) The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs
lior hasson started work on JENKINS-20554 The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs Change By: lior hasson (09/Jun/14 7:04 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22853) SEVERE: Trying to unexport an object that's already unexported
Gardner Bickford commented on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported SEVERE: Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 69 iota=136 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:277) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:300) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.AbstractByteArrayCommandTransport$1.handle(AbstractByteArrayCommandTransport.java:61) at org.jenkinsci.remoting.nio.NioChannelHub$2.run(NioChannelHub.java:529) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.Exception: Object was recently deallocated #69 (ref.0) : hudson.CloseProofOutputStream Created at Mon Jun 09 09:51:00 PDT 2014 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:86) at hudson.remoting.ExportTable.export(ExportTable.java:239) at hudson.remoting.Channel.export(Channel.java:592) at hudson.remoting.RemoteOutputStream.writeObject(RemoteOutputStream.java:82) at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1429) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1175) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) at hudson.util.StreamTaskListener.writeObject(StreamTaskListener.java:161) at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1429) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1175) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1541) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1506) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1429) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1175) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1541) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1506) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1429) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1175) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1541) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1506) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1429) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1175) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at hudson.remoting.UserRequest.init(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:738) at hudson.FilePath.act(FilePath.java:909) at hudson.FilePath.act(FilePath.java:893) at
[JIRA] [core] (JENKINS-23228) Support the range notation for pagination in API
dogfood commented on JENKINS-23228 Support the range notation for pagination in API Integrated in jenkins_main_trunk #3443 FIXED JENKINS-23228 (Revision c95777e47638fa7483611a2a09a4b26de8e9a327) Result = SUCCESS kohsuke : c95777e47638fa7483611a2a09a4b26de8e9a327 Files : core/pom.xml changelog.html core/src/main/resources/hudson/model/Api/index.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22892) DSL for initial Base ClearCase support
SCM/JIRA link daemon commented on JENKINS-22892 DSL for initial Base ClearCase support Code changed in jenkins User: Christian Galsterer Path: docs/Home.md docs/Job-DSL-Commands.md docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/ScmContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/ead661626f40b1845cca0e5fc25f7b983c996a18 Log: JENKINS-22892 DSL for initial Base ClearCase support This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
Jesse Glick assigned JENKINS-19310 to Jesse Glick Incorrect links in build history when view is defined inside a folder Change By: Jesse Glick (09/Jun/14 4:49 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23375) After deleting folder, get 404
dogfood commented on JENKINS-23375 After deleting folder, get 404 Integrated in jenkins_main_trunk #3445 FIXED JENKINS-23375 Incorrect redirect after deleting a folder. (Revision 34f885b73f3a054c6de3e25f47b0e464d9a4df3f) Result = SUCCESS Jesse Glick : 34f885b73f3a054c6de3e25f47b0e464d9a4df3f Files : changelog.html core/src/main/java/hudson/model/AbstractItem.java test/src/test/groovy/hudson/model/AbstractProjectTest.groovy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [koji-plugin] (JENKINS-23374) Reuse git SCM URL from plugins
Vaclav Tunka created JENKINS-23374 Reuse git SCM URL from plugins Issue Type: Bug Assignee: Vaclav Tunka Components: koji-plugin Created: 09/Jun/14 2:36 PM Description: Users shouldn't fill the git SCM URL twice, plugin should be able to construct git+https://*.git#hash Project: Jenkins Priority: Major Reporter: Vaclav Tunka This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23365) Allow SCM to work with non-AbstractProject
Jesse Glick started work on JENKINS-23365 Allow SCM to work with non-AbstractProject Change By: Jesse Glick (09/Jun/14 3:49 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [koji-plugin] (JENKINS-23374) Reuse git SCM URL from plugins
Vaclav Tunka updated JENKINS-23374 Reuse git SCM URL from plugins Change By: Vaclav Tunka (09/Jun/14 2:37 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
Jesse Glick started work on JENKINS-19310 Incorrect links in build history when view is defined inside a folder Change By: Jesse Glick (09/Jun/14 4:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23361) Add CLI commands to add/remove jobs to/from views
Oliver Gondža created JENKINS-23361 Add CLI commands to add/remove jobs to/from views Issue Type: New Feature Assignee: Oliver Gondža Components: core Created: 08/Jun/14 7:29 PM Project: Jenkins Priority: Major Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-20140) GitHub Web Hook does not work unless Prevent Cross Site Request Forgery exploits is disabled
SCM/JIRA link daemon resolved JENKINS-20140 as Fixed GitHub Web Hook does not work unless Prevent Cross Site Request Forgery exploits is disabled Change By: SCM/JIRA link daemon (08/Jun/14 7:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23356) NTLM Proxy issue - authentication fails
Jim Goodspeed resolved JENKINS-23356 as Not A Defect NTLM Proxy issue - authentication fails This turned out to be an issue with our corporate proxy. Change By: Jim Goodspeed (09/Jun/14 5:50 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-22722) Master doesn't show connected slave
Ryan Croom commented on JENKINS-22722 Master doesnt show connected slave We experienced the exact same issue with the same log information that Michaël commented with. A master restart would bring things back to normal until we restarted the slave and then subsequent connections would fail until the master was restarted again. Reverting to 1.559 fixed the issue. Our Jenkins machine is running on ArchLinux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-12093) Allow per-project category throttling on the same job
Geoff Cummings commented on JENKINS-12093 Allow per-project category throttling on the same job Pull request submitted for this: https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/20 Currently no UI changes, but it will allow () Throttle by project alone () Also throttle by one or more categories per existing code, if project values are 0, then no throttling by project will occur. all feedback welcome. Geoff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
