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

new default view in a job folder deletes all config files

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • config-file-provider-plugin
    • None
    • Jenkins ver. 2.32.3
       config-file-provider-plugin 2.16.0

      When setting a new default view in a folder, already existing config files get deleted

      Steps to reproduce:

      1. create a folder
      2. create a config file 'some config'
      3. create job 'test1'
      4. create job 'test2'
      5. create a new view 'test2 only' and assign job test2
      6. edit the folder and set 'test2 only' as default view

      Expected result:

      default view is changed, all configuration files still exist in all views

      Actual result:

      default view changed, all configuration files deleted

      Also switching back the default view does not recover the deleted configuration files

       

      There is a issue, which should be fixed in 2.15.7 by imod:

      https://issues.jenkins-ci.org/browse/JENKINS-42389

          [JENKINS-46874] new default view in a job folder deletes all config files

          Dominik Bartholdi added a comment -

          as you noted, there is a newer version of the config-file-provider plugin - please first try to reproduce the issue with this version

          Dominik Bartholdi added a comment - as you noted, there is a newer version of the config-file-provider plugin - please first try to reproduce the issue with this version

          Josef Rosel added a comment -

          I can do this in the next maintainance window.

          But it should be fixed in 2.15.7, am I correct on this assumption?

          Josef Rosel added a comment - I can do this in the next maintainance window. But it should be fixed in 2.15.7, am I correct on this assumption?

          Dominik Bartholdi added a comment -

          yes - in general, before opening a bug, you should check whether a never version fixes the issue already

          Dominik Bartholdi added a comment - yes - in general, before opening a bug, you should check whether a never version fixes the issue already

            domi Dominik Bartholdi
            josefrosel Josef Rosel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: