[JIRA] (JENKINS-36338) Multibranch pipelines not showing up (correctly)
Title: Message Title Michael Neale commented on JENKINS-36338 Re: Multibranch pipelines not showing up (correctly) I added a small fix to use _class here: https://github.com/jenkinsci/blueocean-plugin/pull/307 as suggested by cliff, this seems good. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36338) Multibranch pipelines not showing up (correctly)
Title: Message Title Michael Neale commented on JENKINS-36338 Re: Multibranch pipelines not showing up (correctly) frankly its terrifying I am in there writing jsx but I have learned to type gulp lint fix often Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36339) upload recursive folders
Title: Message Title Mor Shaked updated an issue Jenkins / JENKINS-36339 upload recursive folders Change By: Mor Shaked Hello. Is there a way to upload recursive folders - so the folder structure in s3 will be the same i sent? as far as i know, for each files i am uploading, i need to specify exact target, But if i have multiple folders inside one folder - when it upload to s3 i am getting all files "flatted on the target" and not in same folder structure ive intended it to be . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36339) upload recursive folders
Title: Message Title Mor Shaked updated an issue Jenkins / JENKINS-36339 upload recursive folders Change By: Mor Shaked Summary: HTTP Headers s3 and upload recursive folders Hello. 2 questions/requests1. Is there a way to upload file to s3 with using this header ContentType: Application/json and not Content-Type: application/octet-stream.2.is there a way to upload recursive folders - so the folder structure in s3 will be the same i sent ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36338) Multibranch pipelines not showing up (correctly)
Title: Message Title Michael Neale commented on JENKINS-36338 Re: Multibranch pipelines not showing up (correctly) Cliff Meyers yeah that was my guess, but we didn't know where to look (as quite a few changes). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36338) Multibranch pipelines not showing up (correctly)
Title: Message Title Cliff Meyers commented on JENKINS-36338 Re: Multibranch pipelines not showing up (correctly) I'll look into it first thing in the morning. Maybe they're being filtered out by the "hide Folder" logic. Can improve that to work off class name now anyhow... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36339) HTTP Headers s3 and upload recursive folders
Title: Message Title Mor Shaked created an issue Jenkins / JENKINS-36339 HTTP Headers s3 and upload recursive folders Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2016/Jun/30 4:15 AM Priority: Minor Reporter: Mor Shaked Hello. 2 questions/requests 1.Is there a way to upload file to s3 with using this header ContentType: Application/json and not Content-Type: application/octet-stream. 2.is there a way to upload recursive folders - so the folder structure in s3 will be the same i sent ? Add Comment
[JIRA] (JENKINS-36132) Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.
Title: Message Title Ulli Hafner edited a comment on JENKINS-36132 Re: Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed. It would help if you can answer the questions that are asked in the trade trace above... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36132) Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.
Title: Message Title Ulli Hafner commented on JENKINS-36132 Re: Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed. It would help if you can answer the questions that are asked in the trade above... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36336) Developer wants to see what tests were fixed for a run
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36336 Developer wants to see what tests were fixed for a run Change By: James Dumay Sprint: 1.0-m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Ulli Hafner commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade Either analysis-core requires a downgrade of joda or dashboard-view an upgrade... I'll check which makes more sense as soon as my laptop is back from repair... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36338) Multibranch pipelines not showing up (correctly)
Title: Message Title Michael Neale commented on JENKINS-36338 Re: Multibranch pipelines not showing up (correctly) https://github.com/jenkinsci/blueocean-plugin/pull/307 currently has a WIP for fixing some of this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Ulli Hafner commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade A workaround is already in the description. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36338) Multibranch pipelines not showing up (correctly)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36338 Multibranch pipelines not showing up (correctly) Change By: Michael Neale Sprint: 1.0-m10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title Ulli Hafner commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config Which version of analysis-core is installed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36338) Multibranch pipelines not showing up (correctly)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-36338 Multibranch pipelines not showing up (correctly) Issue Type: Bug Assignee: James Dumay Components: blueocean-plugin Created: 2016/Jun/30 4:02 AM Priority: Blocker Reporter: Michael Neale Currently multibranch projects are not showing up correctly, or at all. Since the api has moved to using /search, it will either show each branch as a discrete pipeline (incorrectly) or when it excludes the flattening of multibranch (which the api correctly does when told to) it doesn't show up at all. The last known good commit of master (for reference) is https://github.com/jenkinsci/blueocean-plugin/commit/f78c07e3bde8228165aa98416086895b61b713e2 https://github.com/jenkinsci/blueocean-plugin/pull/307 partially fixes it, but multibranch no longer shows up, despite it being returned in what "appears" to be correct json. Needs investigation Add Comment
[JIRA] (JENKINS-36338) Multibranch pipelines not showing up (correctly)
Title: Message Title Michael Neale assigned an issue to Cliff Meyers Jenkins / JENKINS-36338 Multibranch pipelines not showing up (correctly) Change By: Michael Neale Assignee: James Dumay Cliff Meyers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36337) Git plugin can't auto get the changes from gitlab when use http://IP/xx.git
Title: Message Title ying zhang created an issue Jenkins / JENKINS-36337 Git plugin can't auto get the changes from gitlab when use http://IP/xx.git Issue Type: Task Assignee: ying zhang Attachments: 1.jpg, 2.jpg Components: git-changelog-plugin, git-client-plugin, git-plugin, gitlab-oauth-plugin, gitlab-plugin Created: 2016/Jun/30 1:46 AM Environment: jenkins 2.0,git plugin 2.4.4, gitlab 8.8.7. Labels: plugin configuration scm build Priority: Major Reporter: ying zhang Jenkins can't use the Git plugin auto get the changes from gitlab( http://IP/xx.git) then trigger new build. Now we need trigger the job by hand. Does the git plugin didn't support the gitlab use http:// ? Or some other configuration can slove this problem.
[JIRA] (JENKINS-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Francis Upton commented on JENKINS-36197 Re: java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Alvaro Lobato I have been having problems with this. When I raised the version of the bc plugin to 1.648.3, the Junit tests fail because they are getting the wrong version of the bc libraries (version 1.47). I tracked this down and it appears the jenkins-for-test is an expansion of the core jenkins.war file that is done when the tests are run. This is a result of the Jenkins core version being something like 1.624. The parent for this plugin (in the pom) is com.jenkins-ci.plugins/plugin - the highest 1.x version of this is 1.642.4. But I tried this and the corresponding jenkins.war still has the old bc libraries. I can't find a mechanism to inject the desired version of the required plugins (like new bc libs plugin) into the jenkins-for-test so the tests will pass. Is there such a mechanism? Is there a way to depend on Jenkins core 1.648? (should I have a separate dependency on Jenkins core in addition to the parent specification of the .plugins/plugin artifact? Should I depend on Jenkins 2.x? (this seems scary to me). Currently the ec2 build in master is broken because of this, and I'm going to leave it that way for the moment in hope that I can get some prompt help on this by someone who understand this. Thanks, Francis Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Francis Upton reopened an issue Jenkins / JENKINS-36197 java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Change By: Francis Upton Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36273) Add "organization" filter to /search API
Title: Message Title Vivek Pandey commented on JENKINS-36273 Re: Add "organization" filter to /search API PR https://github.com/jenkinsci/blueocean-plugin/pull/307 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Change in pipeline CPS plugin is the umbrella PR. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36334) Configure Cisco Spark room at folder level instead of system level
Title: Message Title jian fu commented on JENKINS-36334 Re: Configure Cisco Spark room at folder level instead of system level 3ks for your feedback. And what's the folder level? I will contact with your cec cisco mail. My contact mail is ji...@cisco.com Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36278) Multi-branch pipelines stored in folders return JSON with invalid Link hrefs
Title: Message Title Vivek Pandey resolved as Fixed Jenkins / JENKINS-36278 Multi-branch pipelines stored in folders return JSON with invalid Link hrefs Change By: Vivek Pandey Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35799) Developer wants to use Bitbucket as a branch source
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35799 Developer wants to use Bitbucket as a branch source Change By: James Dumay Sprint: 1.0-m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class I need UninstantiatedDescribable to also support a single-object non-map parameter. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Brantone edited a comment on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 And this is with 1.5.1 ? A fix was issued with 1.5.2.What other SCM plugins installed as I'm currently unable to reproduce these others errors . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Brantone commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 And this is with 1.5.1 ? A fix was issued with 1.5.2. What other SCM plugins installed as I'm currently unable to reproduce these others. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36336) Developer wants to see what tests were fixed for a run
Title: Message Title James Dumay commented on JENKINS-36336 Re: Developer wants to see what tests were fixed for a run For R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36336) Developer wants to see what tests were fixed for a run
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36336 Developer wants to see what tests were fixed for a run Issue Type: Story Assignee: James Dumay Attachments: Failing result - Tests with failing since.png Components: blueocean-plugin Created: 2016/Jun/30 12:11 AM Labels: x-team Priority: Minor Reporter: James Dumay If there are fixed tests then the developer can see those too. Add Comment
[JIRA] (JENKINS-36336) Developer wants to see what tests were fixed for a run
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36336 Developer wants to see what tests were fixed for a run Change By: James Dumay Labels: x-team Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-675) add toggle button to change build status when plugin fails
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-675 add toggle button to change build status when plugin fails Change By: Alex Earl Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title
Paul Eipper edited a comment on JENKINS-31712
Re: Use SCM from another project is removed after upgrading to 1.5.1
This is in the system log:{code :java }Failed to instantiate Key[type=hudson.plugins.templateproject.ProxySCM$DescriptorImpl, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Guice provision errors:1) Error injecting constructor, java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at hudson.plugins.templateproject.ProxySCM$DescriptorImpl.(ProxySCM.java:113)1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:389) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1233) at hudson.plugins.git.GitSCM.onLoaded(GitSCM.java:1714) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:926) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.privateGetMethodRecursive(Class.java:3048) at java.lang.Class.getMethod0(Class.java:3018) at java.lang.Class.getMethod(Class.java:1784) at hudson.model.Descriptor.(Descriptor.java:285) at hudson.scm.SCMDescriptor.(SCMDescriptor.java:71) at hudson.plugins.templateproject.ProxySCM$DescriptorImpl.(ProxySCM.java:113) at hudson.plugins.templateproject.ProxySCM$DescriptorImpl$$FastClassByGuice$$4e632614.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269) at
[JIRA] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Paul Eipper commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 This is in the system log: Failed to instantiate Key[type=hudson.plugins.templateproject.ProxySCM$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at hudson.plugins.templateproject.ProxySCM$DescriptorImpl.(ProxySCM.java:113) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:389) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1233) at hudson.plugins.git.GitSCM.onLoaded(GitSCM.java:1714) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:926) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.privateGetMethodRecursive(Class.java:3048) at java.lang.Class.getMethod0(Class.java:3018) at java.lang.Class.getMethod(Class.java:1784) at hudson.model.Descriptor.(Descriptor.java:285) at hudson.scm.SCMDescriptor.(SCMDescriptor.java:71) at hudson.plugins.templateproject.ProxySCM$DescriptorImpl.(ProxySCM.java:113) at hudson.plugins.templateproject.ProxySCM$DescriptorImpl$$FastClassByGuice$$4e632614.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Paul Eipper updated an issue Jenkins / JENKINS-36281 Dashboard trend graphs not displayed following plugin upgrade Change By: Paul Eipper Attachment: jenkins-dashboard-view.log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title
Kohsuke Kawaguchi commented on JENKINS-29922
Re: Promote delegates of metasteps to top-level functions, deprecate $class
I spent some time with Jesse Glick today to figure out the direction of this change. User Experience The proposed syntax for this, assuming @Symbol annotations on relevant classes, is as follows:
// symbols on MercurialSCM, Kallithea
// as for steps, if only mandatory params, can elide param name
// @DataBoundConstructor public Kallithea(String url)
hg source: 'https://whatever/',
clean: true,
browser: kallithea('https://whatever/')
kallithea is implemented by DSL.invokeMethod and returns a map-like object that just captures the arguments. We are not going to actually instantiate KallitheaBrowser at this point since disambiguating the symbol might require a context. hg is similarly implemented by DSL.invokeMethod, but Jenkins knows that there's a meta step that can handle SCM, so in this case it instantiates the whole tree (including nested kallithea) into SCM instance and use the meta step to execute it. Design
Symbol plugin
A class that represents a nested describable object (which was formally a map), say, UninstantiatedDescribable
Workflow-Step-API
A new boolean method on StepDescriptor to recognize meta steps
Workflow-CPS-plugin
DSL.invokeMethod recognizes symbol and instantiate UninstantiatedDescribable
DSL.invokeMethod recognizes meta step and execute it on the spot
Snippetizer to recognize UninstantiatedDescribable during formatting
Add Comment
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Change for the structs-plugin is ready Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title Paul Eipper commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade Is there a step by step workaround to fix this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36209) Queued items should show on the activity tab
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36209 Queued items should show on the activity tab Change By: Michael Neale Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36209) Queued items should show on the activity tab
Title: Message Title Michael Neale commented on JENKINS-36209 Re: Queued items should show on the activity tab I am prepared to lower this, not a blocker for alpha IMO Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31362) Google authentication with Swarm plugin
Title: Message Title Leandro Kersting de Freitas commented on JENKINS-31362 Re: Google authentication with Swarm plugin And with 'Github OAuth Plugin' not work too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36227) Logstash plugin Global configure error
Title: Message Title Chris Broll commented on JENKINS-36227 Re: Logstash plugin Global configure error I thought I would try removing 1.2.0, then deleting the $JENKINS_HOME/plugins/logstash folder and also removing manually jenkins.plugins.logstash.LogstashInstallation.xml. I then uploaded 1.1.0 went to configure it in the UI and found that it had auto populated a user name/password and -1 in the port field. They were easy to remove but the "not found" error returns in this version also. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title Jesse Glick started work on JENKINS-34517 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36335) support regex for issue id pattern
Title: Message Title Steven Loomis created an issue Jenkins / JENKINS-36335 support regex for issue id pattern Issue Type: New Feature Assignee: Unassigned Components: trac-publisher-plugin Created: 2016/Jun/29 10:03 PM Priority: Minor Reporter: Steven Loomis Just as in JENKINS-3665 - would like to be able to modify the regex used for the publisher. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick started work on JENKINS-29922 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-29922 Promote delegates of metasteps to top-level functions, deprecate $class Change By: Jesse Glick Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title Vivek Pandey commented on JENKINS-36208 Re: Queued items are not showing up PR https://github.com/jenkinsci/blueocean-plugin/pull/305 submitted. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36321) Install transitive dependencies occasionally failing
Title: Message Title
Manuel Recena Soto updated an issue
Jenkins / JENKINS-36321
Install transitive dependencies occasionally failing
Change By:
Manuel Recena Soto
{{ @WithPlugin }} annotation should install transitive dependencies properly always.Sometimes the transitive dependencies are not installed properly and we end up getting a {{ NullPointerException }} .Example: {code:java}java.lang.NullPointerException: null at org.jenkinsci.test.acceptance.update_center.UpdateCenterMetadata.transitiveDependenciesOf(UpdateCenterMetadata.java:81) at org.jenkinsci.test.acceptance.update_center.UpdateCenterMetadata.transitiveDependenciesOf(UpdateCenterMetadata.java:83) at org.jenkinsci.test.acceptance.update_center.UpdateCenterMetadata.transitiveDependenciesOf(UpdateCenterMetadata.java:83) at org.jenkinsci.test.acceptance.update_center.UpdateCenterMetadata.transitiveDependenciesOf(UpdateCenterMetadata.java:75) at org.jenkinsci.test.acceptance.po.PluginManager.installPlugins(PluginManager.java:157) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.doInstall(WithPlugins.java:141) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.installPlugins(WithPlugins.java:121) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.evaluate(WithPlugins.java:93) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1$2$1.evaluate(JenkinsAcceptanceTestRule.java:172)...{code}This is not easily reproducible, just happened some times.
Add Comment
[JIRA] (JENKINS-35314) p4 Plugin does not trigger Pipeline builds
Title: Message Title
Kyle Mott commented on JENKINS-35314
Re: p4 Plugin does not trigger Pipeline builds
Paul Allen, here's what my Jenkins log looks like just after the trigger is received by Jenkins:
Jun 29, 2016 11:02:57 AM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChange
Received trigger event: {change:905738,p4port: "p4.example.org:1666"}
Jun 29, 2016 11:02:57 AM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobs
P4: probing: project1-tip
Jun 29, 2016 11:02:57 AM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger poke
P4: poking: project1-tip
Jun 29, 2016 11:03:06 AM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobs
P4: probing: project2-tip
Jun 29, 2016 11:03:06 AM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger poke
P4: poking: project2-tip
Jun 29, 2016 11:03:10 AM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobs
P4: probing: project3-tip
Jun 29, 2016 11:03:10 AM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger poke
P4: poking: project3-tip
Jun 29, 2016 11:03:25 AM INFO org.jenkinsci.plugins.p4.PerforceScm guessBrowser
Unable to guess repository browser.
And here's what the full consoleText looks like from a corresponding failed build (almost as if the Jenkinsfile couldn't be found in Perforce, but I know it's there):
Started by an SCM change
(p4):cmd:... p4 client -o jenkins-project1-tip
p4 client -o jenkins-project1-tip
(p4):stop:6
(p4):cmd:... p4 info
p4 info
(p4):stop:7
P4 Task: establishing connection.
... server: p4.example.org:1666
... node: jenkins
(p4):cmd:... p4 client -o jenkins-project1-tip
p4 client -o jenkins-project1-tip
(p4):stop:8
(p4):cmd:... p4 client -i
p4 client -i
Client jenkins-project1-tip not changed.
(p4):stop:9
... client: jenkins-project1-tip
(p4):cmd:... p4 client -o jenkins-project1-tip.clonescript
p4 client -o jenkins-project1-tip.clonescript
(p4):stop:6
(p4):cmd:... p4 info
p4 info
(p4):stop:7
P4 Task: establishing connection.
... server: p4.example.org:1666
... node: jenkins
(p4):cmd:... p4 client -o jenkins-project1-tip
p4 client -o jenkins-project1-tip
(p4):stop:8
(p4):cmd:... p4 client -o jenkins-project1-tip.clonescript
p4 client -o jenkins-project1-tip.clonescript
(p4):stop:9
(p4):cmd:... p4 client -i
p4 client -i
Client jenkins-project1-tip.clonescript not changed.
(p4):stop:10
(p4):cmd:... p4 client -f -s -t jenkins-project1-tip jenkins-project1___
p4 client -f -s -t jenkins-project1-tip jenkins-project1-tip.clonescript
Client jenkins-project1-tip.clonescript not changed.
(p4):stop:11
(p4):cmd:... p4 client -o jenkins-project1-tip.clonescript
p4 client -o jenkins-project1-tip.clonescript
(p4):stop:12
(p4):cmd:... p4 client -i
p4 client -i
Client jenkins-project1-tip.clonescript not changed.
(p4):stop:13
... client: jenkins-project1-tip.clonescript
(p4):cmd:... p4 client -o jenkins-project1-tip.clonescript
p4 client -o jenkins-project1-tip.clonescript
(p4):stop:6
(p4):cmd:... p4 info
p4 info
(p4):stop:7
(p4):cmd:... p4 counter change
p4 counter change
(p4):stop:8
(p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-project1-tip.clonescript/...
p4 changes -m1 -ssubmitted //jenkins-project1-tip.clonescript/...
Change 905738 on 2016/06/29 by user@clientspec 'Change
[JIRA] (JENKINS-33757) Parameterized Trigger plugin not finding properties files when using Parameter factories
Title: Message Title Nishant Rangrej edited a comment on JENKINS-33757 Re: Parameterized Trigger plugin not finding properties files when using Parameter factories I am trying to do the exact thing and I am having the same issues. Can anyone update on this? My jenkins version is 1.580.3. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33757) Parameterized Trigger plugin not finding properties files when using Parameter factories
Title: Message Title Nishant Rangrej commented on JENKINS-33757 Re: Parameterized Trigger plugin not finding properties files when using Parameter factories I am trying to the exact thing and I am having the same issues. Can anyone update on this? My jenkins version is 1.580.3. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title David Johansen commented on JENKINS-27514 Re: Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM So, we were hitting this issue a while back, threads stacking until we had to restart. I tracked it down to some automation that I had written, using http://javadoc.jenkins-ci.org/hudson/model/Computer.html#connect(boolean). I was using connect(true) which is supposed to spawn a new thread if the agent is "disconnected", and cancel the current thread that was disconnected. It doesn't cancel it right away though. Anyways, it was spawning them much more frequently than Jenkins was killing those old threads, when a host was not in a state where it could be connected. I changed my call to connect(false) to not force reconnect if the agent was unavailable, and we stopped seeing the crazy thread stacking. Kinda sounds like what you are seeing, but either way figured I'd share what we did. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33589) Build history widget does not refresh status of Pipeline build which finishes after Jenkins restart
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-33589 Build history widget does not refresh status of Pipeline build which finishes after Jenkins restart Change By: Sam Van Oort Assignee: Tom FENNELLY Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33589) Build history widget does not refresh status of Pipeline build which finishes after Jenkins restart
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-33589 Build history widget does not refresh status of Pipeline build which finishes after Jenkins restart Change By: Sam Van Oort Component/s: pipeline-stage-view-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title
Dilip Mahadevappa edited a comment on JENKINS-27514
Re: Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Jenkins ver. 1.625.2SSH Slaves plugin: 1.10Thread Dump attached: [^thread-dump.txt] Support bundle attached: [^support_2016-06-29_13.17.36 (2).zip] We have hit a similiar issue. We had some 5k+ blocked Computer.threadPoolForRemoting threads.{code:java}Computer.threadPoolForRemoting [#175318] - threadId:2655322 (0x28845a) - state:BLOCKEDstackTrace:- waiting to lock <0x6e0864fe> (a hudson.plugins.sshslaves.SSHLauncher)owned by Computer.threadPoolForRemoting [#175203] id=2653481at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1226)at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:603)at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)at java.util.concurrent.FutureTask.run(FutureTask.java:166)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:724)Locked synchronizers: count = 1- java.util.concurrent.ThreadPoolExecutor$Worker@729cb958...{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-27514 Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM Change By: Dilip Mahadevappa Attachment: support_2016-06-29_13.17.36 (2).zip Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36289) BlueOcean can not call ReplayAction#run and have a Queue.Item returned
Title: Message Title Ivan Meredith resolved as Fixed Jenkins / JENKINS-36289 BlueOcean can not call ReplayAction#run and have a Queue.Item returned Change By: Ivan Meredith Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title Dilip M commented on JENKINS-27514 Re: Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM Jenkins ver. 1.625.2 SSH Slaves plugin: 1.10 Thread Dump attached: thread-dump.txt We have hit a similiar issue. We had some 5k+ blocked Computer.threadPoolForRemoting threads. Computer.threadPoolForRemoting [#175318] - threadId:2655322 (0x28845a) - state:BLOCKED stackTrace: - waiting to lock <0x6e0864fe> (a hudson.plugins.sshslaves.SSHLauncher) owned by Computer.threadPoolForRemoting [#175203] id=2653481 at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1226) at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:603) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Locked synchronizers: count = 1 - java.util.concurrent.ThreadPoolExecutor$Worker@729cb958 . . . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title Dilip M updated an issue Jenkins / JENKINS-27514 Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM Change By: Dilip M Attachment: thread-dump.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34690) Analysis collector ATH tests failing
Title: Message Title Andrew Bayer resolved as Fixed Seems to be fixed by the window size change. Jenkins / JENKINS-34690 Analysis collector ATH tests failing Change By: Andrew Bayer Status: Open Resolved Assignee: Oliver Gondža Andrew Bayer Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-36307) "Can not read hook payload" exception whenever a hook is received
Title: Message Title Coltrey Mather commented on JENKINS-36307 Re: "Can not read hook payload" exception whenever a hook is received I also get this error when bitbucket is triggering a web-hook for a created pull request. Push triggers are received and work fine, PRs are not. Bitbucket cloud Jenkins v2.11 bitbucket-branch-source-plugin v1.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13792) Support for conditional post-build actions
Title: Message Title Moshe Zvi commented on JENKINS-13792 Re: Support for conditional post-build actions The Flexible Publish Plugin also intervenes with Artifactory Plugin, which is a problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36334) Configure Cisco Spark room at folder level instead of system level
Title: Message Title Sikai Peng updated an issue Jenkins / JENKINS-36334 Configure Cisco Spark room at folder level instead of system level Change By: Sikai Peng In the latest version (1.0.5) of Cisco Spark Plugin, Spark rooms are configured at system level and accessible to all users, which is not suitable to a multi-user Jenkins instance. This It will be great if this plugin should could be able to tie Spark rooms down to a folder level. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36334) Configure Cisco Spark room at folder level instead of system level
Title: Message Title Sikai Peng created an issue Jenkins / JENKINS-36334 Configure Cisco Spark room at folder level instead of system level Issue Type: New Feature Assignee: jian fu Components: cisco-spark-plugin Created: 2016/Jun/29 7:33 PM Priority: Minor Reporter: Sikai Peng In the latest version (1.0.5) of Cisco Spark Plugin, Spark rooms are configured at system level and accessible to all users, which is not suitable to a multi-user Jenkins instance. This plugin should be able to tie Spark rooms down to a folder level. Add Comment
[JIRA] (JENKINS-36215) Weblogic Deployer plugin 3.3 issue
Title: Message Title Raphael CHAUMIER commented on JENKINS-36215 Re: Weblogic Deployer plugin 3.3 issue Hi Bharath Natarajan The weblogic command uses the classpath attribute defined in weblogic global configuration (where you specify wlfullclient.ar). Did you try to set Did you try to add The classpath value with /path/to/wulfullclient.jar;/path/to/wlthint3client.jar ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36333) Resume build button allows anyone to rebuild failed build
Title: Message Title Roberto Sena created an issue Jenkins / JENKINS-36333 Resume build button allows anyone to rebuild failed build Issue Type: Bug Assignee: Oleg Nenashev Attachments: image-2016-06-29-13-21-36-105.png Components: multijob-plugin, role-strategy-plugin Created: 2016/Jun/29 7:25 PM Environment: Jenkins v1.642 Multijob plugin v1.21 Role-based Authorization Strategy plugin v2.20 Priority: Minor Reporter: Roberto Sena We are using the Role-based Authorization Strategy plugin to limit the developers to what job they can run. The Multijob plugin is being used to throttle our builds with phases as well as group up application builds that reside on the same Weblogic servers. The issue I am seeing is around the 'Resume build' button for the multijob projects. I just noticed today that anyone, regardless of how the Roles are set up or if one is even signed in, can click the button and resume a build. This has the potential to cause unstable environments if someone realizes that and continues to rebuild the failed build to get what they want built. I know I am a little behind on the role strategy plugin but I don't think that's where the issue is coming from. It seems to me that the resume build button doesn't take into account who actually has access to run the build in the first place. We have it set up to where one can browse the build logs of Jenkins without needing to be logged in. I don't really see that as being an issue since we send out the job url's to many groups so the can check on the stauts of the build. And subsequently look at the
[JIRA] (JENKINS-36215) Weblogic Deployer plugin 3.3 issue
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-36215 Weblogic Deployer plugin 3.3 issue Change By: Raphael CHAUMIER Comment: Hi [~arunb]The issue of your latest deployment log is different. It is a NoClassDefFound java.lang.NoClassDefFoundError: com/rsa/jsafe/JSAFE_SecureRandom. Here is a link related to this (https://community.oracle.com/thread/3519739?start=0=0) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36215) Weblogic Deployer plugin 3.3 issue
Title: Message Title Raphael CHAUMIER commented on JENKINS-36215 Re: Weblogic Deployer plugin 3.3 issue Hi Arun Bharathan The issue of your latest deployment log is different. It is a NoClassDefFound java.lang.NoClassDefFoundError: com/rsa/jsafe/JSAFE_SecureRandom. Here is a link related to this (https://community.oracle.com/thread/3519739?start=0=0) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36214) Image.run should use @tmp so .container is not kept around
Title: Message Title Jesse Glick started work on JENKINS-36214 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36332) docker.WithRun allow CMD args
Title: Message Title Domingo K commented on JENKINS-36332 Re: docker.WithRun allow CMD args Jesse Glick - are there steps anywhere to fork/build/install this workflow plugin until this issues is resolved? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36332) docker.WithRun allow CMD args
Title: Message Title Domingo K created an issue Jenkins / JENKINS-36332 docker.WithRun allow CMD args Issue Type: Improvement Assignee: Jesse Glick Components: docker-workflow-plugin Created: 2016/Jun/29 6:55 PM Priority: Minor Reporter: Domingo K As a user of docker.WithRun, I Should Be Able To specify command arguments for the Docker run So That I Can provide arguments to containers that are meant to be run like commands (e.g have custom entrypoints defined). == Acceptance Criteria == Given I run a docker container When I run the Groovy syntax of docker.image(busybox).withRun(args: "-v /tmp:/tmp", command: "ls -la /tmp") Then I expect the underlying docker run command to look like the following "docker run -d -v /tmp:/tmp busybox ls -la /tmp" === Notes Expand arguments to https://github.com/jenkinsci/docker-workflow-plugin/blob/153c70d5e863eb499b49d08d6992f3eff3ca586a/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy#L133 to allow "command" optional argument as well. Add Comment
[JIRA] (JENKINS-36159) Pipeline "tool" w/ Docker inside { ... } still installs to the parent node
Title: Message Title
Jesse Glick resolved as Won't Do
Has been suggested. I do not think we want to do it. If you wish to use some tool in the container, choose an image which contains that tool. If there is none predefined, create a Dockerfile for it and use docker.build.
Jenkins / JENKINS-36159
Pipeline "tool" w/ Docker inside { ... } still installs to the parent node
Change By:
Jesse Glick
Status:
Open Resolved
Resolution:
Won't Do
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-36331) Jenkins 1.651.3 breaks parameter inheritance for inheritance projects
Title: Message Title Gregory Baumgardner updated an issue Jenkins / JENKINS-36331 Jenkins 1.651.3 breaks parameter inheritance for inheritance projects Change By: Gregory Baumgardner Summary: Jenkins 1.651.3 break breaks parameter inheritance for inheritance projects When I upgraded from 1.651.1 to 1.651.3, my inheritance projects failed with an "org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro" Exception. The macro was a StringParameter, which shows up when I click on Run Now. However, that parameter, nor any other parameter , shows up when under the build job Parameters list and I get the Macro expansion error when I try to use that parameter. I fell back to 1.651.1 and all is functional again, i.e. I can expand the parameter and it shows up under the list. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36331) Jenkins 1.651.3 breaks parameter inheritance for inheritance projects
Title: Message Title Gregory Baumgardner updated an issue Jenkins / JENKINS-36331 Jenkins 1.651.3 breaks parameter inheritance for inheritance projects Change By: Gregory Baumgardner When I upgraded from 1.651.1 to 1.651.3, my inheritance projects failed with an "org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro" Exception. The macro was a StringParameter, inherited from a parent project, which shows up as normal when I click on Run Now. However, that parameter, nor any other parameter, shows up under the build job Parameters list and I get the Macro expansion error when I try to use that parameter. I fell back to 1.651.1 and all is functional again, i.e. I can expand the parameter and it shows up under the list. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-36140) No warning when using an non-existant credentials in withRegistry
Title: Message Title Jesse Glick resolved as Not A Defect there is no warning in the Pipeline script definition, only at runtime Not sure where you were expecting a non-runtime warning to appear, exactly, without solving the Halting Problem. If there is a runtime warning, of course it ought to say that the credentials are invalid if they were supplied, but any failure to do so is likely a bug in the Docker client, not this plugin. Jenkins / JENKINS-36140 No warning when using an non-existant credentials in withRegistry Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36331) Jenkins 1.651.3 break parameter inheritance for inheritance projects
Title: Message Title Gregory Baumgardner created an issue Jenkins / JENKINS-36331 Jenkins 1.651.3 break parameter inheritance for inheritance projects Issue Type: Bug Assignee: Unassigned Components: project-inheritance-plugin Created: 2016/Jun/29 6:51 PM Environment: Jenkins 1.651.3 running on Ubuntu 14.04 Priority: Major Reporter: Gregory Baumgardner When I upgraded from 1.651.1 to 1.651.3, my inheritance projects failed with an "org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro" Exception. The macro was a StringParameter, which shows up when I click on Run Now. However, that parameter, nor any other parameter shows up when under the build job Parameters list and I get the Macro expansion error when I try to use that parameter. I fell back to 1.651.1 and all is functional again, i.e. I can expand the parameter and it shows up under the list. Add Comment
[JIRA] (JENKINS-36330) Make It possible to limit number of jobs in a view
Title: Message Title Mikael Sundberg created an issue Jenkins / JENKINS-36330 Make It possible to limit number of jobs in a view Issue Type: New Feature Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2016/Jun/29 6:46 PM Priority: Minor Reporter: Mikael Sundberg We have a lot of pipelines at work, and when we code we want to see all the most recent jobs on one screen. But adding all jobs and sorting by most recent gets pretty uggly and brings out a scrollbar. Instead we want to be able to limit the number of jobs displayed so we dont have a scrollbar and see only the top of some pipelines. Add Comment
[JIRA] (JENKINS-36043) Saving/Applying multi-branch job config causes NullPointerException hudson.scm.SCMS.parseSCM
Title: Message Title Jesse Glick assigned an issue to Jesse Glick It is not really a core bug, though a core change resulted in the bug. This crazy code is failing to define a NullSCM the way it should (CC Matthew DeTullio). So the call to templateProject.doConfigSubmit is passing an invalid form. Jenkins / JENKINS-36043 Saving/Applying multi-branch job config causes NullPointerException hudson.scm.SCMS.parseSCM Change By: Jesse Glick Component/s: multi-branch-project-plugin Assignee: Oleg Nenashev Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You
[JIRA] (JENKINS-30600) git isn't ran inside build container
Title: Message Title Nicolas De Loof commented on JENKINS-30600 Re: git isn't ran inside build container git-client plugin do not rely on Launcher/FilePath abstraction but sends the whole GitClient implementation class to remote, making it just impossible to rely on a Launcher from caller. Would need to fully refactor GitClient implementation to run on master. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31842) Allow steps to decorate thread dumps
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-31842 Allow steps to decorate thread dumps Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Will Saxon commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We just ran into this with a Jenkins instance running as Local System on Windows, with v4.0.0 of the TFS plugin. Just deleting the 'bad' workspace entries with 'tf workspace /delete' is not enough; as noted by posix phonix there is a cache file on the system which must be also cleaned up. The Local System profile is at %WINDIR%\system32\config\systemprofile. We were able to edit %WINDIR%\system32\config\systemprofile\AppData\Local\Microsoft\Team Foundation\4.0\Cache\VersionControl.config on the problem host to remove the bad workspace entries, restart the Jenkins agent and then rerun our build. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36305) HTTP404 when browsing test actions from test result
Title: Message Title Jesse Glick commented on JENKINS-36305 Re: HTTP404 when browsing test actions from test result Oh the Attachments link in the sidebar. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36305) HTTP404 when browsing test actions from test result
Title: Message Title Jesse Glick assigned an issue to Vincent Latombe Jenkins / JENKINS-36305 HTTP404 when browsing test actions from test result Change By: Jesse Glick Assignee: Vincent Latombe Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36305) HTTP404 when browsing test actions from test result
Title: Message Title Jesse Glick started work on JENKINS-36305 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36305) HTTP404 when browsing test actions from test result
Title: Message Title Jesse Glick commented on JENKINS-36305 Re: HTTP404 when browsing test actions from test result It is not a 404 at the moment, did you change something? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title
Joachim Herb edited a comment on JENKINS-31455
Re: Build instability with "ISVNAuthentication provider did not provide credentials"
Unfortunately, I cannot confirm that downgrading to version 2.5 of the subversion plugin fixes the problem: I still see it (nearly) every second build in pipeline jobs:The checkout of the external SVN project fails with the authentication error. The external project is hosted on the same SVN server as the base project and the same username/password combination is used for the external project as for the base project.No realm is specified in the pipeline job configuration, but the checkout is done within a groovy pipeline script using the following code:{code:java}checkout scm: [$class: 'SubversionSCM',locations: [[remote: "https://some.server/xxx/",local: 'yyy',credentialsId: credentialsId,depthOption: ' files',depthOption: ' infinity',ignoreExternalsOption: false]],workspaceUpdater: [$class: 'UpdateUpdater']]{code}The variable credentialsId contains contains the ID from https://jenkins.server/credentials/store/system/domain/_/credential/(Credentials)I also tested if a loop around the checkout commands with a number of retries and a delay between them helps, but also not. Only "replay"ing the same job fixes the problem (temporarily).So a workaround would be to catch the checkout exception in the Jenkinsfile and restart/trigger the same job with the same parameters again. Is there a simple way for this (especially reuse the same parameters)?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Joachim Herb commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" Unfortunately, I cannot confirm that downgrading to version 2.5 of the subversion plugin fixes the problem: I still see it (nearly) every second build in pipeline jobs: The checkout of the external SVN project fails with the authentication error. The external project is hosted on the same SVN server as the base project and the same username/password combination is used for the external project as for the base project. No realm is specified in the pipeline job configuration, but the checkout is done within a groovy pipeline script using the following code: checkout scm: [ $class: 'SubversionSCM', locations: [[ remote: "https://some.server/xxx/", local: 'yyy', credentialsId: credentialsId, depthOption: 'files', depthOption: 'infinity', ignoreExternalsOption: false ]], workspaceUpdater: [ $class: 'UpdateUpdater' ] ] The variable credentialsId contains contains the ID from https://jenkins.server/credentials/store/system/domain/_/credential/ (Credentials) I also tested if a loop around the checkout commands with a number of retries and a delay between them helps, but also not. Only "replay"ing the same job fixes the problem (temporarily). So a workaround would be to catch the checkout exception in the Jenkinsfile and restart/trigger the same job with the same parameters again. Is there a simple way for this (especially reuse the same parameters)? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34007) Jenkins 2.0 - wizard 'X' button
Title: Message Title Bilel Yahia commented on JENKINS-34007 Re: Jenkins 2.0 - wizard 'X' button I'm running into the same issue. I accidently skipped the wizard when upgrading, and now it's impossible (as far as i know) to re run it. I need to re run the upgrade wizard to install the recommended plugins. I have the Jenkins 2.11 now, but not most of the new features that come with Jenkins 2. can anyone help? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Francis Upton resolved as Fixed Move required plugin version to 1.648.3 Jenkins / JENKINS-36197 java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Change By: Francis Upton Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Francis Upton closed an issue as Fixed Jenkins / JENKINS-36197 java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Change By: Francis Upton Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36197) java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34
Title: Message Title Francis Upton reopened an issue The dependency on the version of the bouncy castle plugin should be corrected, so this is a bug. Jenkins / JENKINS-36197 java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMReader after updating ec2-plugin from 1.33 to 1.34 Change By: Francis Upton Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-36329) Check pending reviews fails for more than 25 diff revisions
Title: Message Title Chris Petrus updated an issue Jenkins / JENKINS-36329 Check pending reviews fails for more than 25 diff revisions Change By: Chris Petrus Summary: Check pending reviews fails for more than 25 diffs diff revisions Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35905) Fail the build if node label does not exist.
Title: Message Title Jesse Glick resolved as Won't Fix Right, in some cases an agent with that label will be attached later. It is also common for the existence of a queue item to spur a Cloud to provision an agent with a matching label. Jenkins / JENKINS-35905 Fail the build if node label does not exist. Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-36329) Check pending reviews fails for more than 25 diffs
Title: Message Title Chris Petrus created an issue Jenkins / JENKINS-36329 Check pending reviews fails for more than 25 diffs Issue Type: Bug Assignee: Unassigned Attachments: 25builds_issue.JPG Components: jenkins-reviewbot Created: 2016/Jun/29 5:11 PM Environment: Jenkins 1.642.3 jenkins-reviewbot 2.4.6 patch-parameter 1.2 Java: OpenJDK 1.7.0.9 OS: Fedora 18 Browser: Google Chrome Priority: Major Reporter: Chris Petrus I've created a Jenkins Build with "Check for reviews that need building" option. It is configured to run every 5 hours and considers reviews sent to Jenkins user, for example. This build is successful as long as the pending reviews have less than 25 revisions of diffs uploaded in Review Board. When there are more than 25 revisions, I'm getting a java.lang.IndexOutOfBoundsException error during the Review Board query. The attached snapshot contains the call trace logged on the console output. In this particular case the latest revision number is 27.
[JIRA] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Konstantinos Kostarellis edited a comment on JENKINS-30744 Re: multibranch issues if branch contains / Got an issue with branches containing slashes calling ant.axisWsdl2java from within an gradle script.OS: ubuntu 14.04the org.apache.axis.tools.ant.wsdl.Wsdl2javaAntTask somehow decodes the path and throws an exception in the next step of not being able to find feature/jenkins .. because it is feature% 2jenkins 2Fjenkins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34863) WebSphere Plugin Configure System Missing
Title: Message Title Daniel Beck commented on JENKINS-34863 Re: WebSphere Plugin Configure System Missing Ugh. Seems I forgot it in https://github.com/jenkins-infra/jenkins.io/commit/c3198c8230b364015490d714d24f465917475302 and only mentioned it in the blog post. Sorry about that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34863) WebSphere Plugin Configure System Missing
Title: Message Title Bruce Coveny commented on JENKINS-34863 Re: WebSphere Plugin Configure System Missing Hi Daniel, Not to be a pain but is this documented somewhere? I went back through all the what's news for the change log and also the overview of Jenkins 2.0. Something like this I would have thought would have been a bigger announcement since all configuration like this was done in one spot before. Thank you for the information and I do see where that information can be found and changed now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35366) Some TaskScannerPluginTest fail while removing build step
Title: Message Title Andrew Bayer resolved as Fixed Seems to be passing now with increased window size, but there could be a non-deterministic issue still. Jenkins / JENKINS-35366 Some TaskScannerPluginTest fail while removing build step Change By: Andrew Bayer Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title Bryson Gibbons commented on JENKINS-32797 Re: Access to check for unprotected/never secured paths Actually (because I didn't do a full look over my workaround code) I am using getUnprotectedRootActions(), but I still need to keep a separate list of AlwaysReadablePaths, and a regex for slave agents. All told I am duplicating about 50 lines of code from Jenkins.java (as an almost exact duplicate) to do the same operation that is contained in the catch clause of Jenkins.getTarget(). In my case I have to check those exceptions before I try authenticating, because I cannot (unfortunately) control filter chaining after I attempt authentication - that process happens in a filter in external code, that I call using super.doFilter(). I may have misspoke about this being a problem with kerberos-sso-plugin, only because do not have a way to test it myself; if kerberos-sso-plugin does not have this issue, it is because it is able to execute the filter chain regardless of whether authentication was successful or not. I can try to attempt something similar, but I don't know if I will be successful in doing so. Going to test that before pursuing this further... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36087) Set stage result manually
Title: Message Title Sam Van Oort closed an issue as Fixed Jenkins / JENKINS-36087 Set stage result manually Change By: Sam Van Oort Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
