[JIRA] (JENKINS-48221) Add parser for abi-compliance-checker
Title: Message Title Vyacheslav Bogachenkov commented on JENKINS-48221 Re: Add parser for abi-compliance-checker Have instructions? Need to know Java? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186800.1511616866000.8793.1568007240222%40Atlassian.JIRA.
[JIRA] (JENKINS-59275) Add support for config drive
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-59275 Add support for config drive Issue Type: Improvement Assignee: Pavel Janoušek Components: openstack-cloud-plugin Created: 2019-09-09 05:31 Priority: Major Reporter: Pavel Janoušek Currently we can't control config drive (1) option through template engine. The aim of this JIRA is to support this option in the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-59274) Support pipeline search in the folder
Title: Message Title runze xia created an issue Jenkins / JENKINS-59274 Support pipeline search in the folder Issue Type: New Feature Assignee: Aytunc BEKEN Components: multibranch-action-triggers-plugin Created: 2019-09-09 03:25 Priority: Minor Reporter: runze xia Now I can search the pipeline of the root directory when using the plugin. It would be better if you could support searching for the pipeline in the folder. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Torsten Walter commented on JENKINS-54662 Re: hudson.model.UsageStatistics not compatible with CasC plugin Oleg Nenashev Any update on this? The linked PR was closed without being merged. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195453.1542317055000.8787.1567986180199%40Atlassian.JIRA.
[JIRA] (JENKINS-58420) Column shows "-" on failed builds
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-58420 Column shows "-" on failed builds Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/203 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200547.1562750576000.8779.1567978560260%40Atlassian.JIRA.
[JIRA] (JENKINS-58420) Column shows "-" on failed builds
Title: Message Title Ulli Hafner started work on JENKINS-58420 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200547.1562750576000.8777.1567978560233%40Atlassian.JIRA.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title René Scheibe commented on JENKINS-57694 Re: BuildChooser logs a missing descriptor message For the IncompatibleClassChangeError issue I have a fix. I linked the respective pull request. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.8775.1567975440124%40Atlassian.JIRA.
[JIRA] (JENKINS-56264) Links in trend chart must not use displayName
Title: Message Title Ulli Hafner updated JENKINS-56264 Jenkins / JENKINS-56264 Links in trend chart must not use displayName Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197835.1551089781000.8765.1567971900831%40Atlassian.JIRA.
[JIRA] (JENKINS-48802) Possibility to add/change the path that used to display source files
Title: Message Title Ulli Hafner updated JENKINS-48802 Jenkins / JENKINS-48802 Possibility to add/change the path that used to display source files Change By: Ulli Hafner Resolution: Fixed Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187580.1515085477000.8767.1567971900994%40Atlassian.JIRA.
[JIRA] (JENKINS-48802) Possibility to add/change the path that used to display source files
Title: Message Title Ulli Hafner updated JENKINS-48802 Jenkins / JENKINS-48802 Possibility to add/change the path that used to display source files Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187580.1515085477000.8755.1567971840706%40Atlassian.JIRA.
[JIRA] (JENKINS-59273) Known security vulnerabilities
Title: Message Title Marky Jackson started work on JENKINS-59273 Change By: Marky Jackson Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201773.1567956187000.8750.1567966560265%40Atlassian.JIRA.
[JIRA] (JENKINS-58634) Custom ID cause broken link in job view
Title: Message Title
Ulli Hafner edited a comment on JENKINS-58634
Re: Custom ID cause broken link in job view
The problem is that you are using a numeric only ID. Seems that such IDs are claimed as build number IDs somewhere in Jenkins core (Build or Run instance). So my URL actually will never be resolved. If you use an id with character in it like {{m1000}} then everything works as expected. That means I can do nothing in my plugin here. You can try to file that as bug in core but I doubt that this will be fixed by someone as an actual build number can also resolve to the ID you have chosen.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200802.1563961595000.8739.1567958520219%40Atlassian.JIRA.
[JIRA] (JENKINS-58634) Custom ID cause broken link in job view
Title: Message Title Ulli Hafner resolved as Won't Fix The problem is that you are using a numeric only ID. Seems that such IDs are claimed as build number IDs somewhere in Jenkins core (Build or Run instance). So my URL actually will never be resolved. If you use an id with character in it m1000 then everything works as expected. That means I can do nothing in my plugin here. You can try to file that as bug in core but I doubt that this will be fixed by someone as an actual build number can also resolve to the ID you have chosen. Jenkins / JENKINS-58634 Custom ID cause broken link in job view Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you 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-59273) Known security vulnerabilities
Title: Message Title Marky Jackson commented on JENKINS-59273 Re: Known security vulnerabilities Github issue: https://github.com/jenkinsci/gitlab-plugin/issues/971 Github PR: https://github.com/jenkinsci/gitlab-plugin/pull/972 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201773.1567956187000.8735.1567956540147%40Atlassian.JIRA.
[JIRA] (JENKINS-59273) Known security vulnerabilities
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59273 Known security vulnerabilities Issue Type: Patch Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-08 15:23 Priority: Major Reporter: Marky Jackson org.apache.httpcomponents:httpclient security CVE-2014-3577 More information com.fasterxml.jackson.core:jackson-databind security CVE-2019-14379 More information Add Comment
[JIRA] (JENKINS-56264) Links in trend chart must not use displayName
Title: Message Title Ulli Hafner started work on JENKINS-56264 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197835.1551089781000.8723.1567954380303%40Atlassian.JIRA.
[JIRA] (JENKINS-56264) Links in trend chart must not use displayName
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56264 Links in trend chart must not use displayName Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/201/ Labels: msbuild plugin warnings Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197835.1551089781000.8719.1567954320197%40Atlassian.JIRA.
[JIRA] (JENKINS-58787) Be able to create a job posting config.xml - Or improve docs
Title: Message Title Janario Oliveira closed an issue as Not A Defect Jenkins / JENKINS-58787 Be able to create a job posting config.xml - Or improve docs Change By: Janario Oliveira Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201097.1564756878000.8714.1567949880319%40Atlassian.JIRA.
[JIRA] (JENKINS-58787) Be able to create a job posting config.xml - Or improve docs
Title: Message Title Janario Oliveira commented on JENKINS-58787 Re: Be able to create a job posting config.xml - Or improve docs This is more related to Jenkins authorization itself not http request plugin But to manage Jenkins jobs I would recommend JobDsl plugin which is made for this https://jenkinsci.github.io/job-dsl-plugin/ Otherwise you'll have to manage the Jenkins authorization to allow those requests, which I'm not sure on how to help (You could try on the Jenkins mail list) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201097.1564756878000.8712.1567949880284%40Atlassian.JIRA.
[JIRA] (JENKINS-58694) Not able to trigger build via API call
Title: Message Title Janario Oliveira updated an issue Jenkins / JENKINS-58694 Not able to trigger build via API call Change By: Janario Oliveira Component/s: core Component/s: http-request-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200983.1564322832000.8710.1567945500450%40Atlassian.JIRA.
[JIRA] (JENKINS-58260) Trouble contacting Salt API
Title: Message Title Janario Oliveira updated an issue Jenkins / JENKINS-58260 Trouble contacting Salt API Change By: Janario Oliveira Component/s: http-request-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200324.1561756576000.8708.1567945440162%40Atlassian.JIRA.
[JIRA] (JENKINS-55977) httpRequest method causes NullPointerException
Title: Message Title Janario Oliveira updated JENKINS-55977 Jenkins / JENKINS-55977 httpRequest method causes NullPointerException Change By: Janario Oliveira Status: In Review Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197388.1549378282000.8705.1567945200243%40Atlassian.JIRA.
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Ariel M commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 Yves Schumann do you think the uninstall of JobConfigHistoryPlugin can help me solve this issue: https://issues.jenkins-ci.org/browse/JENKINS-59239 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189669.1522939372000.8689.1567943880379%40Atlassian.JIRA.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title
René Scheibe edited a comment on JENKINS-57694
Re: BuildChooser logs a missing descriptor message
With the current state of the master branch (commit d1d765a5fabb407d6a8dd6264641df3233ac33c3) I ran {{mvn hpi:run}} to reproduce this.I just tried to create a new multi-branch pipeline via "Jenkins" - "New Item" - "multibranch-test" - "Multibranch Pipeline" - "OK" and got this:{code:java}Sep 08, 2019 1:14:17 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /jenkins/job/multibranch-test/configure. Reason: java.lang.NullPointerException: Descriptor list is null for context 'class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject' in thread 'Handling GET /jenkins/job/multibranch-test/configure from 127.0.0.1 : qtp2091047140-1088 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly'java.lang.NullPointerException: Descriptor list is null for context 'class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject' in thread 'Handling GET /jenkins/job/multibranch-test/configure from 127.0.0.1 : qtp2091047140-1088 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly' at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73) at hudson.Functions.filterDescriptors(Functions.java:1888)... {code}Are you aware of this and can reproduce it? This seems to be reported in JENKINS-47494 already. That's confusing a bit. It does not occur anymore when I temporarily remove the {{multiple-scms}} test dependency from pom.xml. Ok, so that's understood.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title Mark Waite edited a comment on JENKINS-57694 Re: BuildChooser logs a missing descriptor message The second message in the report (java.lang.IncompatibleClassChangeError) is generated when I run the git plugin unit tests. It does not cause any test to fail, but it is very suspicious to me that there is something wrong that I haven't yet understood. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.8684.1567942620217%40Atlassian.JIRA.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title Mark Waite commented on JENKINS-57694 Re: BuildChooser logs a missing descriptor message The second message in the report is generated when I run the git plugin unit tests. It does not cause any test to fail, but it is very suspicious to me that there is something wrong that I haven't yet understood. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.8683.1567942620189%40Atlassian.JIRA.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title
René Scheibe edited a comment on JENKINS-57694
Re: BuildChooser logs a missing descriptor message
With the current state of the master branch (commit d1d765a5fabb407d6a8dd6264641df3233ac33c3) I ran {{mvn hpi:run}} to reproduce this.I just tried to create a new multi-branch pipeline via "Jenkins" - "New Item" - "multibranch-test" - "Multibranch Pipeline" - "OK" and got this:{code:java}Sep 08, 2019 1:14:17 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /jenkins/job/multibranch-test/configure. Reason: java.lang.NullPointerException: Descriptor list is null for context 'class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject' in thread 'Handling GET /jenkins/job/multibranch-test/configure from 127.0.0.1 : qtp2091047140-1088 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly'java.lang.NullPointerException: Descriptor list is null for context 'class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject' in thread 'Handling GET /jenkins/job/multibranch-test/configure from 127.0.0.1 : qtp2091047140-1088 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly' at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73) at hudson.Functions.filterDescriptors(Functions.java:1888)... {code}Are you aware of this and can reproduce it? This seems to be reported in ENKINS JENKINS -47494 already.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you 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-57694) BuildChooser logs a missing descriptor message
Title: Message Title
René Scheibe edited a comment on JENKINS-57694
Re: BuildChooser logs a missing descriptor message
With the current state of the master branch (commit d1d765a5fabb407d6a8dd6264641df3233ac33c3) I ran {{mvn hpi:run}} to reproduce this.I just tried to create a new multi-branch pipeline via "Jenkins" - "New Item" - "multibranch-test" - "Multibranch Pipeline" - "OK" and got this:{code:java}Sep 08, 2019 1:14:17 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /jenkins/job/multibranch-test/configure. Reason: java.lang.NullPointerException: Descriptor list is null for context 'class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject' in thread 'Handling GET /jenkins/job/multibranch-test/configure from 127.0.0.1 : qtp2091047140-1088 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly'java.lang.NullPointerException: Descriptor list is null for context 'class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject' in thread 'Handling GET /jenkins/job/multibranch-test/configure from 127.0.0.1 : qtp2091047140-1088 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly' at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73) at hudson.Functions.filterDescriptors(Functions.java:1888)... {code}Are you aware of this and can reproduce it? This seems to be reported in ENKINS-47494 already.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you 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-57694) BuildChooser logs a missing descriptor message
Title: Message Title René Scheibe commented on JENKINS-57694 Re: BuildChooser logs a missing descriptor message With the current state of the master branch (commit d1d765a5fabb407d6a8dd6264641df3233ac33c3) I ran mvn hpi:run to reproduce this. I just tried to create a new multi-branch pipeline via "Jenkins" - "New Item" - "multibranch-test" - "Multibranch Pipeline" - "OK" and got this: Sep 08, 2019 1:14:17 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /jenkins/job/multibranch-test/configure. Reason: java.lang.NullPointerException: Descriptor list is null for context 'class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject' in thread 'Handling GET /jenkins/job/multibranch-test/configure from 127.0.0.1 : qtp2091047140-1088 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly' java.lang.NullPointerException: Descriptor list is null for context 'class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject' in thread 'Handling GET /jenkins/job/multibranch-test/configure from 127.0.0.1 : qtp2091047140-1088 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly' at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73) at hudson.Functions.filterDescriptors(Functions.java:1888) ... Are you aware of this and can reproduce it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title Mark Waite commented on JENKINS-57694 Re: BuildChooser logs a missing descriptor message The Docker image which shows the problem is defined in my docker-lfs repository. Build the lts-with-plugins branch with docker build and run it with docker run Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.8675.1567941540118%40Atlassian.JIRA.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title René Scheibe commented on JENKINS-57694 Re: BuildChooser logs a missing descriptor message Hi Mark Waite, can you also provide the exact job setup in the issue description? Otherwise it's very hard to reproduce this. I guess currently it's more a note for yourself. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.8673.1567940940248%40Atlassian.JIRA.
[JIRA] (JENKINS-59272) Change default shell for 'sh' in pipeline
Title: Message Title Grzegorz Zieba created an issue Jenkins / JENKINS-59272 Change default shell for 'sh' in pipeline Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-09-08 11:03 Priority: Minor Reporter: Grzegorz Zieba https://support.cloudbees.com/hc/en-us/articles/215171038 JENKINS-57321 sh "..." allocate default shell and then execute script according to shabang But there is no way to change shell for 'sh' statement . And that's an issue. It could be useful to overwrite default shell for example with: sh "script: 'ls -l' shell: '/bin/sh'" Add Comment
[JIRA] (JENKINS-59239) Pipeline job's builds are missing in bulk after failure
Title: Message Title Ariel M commented on JENKINS-59239 Re: Pipeline job's builds are missing in bulk after failure Can someone check it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201696.1567669735000.8670.1567937940075%40Atlassian.JIRA.
[JIRA] (JENKINS-43214) Support for multiple jenkins master with one github application using redirect uri
Title: Message Title Fred Vogt commented on JENKINS-43214 Re: Support for multiple jenkins master with one github application using redirect uri https://github.com/jenkinsci/github-oauth-plugin/pull/111 Addresses this. https://developer.github.com/apps/building-oauth-apps/authorizing-oauth-apps/#redirect-urls Would be nice to get it reviewed and merged. It appears that the Github OAuth app URL would have to be a virtual host. Jenkins servers would then pass the redirect URI sub-path. Example: Github OAuth App Callback URL: https://jenkins.example.com/github-oauth Redirect URL: https://jenkins.example.com/github-oauth///securityRealm/finishLogin Where the vhost 'jenkins.example.com/github-oauth' using path based routing to proxy the callback to the correct jenkins server: https://jenkins-..example.com/securityRealm/finishLogin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180335.1490862927000.8668.1567935660349%40Atlassian.JIRA.
[JIRA] (JENKINS-48221) Add parser for abi-compliance-checker
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-48221 Add parser for abi-compliance-checker Change By: Ulli Hafner Summary: please, create publisher Add parser for abi-compliance-checker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186800.1511616866000.8664.1567934100160%40Atlassian.JIRA.
[JIRA] (JENKINS-58635) New builds with DELTA quality gates fail immediately
Title: Message Title Ulli Hafner updated JENKINS-58635 Jenkins / JENKINS-58635 New builds with DELTA quality gates fail immediately Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200803.1563962484000.8662.1567934040355%40Atlassian.JIRA.
[JIRA] (JENKINS-48221) please, create publisher for abi-compliance-checker
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-48221 please, create publisher for abi-compliance-checker Typically, new parsers are added by volunteers. Are you interested in providing a new parser? Change By: Ulli Hafner Component/s: analysis-model Labels: help-wanted newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186800.1511616866000.8659.1567933560283%40Atlassian.JIRA.
