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

"Team" name in plugin configuration sporadically defaults to "null", then auto-fills with the top-level team in the drop down

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • checkmarx-plugin
    • None

      "Team" name in plugin configuration sporadically defaults to "null", then auto-fills with the top-level team in the drop down after submitting the new configuration. 
      Nearly every time this happens, we have made NO config changes to the Checkmarx plugin area.

       

      Using Jog Config History, I'm including three sets of examples. The XML identifier is <groupId>. Notice how the value changes from "6efe....." to blank, then to "0076...." shortly after. The "6efe..." is our team name, and "0076..." is the top choice in the drop-down. I can't see any patterns. 

       

      This happens about 1 in 6 times that we make a job config change, and takes a while for us to notice the scans are going to a different Team. This doesn't happen for any other field in the plugin or in the main job. 

      Possible explanations:

      • the current config values aren't loading correctly for this field?
      • when the version of a different plugin updates, maybe it nulls that value and gets commited without knowing?

        1. 2021-06-10_075719.png
          98 kB
          Benjamin
        2. 2021-06-10_084552.png
          104 kB
          Benjamin
        3. 2021-07-01_155448.png
          109 kB
          Benjamin
        4. 2021-07-07_082038.png
          170 kB
          Benjamin
        5. 2021-08-16_093328.png
          171 kB
          Benjamin
        6. 2021-08-16_100023.png
          90 kB
          Benjamin

            sergeyk Sergey Kadaner
            benjiboy Benjamin
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: