Hi Team,

      When saving configuration on jenkins job, some of fields are duplicates with default values.
      for example, git source code is duplicate with empty repository value and default branch (master)

      Also I saw a duplicate HTML reports publisher entries when we try to save the jenkins job.

      WARNING-  WARNING hudson.model.AbstractProject#submit: label assignment is using legacy '_.assignedLabelString'

      For example in below screenshot, before saving the job i only added 1 reports(2nd one in SS)
      but default one also coming when opening configuration.

          [JENKINS-67336] Default fields are coming after saving job

          vikas yadav created issue -
          vikas yadav made changes -
          Summary Original: Defauld fiels are coming after saving job New: Defauld fields are coming after saving job
          vikas yadav made changes -
          Description Original: Hi Team,

          When saving configuration on jenkins job, some of configuration are duplicates with default values.
          for example, git source code is duplicate with empty repository value and default branch (master)

          Also I saw a duplicate HTML reports publisher entries when we try to save the jenkins job.

          WARNING-  WARNING hudson.model.AbstractProject#submit: label assignment is using legacy '_.assignedLabelString'


          For example in below screenshot, before saving the job i only added 1 reports(2nd one in SS)
          but default one also coming when opening configuration.



          !image-2021-12-09-14-33-28-693.png!
          New: Hi Team,

          When saving configuration on jenkins job, some of fields are duplicates with default values.
           for example, git source code is duplicate with empty repository value and default branch (master)

          Also I saw a duplicate HTML reports publisher entries when we try to save the jenkins job.

          WARNING-  WARNING hudson.model.AbstractProject#submit: label assignment is using legacy '_.assignedLabelString'

          For example in below screenshot, before saving the job i only added 1 reports(2nd one in SS)
           but default one also coming when opening configuration.

          !image-2021-12-09-14-33-28-693.png!
          Summary Original: Defauld fields are coming after saving job New: Default fields are coming after saving job
          vikas yadav made changes -
          Priority Original: Minor [ 4 ] New: Blocker [ 1 ]
          Mark Waite made changes -
          Component/s Original: git-plugin [ 15543 ]
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]

          Mark Waite added a comment -

          vikas757 there is not enough information in the issue description to allow others to assist you. You reported duplication in two plugins, Git plugin and HTML publisher, but did not provide the version information of Jenkins or the plugins.

          If you're running an older plugin version with a newer Jenkins core, then you may have a plugin installed that has not yet been adapted for configuration form modernization ("tables to divs"). Configuration forms were modernized in Jenkins 2.277.1. If you're running current plugin versions, you may have a plugin installed that has a known issue with configuration form modernization.

          See the community article on configuration form modernization for a summary of the steps you should take.

          Mark Waite added a comment - vikas757 there is not enough information in the issue description to allow others to assist you. You reported duplication in two plugins, Git plugin and HTML publisher, but did not provide the version information of Jenkins or the plugins. If you're running an older plugin version with a newer Jenkins core, then you may have a plugin installed that has not yet been adapted for configuration form modernization ("tables to divs"). Configuration forms were modernized in Jenkins 2.277.1. If you're running current plugin versions, you may have a plugin installed that has a known issue with configuration form modernization. See the community article on configuration form modernization for a summary of the steps you should take.

            Unassigned Unassigned
            vikas757 vikas yadav
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: