[JIRA] [htmlpublisher-plugin] (JENKINS-31142) HTML reports not showing up since 10/22/15
Title: Message Title Adele Zhou created an issue Jenkins / JENKINS-31142 HTML reports not showing up since 10/22/15 Issue Type: Bug Assignee: Unassigned Components: htmlpublisher-plugin Created: 23/Oct/15 6:24 PM Priority: Major Reporter: Adele Zhou HTML reports not showing up since the morning of 10/22. When I zip it, I see my report. I noticed this line is missing in htmlpublisher-wrapper.html: index Add Comment
[JIRA] [htmlpublisher-plugin] (JENKINS-22191) Not able to see HTML Publish Reports
Title: Message Title Adele Zhou commented on JENKINS-22191 Re: Not able to see HTML Publish Reports HTML reports not showing up since the morning of 10/22. When I zip it, I see my reports. I noticed this line is missing in htmlpublisher-wrapper.html: index Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30330) TFS plug-in 4.0.0 lists all workspaces on server
Title: Message Title Rahul Mahulkar commented on JENKINS-30330 Re: TFS plug-in 4.0.0 lists all workspaces on server It take 6-7 ,minutes to list all workspaces. Please provide workaround at least. Regards, Rahul Mahulkar Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31143) Memory Leak
Title: Message Title Chris Hightower created an issue Jenkins / JENKINS-31143 Memory Leak Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Oct/15 6:35 PM Environment: Jenkins v 1.634 Windows Server 2008 R2 Standard, SP1 x64 Active Plugins -- Active Directory Plugin v 1.41 Hudson Ruby Plugin v 1.2 Maven Integration plugin 2.12.1 Mercurial Plugin 1.54 Powershell plugin 1.3 View Job Filters plugin 1.27 Java memory configuation: -Xmx1024m Labels: outofmemoryerror memory-leak Priority: Minor Reporter: Chris Hightower OutOfMemory errors after several hours of Jenkins uptime Java heap dump located at: http://downloads.amarillo.gov/IT/heapdump.hprof
[JIRA] [workflow-plugin] (JENKINS-31118) Workflow jobs that are waiting for input should have a visual cue in build history
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31118 Workflow jobs that are waiting for input should have a visual cue in build history Change By: Jesse Glick Labels: workflow ux Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31118) Workflow jobs that are waiting for input should have a visual cue in build history
Title: Message Title Jesse Glick commented on JENKINS-31118 Re: Workflow jobs that are waiting for input should have a visual cue in build history Yes this is a long-discussed RFE. With the stage view (at job level) you do get a special badge on those build rows waiting for input, which could be made more prominent, but anyway we still need some mechanism (on a view page, perhaps) for showing you all builds of any job awaiting approval (ideally filtered by those you could actually approve, when submitter is specified). Adding a list view column is too intrusive. I think Jenkins needs a general-purpose notification system that the input step could hook into. (There is a system of administrative monitors, but restricted to administrators looking at the Manage Jenkins page.) It doesn't blink on the main Jenkins job list page. Further, if you restart Jenkins, the ball for paused jobs stops blinking If true, both smell like bugs. The ball for a job should match that of its latest build, which should be animated if the build is still in progress. I am pretty sure I have seen this all working in the past 24 hours, but there may be specific conditions you hit where this breaks. Anyway if you can reproduce from scratch please file separately to avoid distraction here. (Workflow 1.8+ does intentionally hide the “flyweight” executor from the master section of the executor widget when the build is paused, or indeed doing something in a step like sh but not actively running Groovy code. But this is unrelated to the build history widget and to ball colors.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31118) Workflow jobs that are waiting for input should have a visual cue in build history
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31118 Workflow jobs that are waiting for input should have a visual cue in build history Change By: Jesse Glick Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title Jarek Lipski commented on JENKINS-31108 Re: Git-Publisher should allow to push tags from a shallow clone Thank you for a quick response. Of course I'd be happy to include tests in my pull request. I was looking around the code a bit, and I wonder what types of tests are you using in Git SCM Plugin project. I see that there are unit tests and integration / functional tests. Are there also tests that are run against different versions of real git CLI and egit? What kind of testing strategy would you recommend for this change? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-7010) Redploy Artifacts as a promotion
Title: Message Title Arnaud Héritier edited a comment on JENKINS-7010 Re: Redploy Artifacts as a promotion This all pull request is solving the incompatibility of the publisher when used inside a promotion Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-7010) Redploy Artifacts as a promotion
Title: Message Title Arnaud Héritier commented on JENKINS-7010 Re: Redploy Artifacts as a promotion A snapshot including the fix can be downloaded from : https://jenkins.ci.cloudbees.com/job/plugins/job/maven-plugin/170/org.jenkins-ci.main$maven-plugin/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-30837) Restriction on image names
Title: Message Title Alexander Kammerer edited a comment on JENKINS-30837 Re: Restriction on image names I do not have any problems to tag and push that image when using only the docker CLI . Thus, this error must have anything to do with the way the plugin uses docker. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-31124) Exception on de-check "Prepare an environment for the run"
Title: Message Title Christopher Orr commented on JENKINS-31124 Re: Exception on de-check "Prepare an environment for the run" A quick search reveals that this is likely a duplicate of JENKINS-19852 . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-31124) Exception on de-check "Prepare an environment for the run"
Title: Message Title Christopher Orr commented on JENKINS-31124 Re: Exception on de-check "Prepare an environment for the run" Moved from INFRA project to JENKINS, as this is not an issue with the Jenkins project infrastructure. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-31124) Exception on de-check "Prepare an environment for the run"
Title: Message Title Christopher Orr moved an issue Jenkins / JENKINS-31124 Exception on de-check "Prepare an environment for the run" Change By: Christopher Orr Project: Infrastructure Jenkins Key: INFRA JENKINS - 388 31124 Workflow: classic default workflow JNJira Component/s: envinject-plugin Component/s: ci Component/s: github Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [maven-plugin] (JENKINS-7010) Redploy Artifacts as a promotion
Title: Message Title Arnaud Héritier started work on JENKINS-7010 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-31126) Wrong pipeline results due to bug in DeliveryPipelineView.getItems()
Title: Message Title André Carmo created an issue Jenkins / JENKINS-31126 Wrong pipeline results due to bug in DeliveryPipelineView.getItems() Issue Type: Bug Assignee: André Carmo Components: delivery-pipeline-plugin, nested-view-plugin Created: 23/Oct/15 10:50 AM Environment: Latest versions of delivery-pipeline-plugin and nest-view-plugin. Jenkins 1.626 Priority: Major Reporter: André Carmo This issue can possibly be a duplicate version of JENKINS-30604. How to reproduce in GUI Pre-conditions: Have those plugins installed Have at least 2 jobs; Have at least one job that failed in the latest build (mandatory for this to be reproducible) Have a Nested View configured
[JIRA] [active-choices-plugin] (JENKINS-29969) groovy script can not run on node specified for the job
Title: Message Title Oleksandr Kulychok commented on JENKINS-29969 Re: groovy script can not run on node specified for the job Your scenario is very specific. By default, at parameter configuration phase, you don't know which slave will be used to run your test so you cannot select slave automatically. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-14155) Automatically select/build the latest svn tag (via "List Subversion tags" build params?)
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-14155 Re: Automatically select/build the latest svn tag (via "List Subversion tags" build params?) Pedro Goncalves, Are you working on this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-31137) Dependency to Maven 2.12 is not optional
Title: Message Title Pierre Frayer created an issue Jenkins / JENKINS-31137 Dependency to Maven 2.12 is not optional Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 23/Oct/15 3:22 PM Priority: Minor Reporter: Pierre Frayer Hello, In the plugin wiki page, it is mentioned that we need Jenkins 1.609 and and the docker-commons plugin 1.0 if we want to use the Docker Custom Build Env plugin. Two others dependencies are listed as optional : maven-plugin 2.12 & dockerhub-notification 1.0. I tried to install your plugin on Jenkins 1.609.3 with docker-commons installed and I get the following error at Jenkins startup : Warning: Failed to scout com.cloudbees.jenkins.plugins.docker_build_env.MavenPluginHelper java.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/maven/TcpSocketHostLocator Note that as I didn't explicitly installed the maven-plugin, Jenkins was using the one embedded in 1.609.3, maven-plugin 2.7.1. Then I installed the maven-plugin 2.12 and your plugin was working fine: I didn't get any error at Jenkins startup.
[JIRA] [build-pipeline-plugin] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Wolfgang Lumetsberger commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job +1 Same problem with Jenkins 1.634 and Build Pipeline 1.4.8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-31139) Plugin version is not reported (it was earlier in the console)
Title: Message Title Bue Petersen created an issue Jenkins / JENKINS-31139 Plugin version is not reported (it was earlier in the console) Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 23/Oct/15 4:16 PM Environment: Pretested Integration Plugin 2.3.3-SNAPSHOT (1c4ce) code.praqma.net/ci Jenkins master Priority: Minor Reporter: Bue Petersen Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on GiJeLiSlave (gijeli) in workspace /home/praqma/jenkins-slave/workspace/JOSRA_pages_publish > /usr/lib/git-core/git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > /usr/lib/git-core/git config remote.origin.url g...@github.com:josra/josra.github.io.git # timeout=10 Pruning obsolete local branches Fetching upstream changes from g...@github.com:josra/josra.github.io.git > /usr/lib/git-core/git --version # timeout=10 > /usr/lib/git-core/git -c core.askpass=true fetch --tags --progress g...@github.com:josra/josra.github.io.git +refs/heads/:refs/remotes/origin/ --prune Seen branch in repository origin/adam Seen branch in repository origin/charter Seen branch in repository origin/master Seen branch in repository origin/ready/Andrey9kin-master Seen branch in repository origin/ready/pub Seen 5 remote branches Checking out
[JIRA] [pretested-integration-plugin] (JENKINS-31138) Integration fails if the word "master" is part of the ready branch name
Title: Message Title Bue Petersen created an issue Jenkins / JENKINS-31138 Integration fails if the word "master" is part of the ready branch name Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 23/Oct/15 4:15 PM Environment: Pretested Integration Plugin 2.3.3-SNAPSHOT (1c4ce) code.praqma.net/ci Jenkins master Priority: Minor Reporter: Bue Petersen Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on GiJeLiSlave (gijeli) in workspace /home/praqma/jenkins-slave/workspace/JOSRA_pages_publish > /usr/lib/git-core/git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > /usr/lib/git-core/git config remote.origin.url g...@github.com:josra/josra.github.io.git # timeout=10 Pruning obsolete local branches Fetching upstream changes from g...@github.com:josra/josra.github.io.git > /usr/lib/git-core/git --version # timeout=10 > /usr/lib/git-core/git -c core.askpass=true fetch --tags --progress g...@github.com:josra/josra.github.io.git +refs/heads/:refs/remotes/origin/ --prune Seen branch in repository origin/adam Seen branch in repository origin/charter Seen branch in repository origin/master Seen branch in repository origin/ready/Andrey9kin-master Seen branch in repository origin/ready/pub Seen 5 remote branches
[JIRA] [envinject-plugin] (JENKINS-31124) Exception on de-check "Prepare an environment for the run"
Title: Message Title Christopher Orr edited a comment on JENKINS-31124 Re: Exception on de-check "Prepare an environment for the run" A quick search reveals that this is likely a duplicate of JENKINS-19852. Is this happening with the current latest version of the plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-31126) Wrong pipeline results due to bug in DeliveryPipelineView.getItems()
Title: Message Title
André Carmo updated an issue
Jenkins / JENKINS-31126
Wrong pipeline results due to bug in DeliveryPipelineView.getItems()
Change By:
André Carmo
This issue can possibly be a duplicate version of JENKINS-30604. This is a bug of Delivery Pipeline Plugin, not Nested View Plugin. *How to reproduce in GUI*Pre-conditions:- Have those plugins installed- Have at least 2 jobs;- Have at least one job that failed in the latest build (mandatory for this to be reproducible)- Have a Nested View configured- In that Nested View, add a new view that is a Delivery Pipeline View.- Add only one job to the Delivery Pipeline View, at make sure that job runs with SUCCESS.- Run the Delivery Pipeline and make sure the job passes.- Return to the Nested ViewExpected Result- Since the only job of the Delivery Pipeline passed, that pipeline should be shown as SUCCESS in the Nested View.Actual Result:- The Nested View shows the pipeline as FAILED.*How to reproduce with the Nested View Plugin source code*- Download the source code from GitHub- Debug the code (having both plugins installed in your Jenkins instance)- The method getWorstResultForNormalView(View v) calls v.getItems() which returns *ALL* jobs existing in Jenkins, not only the jobs for that view.This tells me getItems() implementation of DeliveryPipelineView is wrong.*How to reproduce with the Delivery Pipeline Plugin source code*Add the following JUnit test{code}@Testpublic void testGetItemsAndContainsWithProjectsNotInView() throws Exception {FreeStyleProject build = jenkins.createFreeStyleProject("build");jenkins.createFreeStyleProject("sonar");jenkins.createFreeStyleProject("packaging");jenkins.getInstance().rebuildDependencyGraph();List specs = new ArrayList();specs.add(new DeliveryPipelineView.ComponentSpec("Comp", "build", NONE));DeliveryPipelineView view = new DeliveryPipelineView("name");view.setComponentSpecs(specs);jenkins.getInstance().addView(view);assertTrue(view.contains(build));Collection items = view.getItems();assertEquals(1, items.size());}{code}This test fails on the last line with java.lang.AssertionError: expected:<1> but was:<3>.As you can see, our Jenkins instance has 3 projects, but there is no connection (downstream trigger) between the "build" project and the others. The DeliveryPipelineView starts with the "build" project, so the view should only have 1 item, not 3.
Add Comment
[JIRA] [git-plugin] (JENKINS-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title Mark Waite commented on JENKINS-31108 Re: Git-Publisher should allow to push tags from a shallow clone The git plugin and the git client plugin tests are executed regularly in multi-configuration jobs which run on Debian 6, Debian 7, Debian 8, CentOS 6, CentOS 7, Ubuntu 14.04, Windows 7, Windows Home Server 2011, and Windows 10. Git versions in those environments include 1.7.1, 1.7.2.3, 1.8.1, 1.9.5, 2.2.1, and 2.6.2. I have a FreeBSD 10.1 system ready to test, but the Jenkins core infrastructure is not yet ready to support FreeBSD as a standard development platform. Some automated tests currently fail on FreeBSD 10.1 due to Jenkins limitations. There are probably a few tests in the test collection which test a single object in isolation, without access to external resources. Most tests in the test suites involve multiple objects and execution of one or more calls to external programs. Your tests should assure that both JGit and CliGit are tested. Usually that means either a parameterized test where the implementation is one of the parameters, or a test base class for one of the implementations which is then overridden by a subclass. There is a method already available in the CliGitAPIImpl which returns true if the command line git version is greater than a certain value. You're welcome to use that method to make the code cleaner. Different versions of egit are not tested, since egit is not supported, at least not as an integration to it. The JGit version included in the plugin is tested regularly on different Java versions (Java 7 and Java 8) and different platforms. You can find the JGit version in the pom file. The plugin remains on JGit 3.7.x currently. It cannot use JGit 4.x yet, because JGit 4.x requires JDK 7 and the plugin still supports execution on Java 6. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] [ruby-runtime-plugin] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title
Joan Fisbein edited a comment on JENKINS-31019
Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Same probem, gitlahook gitlabhook stopped working after upgrading from 1.631 to 1.634My environment:OS: Debian WheezyJava: 1.7.0_80Jenkins 1.634Looking at the jenkins log I see the ruby-runtime error:{code}SEVERE: Failed Loading plugin ruby-runtimejava.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441) at hudson.PluginManager$2$1$1.run(PluginManager.java:384) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:915) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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:745)Caused by: java.lang.ClassCircularityError: org/jruby/RubyClass at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:278) at org.jenkinsci.bytecode.ClassWriter.loadClass(ClassWriter.java:97) at org.jenkinsci.bytecode.ClassWriter.getCommonSuperClass(ClassWriter.java:64) at org.kohsuke.asm5.ClassWriter.getMergedType(ClassWriter.java:1654) at org.kohsuke.asm5.Frame.merge(Frame.java:1426) at org.kohsuke.asm5.Frame.merge(Frame.java:1374) at org.kohsuke.asm5.MethodWriter.visitMaxs(MethodWriter.java:1475) at org.kohsuke.asm5.tree.MethodNode.accept(MethodNode.java:833) at org.kohsuke.asm5.commons.JSRInlinerAdapter.visitEnd(JSRInlinerAdapter.java:187) at org.jenkinsci.bytecode.Transformer$1$1.visitEnd(Transformer.java:107) at org.kohsuke.asm5.MethodVisitor.visitEnd(MethodVisitor.java:877) at org.kohsuke.asm5.ClassReader.readMethod(ClassReader.java:1021) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:693) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:506) at org.jenkinsci.bytecode.Transformer.transform(Transformer.java:113) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:800) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1310) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1366) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at org.jenkinsci.jruby.RubyClassConverter.(RubyClassConverter.java:12) at org.jenkinsci.jruby.JRubyXStream.register(JRubyXStream.java:25) at ruby.RubyRuntimePlugin.initRubyXStreams(RubyRuntimePlugin.java:44) at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:28) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:449) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:438) ... 9 more{code}
Add Comment
[JIRA] [ruby-runtime-plugin] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title Joan Fisbein commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Same probem, gitlahook stopped working after upgrading from 1.631 to 1.634 My environment: OS: Debian Wheezy Java: 1.7.0_80 Jenkins 1.634 Looking at the jenkins log I see the ruby-runtime error: SEVERE: Failed Loading plugin ruby-runtime java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441) at hudson.PluginManager$2$1$1.run(PluginManager.java:384) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:915) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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:745) Caused by: java.lang.ClassCircularityError: org/jruby/RubyClass at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:278) at org.jenkinsci.bytecode.ClassWriter.loadClass(ClassWriter.java:97) at org.jenkinsci.bytecode.ClassWriter.getCommonSuperClass(ClassWriter.java:64) at org.kohsuke.asm5.ClassWriter.getMergedType(ClassWriter.java:1654) at org.kohsuke.asm5.Frame.merge(Frame.java:1426) at org.kohsuke.asm5.Frame.merge(Frame.java:1374) at org.kohsuke.asm5.MethodWriter.visitMaxs(MethodWriter.java:1475) at org.kohsuke.asm5.tree.MethodNode.accept(MethodNode.java:833) at org.kohsuke.asm5.commons.JSRInlinerAdapter.visitEnd(JSRInlinerAdapter.java:187) at org.jenkinsci.bytecode.Transformer$1$1.visitEnd(Transformer.java:107) at org.kohsuke.asm5.MethodVisitor.visitEnd(MethodVisitor.java:877) at org.kohsuke.asm5.ClassReader.readMethod(ClassReader.java:1021) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:693) at org.kohsuke.asm5.ClassReader.accept(ClassReader.java:506) at org.jenkinsci.bytecode.Transformer.transform(Transformer.java:113) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:800) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1310) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1366) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at org.jenkinsci.jruby.RubyClassConverter.(RubyClassConverter.java:12) at org.jenkinsci.jruby.JRubyXStream.register(JRubyXStream.java:25) at ruby.RubyRuntimePlugin.initRubyXStreams(RubyRuntimePlugin.java:44) at ruby.RubyRuntimePlugin.start(RubyRuntimePlugin.java:28) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:449) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:438) ... 9 more
[JIRA] [websphere-deployer-plugin] (JENKINS-30250) StackOverflowError in Websphere Deployer
Title: Message Title Greg Peters commented on JENKINS-30250 Re: StackOverflowError in Websphere Deployer Rusty, Please provide more details on your environment in the plugin description. Are you running with plugin under IBM's J9 JRE or Oracle's JRE? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-31130) maven plugin can't handle xml header in pom.xml
Title: Message Title
Anton Lundin updated an issue
Jenkins / JENKINS-31130
maven plugin can't handle xml header in pom.xml
Change By:
Anton Lundin
When a external tool re-wrote our poms, it added a xml header: {{ }} before the tag.This made maven-plugin blow up:{{ monospaced text}} ERROR: Failed to parse POMsjava.io.IOException: remote file operation failed: /XXX at hudson.remoting.Channel@1fabae96:build-03: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at hudson.FilePath.act(FilePath.java:987)at hudson.FilePath.act(FilePath.java:969)at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960)at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)at hudson.model.Run.execute(Run.java:1741)at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:408)Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1364)at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098)at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2691)at hudson.remoting.UserRequest.perform(UserRequest.java:121)at hudson.remoting.UserRequest.perform(UserRequest.java:49)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)at ..remote call to build-03(Native Method)at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413)at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)at hudson.remoting.Channel.call(Channel.java:778)at hudson.FilePath.act(FilePath.java:980)... 8 moreCaused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)at
[JIRA] [subversion-plugin] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Title: Message Title Daniel Beck commented on JENKINS-17616 Re: Performance issue with Subversion plugin - trigger build on SVN commit takes too long Looks like a possible deadlock. Please provide the entire output, not an excerpt. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter-plugin] (JENKINS-31131) Improving visual style.
Title: Message Title Alexey Larsky created an issue Jenkins / JENKINS-31131 Improving visual style. Issue Type: Improvement Assignee: Unassigned Attachments: choise_UI_compare.png Components: extensible-choice-parameter-plugin Created: 23/Oct/15 1:38 PM Priority: Minor Reporter: Alexey Larsky Please update GUI style of extensible-choice plugin. If checkbox is screen-wide and bigger than all another checkboxes based parameters. Add Comment
[JIRA] [subversion-plugin] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Title: Message Title Luis Roberto Perez Rios commented on JENKINS-17616 Re: Performance issue with Subversion plugin - trigger build on SVN commit takes too long Sure, here is all my output http://justpaste.it/oibx Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31133) Allow processing the plugin jar file before generating the hpi file
Title: Message Title stephenconnolly created an issue Jenkins / JENKINS-31133 Allow processing the plugin jar file before generating the hpi file Issue Type: New Feature Assignee: stephenconnolly Components: core Created: 23/Oct/15 1:50 PM Priority: Minor Reporter: stephenconnolly The Maven HPI Plugin currently creates the .jar file for the .hpi when building the .hpi file. Thus there is no option available to process the .jar file (e.g. using the maven-shade-plugin or maven-jarsigner-plugin, etc) The ideal solution would be to add a new goal hpi:jar that would create the .jar file and then have the hpi:hpi goal look for the attached .jar file and only create the .jar if there is no attached artifact created by hpi:jar With the above solution, existing users of the plugin would be unaffected as the .jar file will not be an attached artifact and thus the existing behaviour will be retained. Users that need the more exotic processing can then just obtain it with prepare-package jar followed by whatever processing plugins they require also bound to the process-package phase and listed after the maven-hpi-plugin in their pom.xml
[JIRA] [gerrit-trigger-plugin] (JENKINS-28987) Gerrit-trigger marks a successful build as failed
Title: Message Title Rich Duncan commented on JENKINS-28987 Re: Gerrit-trigger marks a successful build as failed Encountered the same bug - disabling REST API access cause the build to be recorded as a success. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Title: Message Title Luis Roberto Perez Rios commented on JENKINS-17616 Re: Performance issue with Subversion plugin - trigger build on SVN commit takes too long Daniel Beck just to confirm, did you see the output? I mean this http://justpaste.it/oibx, is working? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit-plugin] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Jonas Gunnarsson commented on JENKINS-27906 Re: Fail to read NUnit3 output xml Hi! I'm having the same problem with NUnit 3 beta5. Adding the ;format=nunit2 to the --report parameter, seems to work. Attachments: [^jenkins-nunit3-error.txt] Relates to: https://github.com/nunit/nunit/issues/853 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-31128) Add Matrix Project compatability
Title: Message Title Mads Nielsen created an issue Jenkins / JENKINS-31128 Add Matrix Project compatability Issue Type: Improvement Assignee: Praqma Support Components: pretested-integration-plugin Created: 23/Oct/15 1:11 PM Priority: Minor Reporter: Mads Nielsen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the
[JIRA] [core] (JENKINS-31089) Signature verification failed in update site 'default'
Title: Message Title Keith Albright commented on JENKINS-31089 Re: Signature verification failed in update site 'default' The data I have is this: jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024 jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768 I tried adding MD5 to the exclusion list for tls, restarted but no change. Did same for certpath, again no change. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-31130) maven plugin can't handle xml header in pom.xml
Title: Message Title Anton Lundin created an issue Jenkins / JENKINS-31130 maven plugin can't handle xml header in pom.xml Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 23/Oct/15 1:33 PM Priority: Minor Reporter: Anton Lundin When a external tool re-wrote our poms, it added a xml header: before the tag. This made maven-plugin blow up: monospaced text ERROR: Failed to parse POMs java.io.IOException: remote file operation failed: /XXX at hudson.remoting.Channel@1fabae96:build-03: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2 at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.act(FilePath.java:969) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Caused by: hudson.remoting.ProxyException:
[JIRA] [cloudbees-folder-plugin] (JENKINS-31129) Avoid gratuitous folder recomputation after saves
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-31129 Avoid gratuitous folder recomputation after saves Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 23/Oct/15 1:26 PM Labels: multibranch robustness Priority: Critical Reporter: Jesse Glick Currently scheduleBuild is called from every save, but this is no good since that is called from onDeleted—so a child, once deleted, can get triggered in a zombie mode, leading to bizarre bugs. Probably should limit automatic build scheduling to a UI configSubmit and perhaps some other selected conditions. Add Comment
[JIRA] [websphere-deployer-plugin] (JENKINS-30250) StackOverflowError in Websphere Deployer
Title: Message Title Greg Peters commented on JENKINS-30250 Re: StackOverflowError in Websphere Deployer Yes, please try running Jenkins on OpenJDK to see if that makes a difference. If it does, I'll rename the bug something that's more specific to J9. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ruby-runtime-plugin] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title David Kiser commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass I suspect this problem is from the bct version upgrade that went into 1.6.33 https://issues.jenkins-ci.org/browse/JENKINS-28781 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-issue-updater-plugin] (JENKINS-31134) Role with id: Developer does not exist on Update Relevant Issues
Title: Message Title Max Burdge updated an issue Jenkins / JENKINS-31134 Role with id: Developer does not exist on Update Relevant Issues Change By: Max Burdge Summary: Failure to Role with id: Developer does not exist on Update JIRA issue Relevant Issues Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-31135) Make merge failures more obvious
Title: Message Title Mads Nielsen created an issue Jenkins / JENKINS-31135 Make merge failures more obvious Issue Type: Improvement Assignee: Praqma Support Components: pretested-integration-plugin Created: 23/Oct/15 2:06 PM Priority: Minor Reporter: Mads Nielsen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the
[JIRA] [nunit-plugin] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Jonas Gunnarsson updated an issue Jenkins / JENKINS-27906 Fail to read NUnit3 output xml Change By: Jonas Gunnarsson Attachment: jenkins-nunit3-error.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Title: Message Title Luis Roberto Perez Rios commented on JENKINS-17616 Re: Performance issue with Subversion plugin - trigger build on SVN commit takes too long Daniel Beck I tried with all previous version to 2.5.3 and the problem persists. Here is my threadDump: Handling POST /subversion/* ** *** *** /notifyCommit from myIP : RequestHandlerThread30 "Handling POST /subversion/* ** *** *** ***/notifyCommit from myIP : RequestHandlerThread30" Id=138 Group=main BLOCKED on hudson.scm.SubversionSCM$ModuleLocation@4389df0f owned by "Handling POST /subversion/ ** *** *** /notifyCommit from myIP : RequestHandlerThread22" Id=124 at hudson.scm.SubversionSCM$ModuleLocation.getUUID(SubversionSCM.java:2726) blocked on hudson.scm.SubversionSCM$ModuleLocation@4389df0f at hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl.onNotify(SubversionRepositoryStatus.java:209) at hudson.scm.SubversionRepositoryStatus.doNotifyCommit(SubversionRepositoryStatus.java:137) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [subversion-plugin] (JENKINS-31127) Subversion Notify Commit needs long time to reply
Title: Message Title Luis Roberto Perez Rios commented on JENKINS-31127 Re: Subversion Notify Commit needs long time to reply The threadDump output: Handling POST /subversion/*/notifyCommit from myIP : RequestHandlerThread30 "Handling POST /subversion/***/notifyCommit from myIP : RequestHandlerThread30" Id=138 Group=main BLOCKED on hudson.scm.SubversionSCM$ModuleLocation@4389df0f owned by "Handling POST /subversion/***/notifyCommit from myIP : RequestHandlerThread22" Id=124 at hudson.scm.SubversionSCM$ModuleLocation.getUUID(SubversionSCM.java:2726) blocked on hudson.scm.SubversionSCM$ModuleLocation@4389df0f at hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl.onNotify(SubversionRepositoryStatus.java:209) at hudson.scm.SubversionRepositoryStatus.doNotifyCommit(SubversionRepositoryStatus.java:137) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at
[JIRA] [maven-plugin] (JENKINS-31130) maven plugin can't handle xml header in pom.xml
Title: Message Title
Anton Lundin updated an issue
Jenkins / JENKINS-31130
maven plugin can't handle xml header in pom.xml
Change By:
Anton Lundin
When a external tool re-wrote our poms, it added a xml header:{{}}before the tag.This made maven-plugin blow up:{ { quote} ERROR: Failed to parse POMsjava.io.IOException: remote file operation failed: /XXX at hudson.remoting.Channel@1fabae96:build-03: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at hudson.FilePath.act(FilePath.java:987)at hudson.FilePath.act(FilePath.java:969)at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960)at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)at hudson.model.Run.execute(Run.java:1741)at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:408)Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1364)at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098)at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2691)at hudson.remoting.UserRequest.perform(UserRequest.java:121)at hudson.remoting.UserRequest.perform(UserRequest.java:49)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)at ..remote call to build-03(Native Method)at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413)at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)at hudson.remoting.Channel.call(Channel.java:778)at hudson.FilePath.act(FilePath.java:980)... 8 moreCaused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)at
[JIRA] [maven-plugin] (JENKINS-31130) maven plugin can't handle xml header in pom.xml
Title: Message Title
Anton Lundin updated an issue
Jenkins / JENKINS-31130
maven plugin can't handle xml header in pom.xml
Change By:
Anton Lundin
When a external tool re-wrote our poms, it added a xml header:{{}}before the tag.This made maven-plugin blow up:{{ ERROR: Failed to parse POMsjava.io.IOException: remote file operation failed: /XXX at hudson.remoting.Channel@1fabae96:build-03: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at hudson.FilePath.act(FilePath.java:987)at hudson.FilePath.act(FilePath.java:969)at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960)at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)at hudson.model.Run.execute(Run.java:1741)at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:408)Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1364)at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098)at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2691)at hudson.remoting.UserRequest.perform(UserRequest.java:121)at hudson.remoting.UserRequest.perform(UserRequest.java:49)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)at ..remote call to build-03(Native Method)at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413)at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)at hudson.remoting.Channel.call(Channel.java:778)at hudson.FilePath.act(FilePath.java:980)... 8 moreCaused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)at
[JIRA] [script-scm-plugin] (JENKINS-31132) Provide some documentation - at least an example groovy script
Title: Message Title Florent Fievez created an issue Jenkins / JENKINS-31132 Provide some documentation - at least an example groovy script Issue Type: Bug Assignee: Unassigned Components: script-scm-plugin Created: 23/Oct/15 1:49 PM Priority: Major Reporter: Florent Fievez Please provide some documentation for the plugin, at least an example groovy script Add Comment This message was sent by
[JIRA] [nunit-plugin] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Brian Reeves commented on JENKINS-27906 Re: Fail to read NUnit3 output xml We finally got this to work by putting in quotes. "--result:TestResult.xml;format=nunit2" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-31046) How to stop the “no changes” mail in e-mail notification.
Title: Message Title R. Tyler Croy commented on JENKINS-31046 Re: How to stop the “no changes” mail in e-mail notification. srinivas varanasi the mailing list is all volunteer driven, as is this entire project. There's nothing to do if nobody is answering your question. If you need professional support, please consult this wiki page. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31127) Subversion Notify Commit needs long time to reply
Title: Message Title Luis Roberto Perez Rios created an issue Jenkins / JENKINS-31127 Subversion Notify Commit needs long time to reply Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 23/Oct/15 12:42 PM Environment: Ubuntu Server 14.04 64 bits Jenkins version: 1.633 Subversion Plugin version: 2.5.3 Labels: jenkins subversion plugin Priority: Major Reporter: Luis Roberto Perez Rios In the post-commit hook the request to url to notify subversion commits takes long time to reply (3-5 min), using wget the error showed is: Connecting to myjenkins:8080... connected HTTP request sent, awaiting response... Read error (Connection timed out) in headers. This is reproducible in each try, using the next timeout values: 2, 4, 8, 16, 32, 64, 128, 256, 1024, 2048...
[JIRA] [websphere-deployer-plugin] (JENKINS-30250) StackOverflowError in Websphere Deployer
Title: Message Title Rusty Bentz commented on JENKINS-30250 Re: StackOverflowError in Websphere Deployer Greg, I am running jenkins with IBM J9 JRE under java 1.7u85. Should I try using OpenJDK? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-issue-updater-plugin] (JENKINS-31134) Failure to Update JIRA issue
Title: Message Title
Max Burdge created an issue
Jenkins / JENKINS-31134
Failure to Update JIRA issue
Issue Type:
Bug
Assignee:
Unassigned
Components:
jira-issue-updater-plugin
Created:
23/Oct/15 1:56 PM
Priority:
Minor
Reporter:
Max Burdge
Get this error since upgrade to 2.0.2:
jira rest client add comment error. cause: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors= {commentLevel=Role with id: Developer does not exist.}
, errorMessages=[]}]}
Jenkins version: 1.622 JIRA version: 6.47
Add Comment
[JIRA] [jobcopy-builder-plugin] (JENKINS-31091) Promotions not copied to new job
Title: Message Title Jacob Hacker updated an issue Jenkins / JENKINS-31091 Promotions not copied to new job Change By: Jacob Hacker Environment: Windows 2012 R2 JobCopy 1. Promoted Builds 2. 0 23 Jenkins ver. 1.594 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobcopy-builder-plugin] (JENKINS-31091) Promotions not copied to new job
Title: Message Title Jacob Hacker updated an issue Jenkins / JENKINS-31091 Promotions not copied to new job Change By: Jacob Hacker Environment: Windows 2012 R2 Promoted Builds Job Copy 1. 2. 23 0 Jenkins ver. 1.594 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31136) Sorting promotions in order of appearance
Title: Message Title Jacob Hacker created an issue Jenkins / JENKINS-31136 Sorting promotions in order of appearance Issue Type: Improvement Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 23/Oct/15 2:16 PM Environment: Windows Server 2012 R2 Jenkins ver. 1.594 Promoted Builds 2.23 Priority: Minor Reporter: Jacob Hacker It looks like by default this job sorts alphabetically, it would be nice if promotions would appear in the order they are declared. It would be nice if you could change the order of the promotions as well. In my case I am deploying to multiple servers on deploy Development server Testing server UAT server PreProd server Ideally they would appear in that order, as that is the order they will be deployed in, but instead it shows them alphabetically.
[JIRA] [core] (JENKINS-31055) Make Node implement Saveable
Title: Message Title dogfood commented on JENKINS-31055 Re: Make Node implement Saveable Integrated in jenkins_main_trunk #4337 [FIXED JENKINS-31055] Make Node implement Saveable (Revision e4b1aab4acab93d638624c7705cfe6eea2d01786) JENKINS-31055 Finessing the exception handling (Revision 8645978bfbe272a494d2bc65cf47104255cfb3fb) JENKINS-31055 Replacing @since tag with placeholder to be restored on merge (Revision db37c76327748261c3b01eebd13369a1ca733282) JENKINS-31055 The intent of Node.save() is a no-op when not in Jenkins list of nodes (Revision 8e24f69013e96e8b7f8b86e9b7a9133e2412c638) JENKINS-31055 Note theoretical race condtion (Revision d2276c3c9b16fd46a3912ab8d58c418e67d8ce3e) Result = SUCCESS stephen connolly : e4b1aab4acab93d638624c7705cfe6eea2d01786 Files : core/src/main/java/jenkins/model/Nodes.java core/src/main/java/hudson/model/Node.java changelog.html core/src/main/java/hudson/model/Computer.java core/src/main/java/jenkins/model/Jenkins.java stephen connolly : 8645978bfbe272a494d2bc65cf47104255cfb3fb Files : core/src/main/java/jenkins/model/Nodes.java stephen connolly : db37c76327748261c3b01eebd13369a1ca733282 Files : core/src/main/java/hudson/model/Node.java stephen connolly : 8e24f69013e96e8b7f8b86e9b7a9133e2412c638 Files : core/src/main/java/hudson/model/Node.java stephen connolly : d2276c3c9b16fd46a3912ab8d58c418e67d8ce3e Files :
[JIRA] [github-plugin] (JENKINS-31103) How to troubleshoot maximum number of statuses errors?
Title: Message Title Kirill Merkushev commented on JENKINS-31103 Re: How to troubleshoot maximum number of statuses errors? How many server-configs do you have in your global setup? I see a cycle in a code: for (GitHubRepositoryName name : GitHubRepositoryNameContributor.parseAssociatedNames(build.getProject())) which means that status will be updated with each config. (Originally it was done to try to find creds with repo:status scope). So maybe its a time to change this behaviour Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-30837) Restriction on image names
Title: Message Title Alexander Kammerer commented on JENKINS-30837 Re: Restriction on image names I do not have any problems to tag and push that image when using docker. Thus, this error must have anything to do with the way the plugin uses docker. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-31124) Exception on de-check "Prepare an environment for the run"
Title: Message Title Christopher Orr assigned an issue to Christopher Orr Jenkins / JENKINS-31124 Exception on de-check "Prepare an environment for the run" Change By: Christopher Orr Assignee: Christopher Orr Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-31124) Exception on de-check "Prepare an environment for the run"
Title: Message Title Christopher Orr assigned an issue to Oleg Nenashev Jenkins / JENKINS-31124 Exception on de-check "Prepare an environment for the run" Change By: Christopher Orr Assignee: Christopher Orr Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unique-id] (JENKINS-30424) Run.save called inside Run.onLoad by migrator
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30424 Re: Run.save called inside Run.onLoad by migrator Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/uniqueid/impl/IdStoreMigratorV1ToV2.java src/test/java/org/jenkinsci/plugins/uniqueid/impl/IdStoreMigratorV1ToV2Test.java http://jenkins-ci.org/commit/unique-id-plugin/a4073a5d07c414740d20a29c525460b8725a6ccb Log: Merge pull request #9 from amuniz/JENKINS-30424-fix-tests JENKINS-30424 Fix tests failures Compare: https://github.com/jenkinsci/unique-id-plugin/compare/7d4a403b73fd...a4073a5d07c4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unique-id] (JENKINS-30424) Run.save called inside Run.onLoad by migrator
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30424 Re: Run.save called inside Run.onLoad by migrator Code changed in jenkins User: Antonio Muñiz Path: src/main/java/org/jenkinsci/plugins/uniqueid/impl/IdStoreMigratorV1ToV2.java src/test/java/org/jenkinsci/plugins/uniqueid/impl/IdStoreMigratorV1ToV2Test.java http://jenkins-ci.org/commit/unique-id-plugin/ee3b0b45f0b93a271fac2a3189a4635662cd6520 Log: Fix tests failures (under some timing conditions) after JENKINS-30424 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31055) Make Node implement Saveable
Title: Message Title dogfood commented on JENKINS-31055 Re: Make Node implement Saveable Integrated in jenkins_main_trunk #4338 JENKINS-31055 Update @since tag (Revision 86f8574ff5bbe82fc4931c29dbd55319e96a8e06) Result = SUCCESS stephen connolly : 86f8574ff5bbe82fc4931c29dbd55319e96a8e06 Files : core/src/main/java/hudson/model/Node.java Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Chen Cohen commented on JENKINS-30906 Re: MultiJobBuild.SubBuild does not contain full job name (if using folders) Hi Vasili and thanks for your detailed explanation. Since MultiJobBuild is sub-type of AbstractBuild you can use the following: MultiJobBuild mjb; mjb.getProject().getFullName(); When debugging the example in screenshot-1.png the above code returns: folder1/job1 Please let me know if it worked for you. Thanks, Chen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-30906) MultiJobBuild.SubBuild does not contain full job name (if using folders)
Title: Message Title Vasili Galka commented on JENKINS-30906 Re: MultiJobBuild.SubBuild does not contain full job name (if using folders) Hi Chen Cohen, But my question was, how do I get the mjb corresponding to the subBuild? Best, Vasili Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30873) Jenkins' Git plugin reparses all previous build.xml on restart
Title: Message Title Mark Waite commented on JENKINS-30873 Re: Jenkins' Git plugin reparses all previous build.xml on restart I believe this is another case of a BuildData related problem in the plugin as described in JENKINS-19022. It is a hard problem to solve without risking major compatibility breaks in the plugin. Refer to pull request 313 for some of the experiments that have been attempted and the challenges which remain. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-merge-request-jenkins] (JENKINS-29698) NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin
Title: Message Title Ludovic Vercruysse commented on JENKINS-29698 Re: NullPointerException and threads blocked in the JVM with the Gitlab Merge Requests Builder plugin Hi Timothy Olshansky, Could you please provide an update ? Which solution could you propose ? Best regards Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [amazon-ecs-plugin] (JENKINS-31125) Add support of different AWS regions
Title: Message Title aleksey savitskiy commented on JENKINS-31125 Re: Add support of different AWS regions submitted pull request https://github.com/jenkinsci/amazon-ecs-plugin/pull/5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-31126) Wrong pipeline results due to bug in DeliveryPipelineView.getItems()
Title: Message Title André Carmo assigned an issue to Patrik Boström Jenkins / JENKINS-31126 Wrong pipeline results due to bug in DeliveryPipelineView.getItems() Change By: André Carmo Assignee: André Carmo Patrik Boström Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-31106) No OAuth credentials options
Title: Message Title Kirill Merkushev commented on JENKINS-31106 Re: No OAuth credentials options GitHub Plugin uses already created OAuth token with required scopes. The way of creating this token can be different: personal access token token manually returned by oauth web-flow (without jenkins). With 1st way gh-plugin can help via https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin (step 2.1) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-31106) No OAuth credentials options
Title: Message Title Kirill Merkushev closed an issue as Not A Defect Jenkins / JENKINS-31106 No OAuth credentials options Change By: Kirill Merkushev Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unique-id] (JENKINS-30424) Run.save called inside Run.onLoad by migrator
Title: Message Title Antonio Muñiz resolved as Fixed Released as 2.1.1 Jenkins / JENKINS-30424 Run.save called inside Run.onLoad by migrator Change By: Antonio Muñiz Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [amazon-ecs-plugin] (JENKINS-31125) Add support of different AWS regions
Title: Message Title aleksey savitskiy created an issue Jenkins / JENKINS-31125 Add support of different AWS regions Issue Type: New Feature Assignee: Nicolas De Loof Components: amazon-ecs-plugin Created: 23/Oct/15 10:08 AM Priority: Major Reporter: aleksey savitskiy currently default region is used, but ECS available also on following regions: http://docs.aws.amazon.com/general/latest/gr/rande.html#ecs_region Add Comment This message was
[JIRA] [email-ext-plugin] (JENKINS-31046) How to stop the “no changes” mail in e-mail notification.
Title: Message Title srinivas varanasi commented on JENKINS-31046 Re: How to stop the “no changes” mail in e-mail notification. Thanks for the given the information. Already i have joined the Jenkins users group on 20th October of this month and mentioned this issue but i am not getting any reply from them till now. Kindly please give me the any other way to rectify the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31141) In Ukrainian locale, some text in update center is displayed in Korean
Title: Message Title Roman Franchuk created an issue Jenkins / JENKINS-31141 In Ukrainian locale, some text in update center is displayed in Korean Issue Type: Bug Assignee: Unassigned Attachments: 2015-10-23 20_18_19-Update Center [Jenkins] - Firefox Developer Edition.png Components: core Created: 23/Oct/15 5:37 PM Priority: Major Reporter: Roman Franchuk Reproduction steps Configure browser to request Ukrainian language content; Open Update centre; Observe column titles and some columns' content to be written with Korean characters. Only the last column is in Ukrainian; I can reproduce the issue on very different configurations on different machines (Windows, Fedora 22, CentOS 7), with freshly installed Jenkins.
[JIRA] [core] (JENKINS-31140) Suggestion - add a "lastBuild" link in the builds tree
Title: Message Title Nathan Neulinger created an issue Jenkins / JENKINS-31140 Suggestion - add a "lastBuild" link in the builds tree Issue Type: Improvement Assignee: Unassigned Components: core Created: 23/Oct/15 4:45 PM Priority: Minor Reporter: Nathan Neulinger Went to go look at a bunch of jobs and noticed that there was no 'last build' link, only individual for last successful and last failed. Seems like a trivial addition to add a common 'lastBuild' one as well. Add Comment
[JIRA] [artifactory-plugin] (JENKINS-27724) Artifactory global configuration panel not showing up.
Title: Message Title R. Tyler Croy assigned an issue to Unassigned I'm not sure why I was assigned this, so removing myself, sorry I can't help! Jenkins / JENKINS-27724 Artifactory global configuration panel not showing up. Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title Sandro Cirulli commented on JENKINS-30682 Re: JIRA ticket creation failing with java.lang.NullPointerException Is there anything I can try at my end? Or anything to help debugging it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23243) Add url redirect support for renamed projects
Title: Message Title R. Tyler Croy assigned an issue to Unassigned Jenkins / JENKINS-23243 Add url redirect support for renamed projects Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23349) Views with a name that start with an emoji are not accessible
Title: Message Title R. Tyler Croy assigned an issue to Unassigned Jenkins / JENKINS-23349 Views with a name that start with an emoji are not accessible Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [labeled-test-groups-publisher-plugin] (JENKINS-30711) TAP Parser comes up as default test result format while loading job config UI
Title: Message Title Larry Bordowitz assigned an issue to Larry Bordowitz Jenkins / JENKINS-30711 TAP Parser comes up as default test result format while loading job config UI Change By: Larry Bordowitz Assignee: Larry Bordowitz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Title: Message Title Alan Qian commented on JENKINS-7139 Re: HtmlPublisher should be able to handle wildcard paths to find multiple html files looks like this was this reverted in 1.8? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30684) When saving configuration jenkins got an issue with PR Builder
Title: Message Title bruce xu commented on JENKINS-30684 Re: When saving configuration jenkins got an issue with PR Builder i figured it out. the application setup must have a trigger. select the build commit status trigger. it's okay if the values are emtpy but it must be added. Hope this helps everyone. https://github.com/janinko/ghprb/issues/351 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Rich Hopkins commented on JENKINS-31144 Re: When specifying an alternate working directory I get a path error Changing my path from D:\Workflow\Environments\DevAgile\Global\core to D:/Workflow/Environments/DevAgile/Global/core fixed the issue, however as a way to make the plugin more friendly to Windows users I'd suggest putting a regex in there that looks at the path and replaces \ with /. That'll throw off Windows purists. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Cletus D'Souza resolved as Won't Fix Jenkins / JENKINS-31144 When specifying an alternate working directory I get a path error Change By: Cletus D'Souza Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Cletus D'Souza reopened an issue Jenkins / JENKINS-31144 When specifying an alternate working directory I get a path error Change By: Cletus D'Souza Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-2111) removing a job does not remove the workspace
Title: Message Title Laurent TOURREAU commented on JENKINS-2111 Re: removing a job does not remove the workspace Hi this issue is very annoying when dealing with hundred jobs you manage dynamically. In long term, this causes a lot of space disk issues. I agree this not desirable when having a workspace shared with others jobs. In this case it should be the responsibility of the job author to know if the job deletion (along with its workspace) should impact others jobs. To avoid such case I suggest to add a check box "Don't delete the workspace if this job is deleted" in job configuration and find a way to mark a directory not eraseable. Concerning the slaves I suggest to check once a the node is reconnected, the list of orphan job workspaces and remove them automaticaly. Is it conceivable? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Cletus D'Souza commented on JENKINS-31144 Re: When specifying an alternate working directory I get a path error This is probably a side-effect of implementing JENKINS-29906 . Please use a forward slash when defining the path as backward slash is an escape character for groovy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29542) example for help for "env" global variable is wrong.
Title: Message Title
Rodrigo Russo resolved as Fixed
Issue fixed in https://github.com/jenkinsci/workflow-plugin/pull/221 Now the mail example is shown like that:
mail to: 'dev...@acme.com',
subject: "Job '${env.JOB_NAME}' (${env.BUILD_NUMBER}) is waiting for input",
body: "Please go to ${env.BUILD_URL} and verify the build"
Jenkins / JENKINS-29542
example for help for "env" global variable is wrong.
Change By:
Rodrigo Russo
Status:
In Progress Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Cletus D'Souza commented on JENKINS-31144 Re: When specifying an alternate working directory I get a path error I thought about that, but that won't quite work as you could legitimately have a \ in there for an escape to groovy. Can't please them all I will update the documentation/tool-tip for that field, so windows users don't get thrown off Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Rich Hopkins commented on JENKINS-31144 Re: When specifying an alternate working directory I get a path error Another work around I found is to change my path to D:\\Workflow\\Environments\\DevAgile\\Globalcore. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Cletus D'Souza updated an issue Jenkins / JENKINS-31144 When specifying an alternate working directory I get a path error Change By: Cletus D'Souza Comment: :D Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Cletus D'Souza commented on JENKINS-31144 Re: When specifying an alternate working directory I get a path error Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31144 When specifying an alternate working directory I get a path error Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31144 Re: When specifying an alternate working directory I get a path error Code changed in jenkins User: Cletus D'Souza Path: src/main/resources/hudson/scm/IntegritySCM/help-alternateWorkspace.html http://jenkins-ci.org/commit/integrity-plugin/57aea8b0fd4d5db3682f21454f8f7f8a6dd4d3a0 Log: In response to [FIXED JENKINS-31144] cannot fix in code at this time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Rich Hopkins created an issue Jenkins / JENKINS-31144 When specifying an alternate working directory I get a path error Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 23/Oct/15 7:56 PM Environment: Jenkins Version: 1.634 integrity-plugin: 1.35 Windows Server 2012 R2 java.runtime.version: 1.8.0_60-b27 Master and Slave servers are setup with same OS and JDK. Slave node is installed as a service with a service account running it and Integrity configured in the service account profile. I'm running Jenkins on port 80, without IIS. Priority: Critical Reporter: Rich Hopkins Since upgrading to version 1.35 I'm getting this anywhere I specify an alternate workspace for the plugin. The ^ in the error message is pointing to the first \ after D:\. FATAL: startup failed: Script1.groovy: 1: unexpected char: '\' @ line 1, column 11. return "D:\Workflow\Environments\DevAgile\Global\core" ^ 1 error org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: Script1.groovy: 1: unexpected char: '\' @ line 1, column 11. return "D:\Workflow\Environments\DevAgile\Global\core" ^ 1 error at
[JIRA] [integrity-plugin] (JENKINS-31144) When specifying an alternate working directory I get a path error
Title: Message Title Rich Hopkins updated an issue Jenkins / JENKINS-31144 When specifying an alternate working directory I get a path error Change By: Rich Hopkins Comment: Another work around I found is to change my path to D:\\Workflow\\Environments\\DevAgile\\Global\\core. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
