• Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • core
    • None
    • Windows 10

      This started in version 2.277.3.  When I use the UI to edit anything in the parameterized data, I lose the entire section of the config.xml file.

          [JENKINS-65544] Losing all parameterized data

          Mark Waite added a comment -

          jyoungman please provide more details about the failure you're seeing and the conditions surrounding the failure. Two sentences do not provide enough information for others to assist you.

          You've provided a very brief description of what you're seeing but no description of the context around the issue, the things you've investigated, or the things that you've discovered while exploring the issue.

          In an open source community (even more than in a business), an issue report needs to be more filled with insights about your exploration rather than containing a single "photograph" of the current state. An issue report that is processed by volunteers (like most open source projects) needs to contain enough information that those volunteers find enough motivation in the description to provide assistance. Many volunteers want their donated time to help as broadly as possible. Your description is not enough that anyone else can assist you.

          Some things that might inspire others to want to assist:

          • Describe the last version that worked (assumed to be before 2.277.1)
          • List the plugin names and versions installed (see "How to report an issue")
          • Upload the job definition that fails to save parameterized data
          • Confirm that you've performed the steps described in the Jenkins 2.277.1 upgrade guide and in the Jenkins 2.277.1 upgrade webinar
          • Describe the experiments you've tried and their results

          Frequently, collecting that information will discover a solution to the problem faster than posting an incomplete issue report and hoping someone will help you.

          Mark Waite added a comment - jyoungman please provide more details about the failure you're seeing and the conditions surrounding the failure. Two sentences do not provide enough information for others to assist you. You've provided a very brief description of what you're seeing but no description of the context around the issue, the things you've investigated, or the things that you've discovered while exploring the issue. In an open source community (even more than in a business), an issue report needs to be more filled with insights about your exploration rather than containing a single "photograph" of the current state. An issue report that is processed by volunteers (like most open source projects) needs to contain enough information that those volunteers find enough motivation in the description to provide assistance. Many volunteers want their donated time to help as broadly as possible. Your description is not enough that anyone else can assist you. Some things that might inspire others to want to assist: Describe the last version that worked (assumed to be before 2.277.1) List the plugin names and versions installed (see "How to report an issue" ) Upload the job definition that fails to save parameterized data Confirm that you've performed the steps described in the Jenkins 2.277.1 upgrade guide and in the Jenkins 2.277.1 upgrade webinar Describe the experiments you've tried and their results Frequently, collecting that information will discover a solution to the problem faster than posting an incomplete issue report and hoping someone will help you.

          James added a comment -

          i had a job with 6 parameters.  I used the UI to delete 1 param.  After clcking save, the job had "Build Now".  I compared the config.xml to a backup copy and the entire section of parameterized data was gone.  This happened several times.  It is not a fluke.  What more do you need?

          James added a comment - i had a job with 6 parameters.  I used the UI to delete 1 param.  After clcking save, the job had "Build Now".  I compared the config.xml to a backup copy and the entire section of parameterized data was gone.  This happened several times.  It is not a fluke.  What more do you need?

          Mark Waite added a comment - - edited

          I am unable to duplicate the issue as you described it. I made the following guesses based on the information you provided:

          • Using the precise Jenkins plugins and versions as described in my repository (you should provide a similar list by following the instructions at "What information to provide for environment and description")
          • Created a freestyle project named JENKINS-65544-six-parameters with 6 parameters, BOOLEAN_PARAM_1 (default 'True'), LABEL_PARAM_2 (default 'amd64'), STRING_PARAM_3 (default value 'a-string'), CREDENTIAL_PARAM_4 (default value 'mark-pc3 ed25519 private key'), BOOLEAN_PARAM_5 (default 'False'), and BOOLEAN_PARAM_6 (default 'True')
          • Saved the freestyle project
          • Ran the freestyle project
          • Modified the freestyle project to delete a parameter and saved it
          • Ran the freestyle project again
          • Modified the freestyle project to change a parameter and saved it again
          • Ran the freestyle project again

          Your job configuration might be failing to save because you have plugins installed that do not support the changes made in Jenkins 2.277.1 for configuration form modernization. Refer to the Jenkins 2.277.1 changelog, Jenkins 2.277.1 upgrade guide, and the Jenkins 2.277.1 webinar for more details.

          Mark Waite added a comment - - edited I am unable to duplicate the issue as you described it. I made the following guesses based on the information you provided: Using the precise Jenkins plugins and versions as described in my repository (you should provide a similar list by following the instructions at "What information to provide for environment and description" ) Created a freestyle project named JENKINS-65544-six-parameters with 6 parameters, BOOLEAN_PARAM_1 (default 'True'), LABEL_PARAM_2 (default 'amd64'), STRING_PARAM_3 (default value 'a-string'), CREDENTIAL_PARAM_4 (default value 'mark-pc3 ed25519 private key'), BOOLEAN_PARAM_5 (default 'False'), and BOOLEAN_PARAM_6 (default 'True') Saved the freestyle project Ran the freestyle project Modified the freestyle project to delete a parameter and saved it Ran the freestyle project again Modified the freestyle project to change a parameter and saved it again Ran the freestyle project again Your job configuration might be failing to save because you have plugins installed that do not support the changes made in Jenkins 2.277.1 for configuration form modernization. Refer to the Jenkins 2.277.1 changelog, Jenkins 2.277.1 upgrade guide, and the Jenkins 2.277.1 webinar for more details.

          Mark Waite added a comment -

          Closing as "Cannot reproduce". If sufficiently detailed configuration information is provided so that the problem can be duplicated, then the issue can be reopened.

          Mark Waite added a comment - Closing as "Cannot reproduce". If sufficiently detailed configuration information is provided so that the problem can be duplicated, then the issue can be reopened.

            Unassigned Unassigned
            jyoungman James
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: