Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33582

Empty warnings parser listbox in multi-branch project

      How to reproduce:
      1) Create a new multibranch project.
      2) Add some build steps
      3) Add a "Scan for compiler warnings" Post-Build action.
      4) Choose "Add" for "Scan workspace files"
      5) Choose a "File pattern"

      The "Parser" drop down box remain empty. There is no way to choose a parser.
      Leaving the Parser unconfigured end up in a build failure.

      Workaround: Configure Warnings Plugin in each branch project seperatly
      Cavats: Configuration on each brach project get lost on changes on the multi-branch project.

      Regards
      Bene

          [JENKINS-33582] Empty warnings parser listbox in multi-branch project

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          src/main/java/org/jenkinsci/test/acceptance/po/FreeStyleMultiBranchJob.java
          src/test/java/plugins/AbstractAnalysisTest.java
          src/test/java/plugins/WarningsPluginTest.java
          http://jenkins-ci.org/commit/acceptance-test-harness/cdf155f42d4b0da3d390974cc52b16804854de12
          Log:
          JENKINS-33582 Initial test case for multi-branch jobs.

          Use multi-branch freestyle jobs in conjunction with warnings plug-in.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/main/java/org/jenkinsci/test/acceptance/po/FreeStyleMultiBranchJob.java src/test/java/plugins/AbstractAnalysisTest.java src/test/java/plugins/WarningsPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/cdf155f42d4b0da3d390974cc52b16804854de12 Log: JENKINS-33582 Initial test case for multi-branch jobs. Use multi-branch freestyle jobs in conjunction with warnings plug-in.

          Ulli Hafner added a comment - - edited

          I can't reproduce this bug. I created a small test case in our ATH that successfully created a freestyle multi-branch project. I did not configure anything in the job, just three parsers. Can you try to reproduce this on a new clean Jenkins installation with just the 2 plug-ins installed? Or can you add more details on your job configuration?

          Or Matthew, can you reproduce this bug?

          Ulli Hafner added a comment - - edited I can't reproduce this bug. I created a small test case in our ATH that successfully created a freestyle multi-branch project. I did not configure anything in the job, just three parsers. Can you try to reproduce this on a new clean Jenkins installation with just the 2 plug-ins installed? Or can you add more details on your job configuration? Or Matthew, can you reproduce this bug?

          I repeated the test:

          1) fresh jenkins install (1.653)
          2) install "Multi-Branch Project Plugin"
          3) "Warnings Plug-in" with jenkins restart
          4) "create new job" and choose "Freestyle multi-branch project"
          5) "Add post-build action" -> "Scan for compiler warnings"
          6) Add "Scan workspace files"
          Everything OK. I can choose a Parser.

          After that I did an update (1.652 -> 1.653) of my productional jenkins instance but with no luck.
          The problem remains. Dig deeper into it. For now I close the issue, since it is obvious buried
          in my productive installation/configuration.

          Thx for your help.
          Bene

          Benedikt Spranger added a comment - I repeated the test: 1) fresh jenkins install (1.653) 2) install "Multi-Branch Project Plugin" 3) "Warnings Plug-in" with jenkins restart 4) "create new job" and choose "Freestyle multi-branch project" 5) "Add post-build action" -> "Scan for compiler warnings" 6) Add "Scan workspace files" Everything OK. I can choose a Parser. After that I did an update (1.652 -> 1.653) of my productional jenkins instance but with no luck. The problem remains. Dig deeper into it. For now I close the issue, since it is obvious buried in my productive installation/configuration. Thx for your help. Bene

          Close this issue, since it is obvious buried in my configuration/installation.

          Thx for your help.

          Benedikt Spranger added a comment - Close this issue, since it is obvious buried in my configuration/installation. Thx for your help.

          Philipp Moeller added a comment - - edited

          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.

          I attach a shortened version of our authorization matrix, but I have not verified that this shortened version can reproduce the problem.

          <authorizationStrategy class="hudson.security.ProjectMatrixAuthorizationStrategy">
          <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Create:ADMINISTRATORS</permission>
          <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Delete:ADMINISTRATORS</permission>
          <permission>com.cloudbees.plugins.credentials.CredentialsProvider.ManageDomains:ADMINISTRATORS</permission>
          <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Update:ADMINISTRATORS</permission>
          <permission>com.cloudbees.plugins.credentials.CredentialsProvider.View:ADMINISTRATORS</permission>
          <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:ADMINISTRATORS</permission>
          <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:ADMINISTRATORS</permission>
          <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:ADMINISTRATORS</permission>
          <permission>hudson.model.Computer.Build:ADMINISTRATORS</permission>
          <permission>hudson.model.Computer.Configure:ADMINISTRATORS</permission>
          <permission>hudson.model.Computer.Connect:ADMINISTRATORS</permission>
          <permission>hudson.model.Computer.Create:ADMINISTRATORS</permission>
          <permission>hudson.model.Computer.Delete:ADMINISTRATORS</permission>
          <permission>hudson.model.Computer.Disconnect:ADMINISTRATORS</permission>
          <permission>hudson.model.Hudson.Administer:ADMINISTRATORS</permission>
          <permission>hudson.model.Hudson.ConfigureUpdateCenter:ADMINISTRATORS</permission>
          <permission>hudson.model.Hudson.Read:ADMINISTRATORS</permission>
          <permission>hudson.model.Hudson.RunScripts:ADMINISTRATORS</permission>
          <permission>hudson.model.Hudson.UploadPlugins:ADMINISTRATORS</permission>
          <permission>hudson.model.Item.Build:ADMINISTRATORS</permission>
          <permission>hudson.model.Item.Cancel:ADMINISTRATORS</permission>
          <permission>hudson.model.Item.Configure:ADMINISTRATORS</permission>
          <permission>hudson.model.Item.Create:ADMINISTRATORS</permission>
          <permission>hudson.model.Item.Delete:ADMINISTRATORS</permission>
          <permission>hudson.model.Item.Discover:ADMINISTRATORS</permission>
          <permission>hudson.model.Item.Read:ADMINISTRATORS</permission>
          <permission>hudson.model.Item.Workspace:ADMINISTRATORS</permission>
          <permission>hudson.model.Run.Delete:ADMINISTRATORS</permission>
          <permission>hudson.model.Run.Update:ADMINISTRATORS</permission>
          <permission>hudson.model.View.Configure:ADMINISTRATORS</permission>
          <permission>hudson.model.View.Create:ADMINISTRATORS</permission>
          <permission>hudson.model.View.Delete:ADMINISTRATORS</permission>
          <permission>hudson.model.View.Read:ADMINISTRATORS</permission>
          <permission>hudson.scm.SCM.Tag:ADMINISTRATORS</permission>
          <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:INTEGRATORS</permission>
          <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:INTEGRATORS</permission>
          <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:INTEGRATORS</permission>
          <permission>hudson.model.Hudson.Read:INTEGRATORS</permission>
          <permission>hudson.model.Hudson.RunScripts:INTEGRATORS</permission>
          <permission>hudson.model.Item.Build:INTEGRATORS</permission>
          <permission>hudson.model.Item.Cancel:INTEGRATORS</permission>
          <permission>hudson.model.Item.Configure:INTEGRATORS</permission>
          <permission>hudson.model.Item.Create:INTEGRATORS</permission>
          <permission>hudson.model.Item.Delete:INTEGRATORS</permission>
          <permission>hudson.model.Item.Discover:INTEGRATORS</permission>
          <permission>hudson.model.Item.Read:INTEGRATORS</permission>
          <permission>hudson.model.Item.Workspace:INTEGRATORS</permission>
          <permission>hudson.model.Run.Delete:INTEGRATORS</permission>
          <permission>hudson.model.Run.Update:INTEGRATORS</permission>
          <permission>hudson.model.View.Configure:INTEGRATORS</permission>
          <permission>hudson.model.View.Create:INTEGRATORS</permission>
          <permission>hudson.model.View.Delete:INTEGRATORS</permission>
          <permission>hudson.model.View.Read:INTEGRATORS</permission>
          <permission>hudson.scm.SCM.Tag:INTEGRATORS</permission>
          </authorizationStrategy>

          Philipp Moeller added a comment - - edited 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. I attach a shortened version of our authorization matrix, but I have not verified that this shortened version can reproduce the problem. <authorizationStrategy class="hudson.security.ProjectMatrixAuthorizationStrategy"> <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Create:ADMINISTRATORS</permission> <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Delete:ADMINISTRATORS</permission> <permission>com.cloudbees.plugins.credentials.CredentialsProvider.ManageDomains:ADMINISTRATORS</permission> <permission>com.cloudbees.plugins.credentials.CredentialsProvider.Update:ADMINISTRATORS</permission> <permission>com.cloudbees.plugins.credentials.CredentialsProvider.View:ADMINISTRATORS</permission> <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:ADMINISTRATORS</permission> <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:ADMINISTRATORS</permission> <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:ADMINISTRATORS</permission> <permission>hudson.model.Computer.Build:ADMINISTRATORS</permission> <permission>hudson.model.Computer.Configure:ADMINISTRATORS</permission> <permission>hudson.model.Computer.Connect:ADMINISTRATORS</permission> <permission>hudson.model.Computer.Create:ADMINISTRATORS</permission> <permission>hudson.model.Computer.Delete:ADMINISTRATORS</permission> <permission>hudson.model.Computer.Disconnect:ADMINISTRATORS</permission> <permission>hudson.model.Hudson.Administer:ADMINISTRATORS</permission> <permission>hudson.model.Hudson.ConfigureUpdateCenter:ADMINISTRATORS</permission> <permission>hudson.model.Hudson.Read:ADMINISTRATORS</permission> <permission>hudson.model.Hudson.RunScripts:ADMINISTRATORS</permission> <permission>hudson.model.Hudson.UploadPlugins:ADMINISTRATORS</permission> <permission>hudson.model.Item.Build:ADMINISTRATORS</permission> <permission>hudson.model.Item.Cancel:ADMINISTRATORS</permission> <permission>hudson.model.Item.Configure:ADMINISTRATORS</permission> <permission>hudson.model.Item.Create:ADMINISTRATORS</permission> <permission>hudson.model.Item.Delete:ADMINISTRATORS</permission> <permission>hudson.model.Item.Discover:ADMINISTRATORS</permission> <permission>hudson.model.Item.Read:ADMINISTRATORS</permission> <permission>hudson.model.Item.Workspace:ADMINISTRATORS</permission> <permission>hudson.model.Run.Delete:ADMINISTRATORS</permission> <permission>hudson.model.Run.Update:ADMINISTRATORS</permission> <permission>hudson.model.View.Configure:ADMINISTRATORS</permission> <permission>hudson.model.View.Create:ADMINISTRATORS</permission> <permission>hudson.model.View.Delete:ADMINISTRATORS</permission> <permission>hudson.model.View.Read:ADMINISTRATORS</permission> <permission>hudson.scm.SCM.Tag:ADMINISTRATORS</permission> <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.RemoveCause:INTEGRATORS</permission> <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.UpdateCauses:INTEGRATORS</permission> <permission>com.sonyericsson.jenkins.plugins.bfa.PluginImpl.ViewCauses:INTEGRATORS</permission> <permission>hudson.model.Hudson.Read:INTEGRATORS</permission> <permission>hudson.model.Hudson.RunScripts:INTEGRATORS</permission> <permission>hudson.model.Item.Build:INTEGRATORS</permission> <permission>hudson.model.Item.Cancel:INTEGRATORS</permission> <permission>hudson.model.Item.Configure:INTEGRATORS</permission> <permission>hudson.model.Item.Create:INTEGRATORS</permission> <permission>hudson.model.Item.Delete:INTEGRATORS</permission> <permission>hudson.model.Item.Discover:INTEGRATORS</permission> <permission>hudson.model.Item.Read:INTEGRATORS</permission> <permission>hudson.model.Item.Workspace:INTEGRATORS</permission> <permission>hudson.model.Run.Delete:INTEGRATORS</permission> <permission>hudson.model.Run.Update:INTEGRATORS</permission> <permission>hudson.model.View.Configure:INTEGRATORS</permission> <permission>hudson.model.View.Create:INTEGRATORS</permission> <permission>hudson.model.View.Delete:INTEGRATORS</permission> <permission>hudson.model.View.Read:INTEGRATORS</permission> <permission>hudson.scm.SCM.Tag:INTEGRATORS</permission> </authorizationStrategy>

          I just tested this with the following environment:

          • Jenkins 1.625.1
          • Warnings Plugin 4.56
          • Multi-Branch Project Plugin 0.5.1
          • Branch API Plugin 1.10
          • Folders Plugin 5.12

          Looks fine to me. Assuming it got fixed somewhere along the line, so closing as can't reproduce

          Matthew DeTullio added a comment - I just tested this with the following environment: Jenkins 1.625.1 Warnings Plugin 4.56 Multi-Branch Project Plugin 0.5.1 Branch API Plugin 1.10 Folders Plugin 5.12 Looks fine to me. Assuming it got fixed somewhere along the line, so closing as can't reproduce

            mjdetullio Matthew DeTullio
            bene42 Benedikt Spranger
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: