[JIRA] (JENKINS-60607) mattermost-plugin 3.0 does not work with Mattermost 5.6.2
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-60607 mattermost-plugin 3.0 does not work with Mattermost 5.6.2 Issue Type: Bug Assignee: Jo Vandeginste Components: mattermost-plugin Created: 2019-12-30 09:19 Environment: Jenkins Version: 2.204.1 mattermost-plugin: 3.0.0 Mattermost Version: 5.6.2 Priority: Blocker Reporter: Philipp Moeller After updating to versin 3.0.0 of the mattermost-plugin, notifications are not posted to the Mattermost server 5.6.2 anymore. After a downgrade to version 2.7.1 notifications are posted again. Unfortunately there is no up-to-date changelog for this new major release to help narrow this down. The following exception can be found in the log: 2019-12-30 08:48:06.321+ [id=285] WARNING j.p.m.StandardMattermostService#publish: Error posting to Mattermost java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171) at java.net.SocketInputStream.read(SocketInputStream.java:141) at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137) at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153) at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:280) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138) at org.apache.http.impl.conn.De
[JIRA] (JENKINS-58167) files-with-issues folders excessively large
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-58167 files-with-issues folders excessively large Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-06-24 13:59 Environment: Jenkins 2.164.3 warnings-ng 5.1.0 Priority: Minor Reporter: Philipp Moeller We are using the warnings-ng plugin to analyze some of our projects with the following code recordIssues enabledForFailure: true, blameDisabled: true,tools: [java(), mavenConsole(), taskScanner(highTags: 'FIXME', normalTags: 'TODO, CHECKSTYLE IGNORE')] This leads to very large folders on the Jenkins master (around 250MB for a single build) compared to the old Static Analysis Plugin. An option to disable this behaviour or to specify retention times separatly from build retention times would be appreciated.
[JIRA] (JENKINS-57427) Use warnings-next-generation instead of old plugins in pipeline-maven-plugin
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-57427 Use warnings-next-generation instead of old plugins in pipeline-maven-plugin Issue Type: New Feature Assignee: Alvaro Lobato Components: pipeline-maven-plugin, warnings-ng-plugin Created: 2019-05-13 10:38 Priority: Minor Reporter: Philipp Moeller Use the warnings-ng-plugin instead of the old plugins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56936) Green Balls Plugin has too many implicit dependencies
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-56936 Green Balls Plugin has too many implicit dependencies Issue Type: Bug Assignee: asgeirn Components: greenballs-plugin Created: 2019-04-08 14:00 Labels: plugin user-experience Priority: Minor Reporter: Philipp Moeller Green Balls is a very popular, useful, stable and old plugin. Since it's so stable it hasn't been released in a long time and accumulated quite a bunch of implicit dependencies which all seem unnecessary. Reducing the number of unnecessary plugins is helpful when trying to switch to Jenkins Configuration as Source. Please release a new version of the plugin to reduce the dependency tree. Add Comment
[JIRA] (JENKINS-55256) ssh-agent in pipeline leaves defunct processes on swarm client
Title: Message Title
Philipp Moeller edited a comment on JENKINS-55256
Re: ssh-agent in pipeline leaves defunct processes on swarm client
I just confirmed that this happens during normal execution of code like: { quote code:java } node('basic') { sshagent(['X']) { sh "echo foo" }}{ quote code }
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55256) ssh-agent in pipeline leaves defunct processes on swarm client
Title: Message Title
Philipp Moeller edited a comment on JENKINS-55256
Re: ssh-agent in pipeline leaves defunct processes on swarm client
I just confirmed that this happens during normal execution of code like: {quote}node('basic') { sshagent(['X']) { }}{quote}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55256) ssh-agent in pipeline leaves defunct processes on swarm client
Title: Message Title
Philipp Moeller edited a comment on JENKINS-55256
Re: ssh-agent in pipeline leaves defunct processes on swarm client
I just confirmed that this happens during normal execution of code like: {quote}node('basic') { sshagent(['X']) { { sh "echo Test" } }{quote}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55256) ssh-agent in pipeline leaves defunct processes on swarm client
Title: Message Title
Philipp Moeller edited a comment on JENKINS-55256
Re: ssh-agent in pipeline leaves defunct processes on swarm client
I just confirmed that this happens during normal execution of code like: {quote}node('basic') { sshagent(['X']) { sh "echo Test" }}{quote}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55256) ssh-agent in pipeline leaves defunct processes on swarm client
Title: Message Title
Philipp Moeller commented on JENKINS-55256
Re: ssh-agent in pipeline leaves defunct processes on swarm client
I just confirmed that this happens during normal execution of code like:
node('basic') { sshagent(['X'])
Unknown macro: { sh "echo Test" }
}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55256) ssh-agent in pipeline leaves defunct processes on swarm client
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-55256 ssh-agent in pipeline leaves defunct processes on swarm client Issue Type: Bug Assignee: Oleg Nenashev Components: pipeline, ssh-agent-plugin, swarm-plugin Created: 2018-12-19 09:38 Environment: Jenkins ver. 2.150.1, SSH Agent Plugin 1.17, Self-Organizing Swarm Plug-in Modules 3.15 Priority: Major Reporter: Philipp Moeller We run build nodes via Docker and the Swarm Plugin. After a while defunct processes start to pile up on the nodes: 1000 9386 9371 1 Dec18 ? 00:10:49 java -jar /usr/share/jenkins/swarm-client-3.15-jar-with-dependencies.jar -fsroot /var/jenkins-node_home -master https://jenkins.cosmos.local -username XXX -password XXX -executors 10 -mode exclusive -labels linux basic build -name basic-node-dc -disableSslVerification -description Basic node [root@XXX:/root]# ps -ef | grep defu 1000 2489 9386 0 Dec18 ? 00:00:00 [ssh-agent] 1000 2514 9386 0 Dec18 ? 00:00:00 [ssh-agent] 1000 2544 9386 0 Dec18 ? 00:00:00 [ssh-agent] 1000 2618 9386 0 Dec18 ? 00:00:00 [ssh-agent] ... We run ssh-agent often through many scripted pipelines so it is hard to trace it down to a specific Pipeline, but this behavior shouldn't occur to begin with.
[JIRA] (JENKINS-38992) Cache libraries specified by a permanent revision string
Title: Message Title Philipp Moeller commented on JENKINS-38992 Re: Cache libraries specified by a permanent revision string What is missing for this to be integrated? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49685) Unable to download the NVD CVE data. Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"
Title: Message Title Philipp Moeller commented on JENKINS-49685 Re: Unable to download the NVD CVE data. Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required" IMO that would solve the issue, but I think it should not be necessary. The Jenkins Plugin Manager and almost all other plugins have no issue with the configured proxy. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49685) Unable to download the NVD CVE data. Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"
Title: Message Title Philipp Moeller edited a comment on JENKINS-49685 Re: Unable to download the NVD CVE data. Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required" IMO that would solve the issue, but I think it should not be necessary. The Jenkins Plugin Manager and almost all other plugins have no issue with the configured proxy. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50343) ComposedClosure not working with List.each
Title: Message Title
Philipp Moeller created an issue
Jenkins / JENKINS-50343
ComposedClosure not working with List.each
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-03-22 15:19
Environment:
Jenkins ver. 2.89.4, Pipeline: Groovy 2.45
Labels:
groovy pipeline
Priority:
Major
Reporter:
Philipp Moeller
The following Pipeline code does not yield the expected result.
def xs = ['1', '2', '3']
def fix = { it + '-webapp' } >> { echo "ha ${it}" }
echo "${fix('foobar')}" // works
xs.each { echo "${it}" } // works
xs.each fix // fails
Results in the following output:
[Pipeline] echo
foobar-webapp
[Pipeline] echo
1
[Pipeline] echo
2
[Pipeline] echo
3
[Pipeline] End of Pipeline
Finished: SUCCESS
So calling the ComposedClosure works, calling each with a simple Closure works, but calling each with the ComposedClosure does not work. The expected result is that calling each with the ComposedClosure yields:
[JIRA] (JENKINS-49685) Unable to download the NVD CVE data. Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-49685 Unable to download the NVD CVE data. Caused by: java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required" Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2018-02-22 07:18 Environment: Jenkins 2.89.4, JDK 8u161 Priority: Major Reporter: Philipp Moeller My Jenkins Instance is sitting behind a proxy that requires basic authentication, which is configured in the Jenkins Instance. Updating plugins via https works without problems with the configured proxy. When trying to run the dependencyCheckAnalyzer from a Jenkins Pipeline I get the following error and stack trace: [DependencyCheck] One or more exceptions were thrown while executing Dependency-Check [DependencyCheck] Exception Caught: org.owasp.dependencycheck.data.update.exception.UpdateException [DependencyCheck] Cause: java.util.concurrent.ExecutionException: org.owasp.dependencycheck.utils.DownloadFailedException: Error making HTTP GET request. [DependencyCheck] Message: Unable to download the NVD CVE data. [DependencyCheck] org.owasp.dependencycheck.data.update.exception.UpdateException: Unable to download the NVD CVE data. [DependencyCheck] at org.owasp.dependencycheck.data.update.NvdCveUpdater.update(NvdCveUpdater.java:130) [DependencyCheck] at org.owasp.dependencycheck.Engine.doUpdates(Engine.java:889) [DependencyCheck] at org.owasp.dependencycheck.Engine.initializeAndUpdateDatabase(Engine.java:716) [DependencyCheck] at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:642) [DependencyCheck] at org.jen
[JIRA] (JENKINS-17440) SSH Plugin throws auth cancel
Title: Message Title Philipp Moeller commented on JENKINS-17440 Re: SSH Plugin throws auth cancel Can confirm this on Jenkins 2.7.2 SSH Plugin 2.4 with the default Jenkins Dockerimage. 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-37310) Support Jump Hosts via SSH Tunnel
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-37310 Support Jump Hosts via SSH Tunnel Issue Type: Improvement Assignee: bap Components: publish-over-ssh-plugin Created: 2016/Aug/10 1:39 PM Priority: Major Reporter: Philipp Moeller Often Servers that need to deployed are in a DMZ or otherwise only reachable through a jump host. This is already supported by JSch (http://www.jcraft.com/jsch/examples/JumpHosts.java.html) and would be a great addition to this plugin. Add Comment
[JIRA] [thinBackup] (JENKINS-35324) Support restoring secrects
Title: Message Title Philipp Moeller created an issue Jenkins / JENKINS-35324 Support restoring secrects Issue Type: New Feature Assignee: Thomas Fürer Components: thinBackup Created: 2016/Jun/03 7:25 AM Environment: Jenkins ver. 1.642.2, thinBackup 1.7.4 Priority: Minor Reporter: Philipp Moeller When trying to restore a backup on a fresh install, I've noticed that the secrets are missing and password cannot be encrypted. I understand why some users would not want to backup secrets, but in some cases this is really useful. Could you add an option to backup the secrets folder as well? Add Comment
[JIRA] [jobconfighistory-plugin] (JENKINS-30089) new config history created on each multibranch build
Title: Message Title Philipp Moeller commented on JENKINS-30089 Re: new config history created on each multibranch build Jochen A. Fürbacher Jesse Glick I have seen this option and it is enabled in my Jenkins Instance. I also don't see any duplicated history, but there are still tons of files in the following directories: `$JENKINS_HOME/config-history-jobs/MULTIBRANCH_JOB/branches/*` (note the branches subdirectory). This is the real culprit IMO and makes it necessary to exclude all multi-branch jobs from the job config history or disabling the plugin alltogether. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-30089) new config history created on each multibranch build
Title: Message Title Philipp Moeller commented on JENKINS-30089 Re: new config history created on each multibranch build Jesse Glick I don't see how I can configure the plugin in such a way. Can you explain this a little bit further? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-30089) new config history created on each multibranch build
Title: Message Title Philipp Moeller edited a comment on JENKINS-30089 Re: new config history created on each multibranch build Can confirm this on Jenkins Version 1.642.2 and it isa is a pain. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-30089) new config history created on each multibranch build
Title: Message Title Philipp Moeller commented on JENKINS-30089 Re: new config history created on each multibranch build Can confirm this on Jenkins Version 1.642.2 and it isa pain. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multi-branch-project-plugin] (JENKINS-33582) empty parser listbox in multi-branch project
Title: Message Title Philipp Moeller edited a comment on JENKINS-33582 Re: empty parser listbox in multi-branch project I have just encountered the same issue on Jenkins 1.642.2 using the multi-branch-project-plugin 0.4.2 but have some additional information.Users in the ADMIN ADMINISTRATORS group see the list of available parsers, while users in the INTEGRATOR group do not see.I will attach a shortened version of our authorization matrix, but I have not verified that this shortened version can reproduce the problem.com.cloudbees.plugins.credentials.CredentialsProvider.Create:ADMINISTRATORScom.cloudbees.plugins.credentials.CredentialsProvider.Delete:ADMINISTRATORScom.cloudbees.plugins.credentials.CredentialsProvider.ManageDomains:ADMINISTRATORScom.cloudbees.plugins.credentials.CredentialsProvider.Update:ADMINISTRATORScom.cloudbees.plugins.credentials.CredentialsProvider.View:ADMINISTRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:ADMINISTRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:ADMINISTRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:ADMINISTRATORShudson.model.Computer.Build:ADMINISTRATORShudson.model.Computer.Configure:ADMINISTRATORShudson.model.Computer.Connect:ADMINISTRATORShudson.model.Computer.Create:ADMINISTRATORShudson.model.Computer.Delete:ADMINISTRATORShudson.model.Computer.Disconnect:ADMINISTRATORShudson.model.Hudson.Administer:ADMINISTRATORShudson.model.Hudson.ConfigureUpdateCenter:ADMINISTRATORShudson.model.Hudson.Read:ADMINISTRATORShudson.model.Hudson.RunScripts:ADMINISTRATORShudson.model.Hudson.UploadPlugins:ADMINISTRATORShudson.model.Item.Build:ADMINISTRATORShudson.model.Item.Cancel:ADMINISTRATORShudson.model.Item.Configure:ADMINISTRATORShudson.model.Item.Create:ADMINISTRATORShudson.model.Item.Delete:ADMINISTRATORShudson.model.Item.Discover:ADMINISTRATORShudson.model.Item.Read:ADMINISTRATORShudson.model.Item.Workspace:ADMINISTRATORShudson.model.Run.Delete:ADMINISTRATORShudson.model.Run.Update:ADMINISTRATORShudson.model.View.Configure:ADMINISTRATORShudson.model.View.Create:ADMINISTRATORShudson.model.View.Delete:ADMINISTRATORShudson.model.View.Read:ADMINISTRATORShudson.scm.SCM.Tag:ADMINISTRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:INTEGRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:INTEGRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:INTEGRATORShudson.model.Hudson.Read:INTEGRATORShudson.model.Hudson.RunScripts:INTEGRATORShudson.model.Item.Build:INTEGRATORShudson.model.Item.Cancel:INTEGRATORShudson.model.Item.Configure:INTEGRATORShudson.model.Item.Create:INTEGRATORShudson.model.Item.Delete:INTEGRATORShudson.model.Item.Discover:INTEGRATORShudson.model.Item.Read:INTEGRATORShudson.model.Item.Workspace:INTEGRATORShudson.model.Run.Delete:INTEGRATORShudson.model.Run.Update:INTEGRATORShudson.model.View.Configure:INTEGRATORShudson.model.View.Create:INTEGRATORShudson.model.View.Delete:INTEGRATORShudson.model.View.Read:INTEGRATORShudson.scm.SCM.Tag:INTEGRATORS Add Comment
[JIRA] [multi-branch-project-plugin] (JENKINS-33582) empty parser listbox in multi-branch project
Title: Message Title Philipp Moeller edited a comment on JENKINS-33582 Re: empty parser listbox in multi-branch project I have just encountered the same issue on Jenkins 1.642.2 using the multi-branch-project-plugin 0.4.2 but have some additional information.Users in the ADMINISTRATORS group see the list of available parsers, while users in the INTEGRATOR group do not see .I will attach a shortened version of our authorization matrix, but I have not verified that this shortened version can reproduce the problem.com.cloudbees.plugins.credentials.CredentialsProvider.Create:ADMINISTRATORScom.cloudbees.plugins.credentials.CredentialsProvider.Delete:ADMINISTRATORScom.cloudbees.plugins.credentials.CredentialsProvider.ManageDomains:ADMINISTRATORScom.cloudbees.plugins.credentials.CredentialsProvider.Update:ADMINISTRATORScom.cloudbees.plugins.credentials.CredentialsProvider.View:ADMINISTRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:ADMINISTRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:ADMINISTRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:ADMINISTRATORShudson.model.Computer.Build:ADMINISTRATORShudson.model.Computer.Configure:ADMINISTRATORShudson.model.Computer.Connect:ADMINISTRATORShudson.model.Computer.Create:ADMINISTRATORShudson.model.Computer.Delete:ADMINISTRATORShudson.model.Computer.Disconnect:ADMINISTRATORShudson.model.Hudson.Administer:ADMINISTRATORShudson.model.Hudson.ConfigureUpdateCenter:ADMINISTRATORShudson.model.Hudson.Read:ADMINISTRATORShudson.model.Hudson.RunScripts:ADMINISTRATORShudson.model.Hudson.UploadPlugins:ADMINISTRATORShudson.model.Item.Build:ADMINISTRATORShudson.model.Item.Cancel:ADMINISTRATORShudson.model.Item.Configure:ADMINISTRATORShudson.model.Item.Create:ADMINISTRATORShudson.model.Item.Delete:ADMINISTRATORShudson.model.Item.Discover:ADMINISTRATORShudson.model.Item.Read:ADMINISTRATORShudson.model.Item.Workspace:ADMINISTRATORShudson.model.Run.Delete:ADMINISTRATORShudson.model.Run.Update:ADMINISTRATORShudson.model.View.Configure:ADMINISTRATORShudson.model.View.Create:ADMINISTRATORShudson.model.View.Delete:ADMINISTRATORShudson.model.View.Read:ADMINISTRATORShudson.scm.SCM.Tag:ADMINISTRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:INTEGRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:INTEGRATORScom.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:INTEGRATORShudson.model.Hudson.Read:INTEGRATORShudson.model.Hudson.RunScripts:INTEGRATORShudson.model.Item.Build:INTEGRATORShudson.model.Item.Cancel:INTEGRATORShudson.model.Item.Configure:INTEGRATORShudson.model.Item.Create:INTEGRATORShudson.model.Item.Delete:INTEGRATORShudson.model.Item.Discover:INTEGRATORShudson.model.Item.Read:INTEGRATORShudson.model.Item.Workspace:INTEGRATORShudson.model.Run.Delete:INTEGRATORShudson.model.Run.Update:INTEGRATORShudson.model.View.Configure:INTEGRATORShudson.model.View.Create:INTEGRATORShudson.model.View.Delete:INTEGRATORShudson.model.View.Read:INTEGRATORShudson.scm.SCM.Tag:INTEGRATORS Add Comment
[JIRA] [multi-branch-project-plugin] (JENKINS-33582) empty parser listbox in multi-branch project
Title: Message Title Philipp Moeller reopened an issue I have just encountered the same issue on Jenkins 1.642.2 using the multi-branch-project-plugin 0.4.2 but have some additional information. Users in the ADMIN group see the list of available parsers, while users in the INTEGRATOR group do not see. I will attach a shortened version of our authorization matrix, but I have not verified that this shortened version can reproduce the problem. com.cloudbees.plugins.credentials.CredentialsProvider.Create:ADMINISTRATORS com.cloudbees.plugins.credentials.CredentialsProvider.Delete:ADMINISTRATORS com.cloudbees.plugins.credentials.CredentialsProvider.ManageDomains:ADMINISTRATORS com.cloudbees.plugins.credentials.CredentialsProvider.Update:ADMINISTRATORS com.cloudbees.plugins.credentials.CredentialsProvider.View:ADMINISTRATORS com.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:ADMINISTRATORS com.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:ADMINISTRATORS com.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:ADMINISTRATORS hudson.model.Computer.Build:ADMINISTRATORS hudson.model.Computer.Configure:ADMINISTRATORS hudson.model.Computer.Connect:ADMINISTRATORS hudson.model.Computer.Create:ADMINISTRATORS hudson.model.Computer.Delete:ADMINISTRATORS hudson.model.Computer.Disconnect:ADMINISTRATORS hudson.model.Hudson.Administer:ADMINISTRATORS hudson.model.Hudson.ConfigureUpdateCenter:ADMINISTRATORS hudson.model.Hudson.Read:ADMINISTRATORS hudson.model.Hudson.RunScripts:ADMINISTRATORS hudson.model.Hudson.UploadPlugins:ADMINISTRATORS hudson.model.Item.Build:ADMINISTRATORS hudson.model.Item.Cancel:ADMINISTRATORS hudson.model.Item.Configure:ADMINISTRATORS hudson.model.Item.Create:ADMINISTRATORS hudson.model.Item.Delete:ADMINISTRATORS hudson.model.Item.Discover:ADMINISTRATORS hudson.model.Item.Read:ADMINISTRATORS hudson.model.Item.Workspace:ADMINISTRATORS hudson.model.Run.Delete:ADMINISTRATORS hudson.model.Run.Update:ADMINISTRATORS hudson.model.View.Configure:ADMINISTRATORS hudson.model.View.Create:ADMINISTRATORS hudson.model.View.Delete:ADMINISTRATORS hudson.model.View.Read:ADMINISTRATORS hudson.scm.SCM.Tag:ADMINISTRATORS com.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:INTEGRATORS com.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:INTEGRATORS com.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:INTEGRATORS hudson.model.Hudson.Read:INTEGRATORS hudson.model.Hudson.RunScripts:INTEGRATORS hudson.model.Item.Build:INTEGRATORS hudson.model.Item.Cancel:INTEGRATORS hudson.model.Item.Configure:INTEGRATORS hudson.model.Item.Create:INTEGRATORS hudson.model.Item.Delete:INTEGRATORS hudson.model.Item.Discover:INTEGRATORS hudson.model.Item.Read:INTEGRATORS hudson.model.Item.Workspace:INTEGRATORS hudson.model.Run.Delete:INTEGRATORS hudson.model.Run.Update:INTEGRATORS hudson.model.View.Configure:INTEGRATORS hudson.model.View.Create:INTEGRATORS hudson.model.View.Delete:INTEGRATORS hudson.model.View.Read:INTEGRATORS hudson.scm.SCM.Tag:INTEGRATORS Jenkins / JENKINS-33582 empty parser listbox in multi-branch project Change By: Philipp Moeller
