• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • OS: RHEL 6
      Jenkins: 2.93
      ThinBackup: 1.9

      After upgrading to Jenkins 2.93, ThinBackup sets the permissions of installedPlugins.xml to 600.  Previously, the permission were 644, matching the original file.

      If I watch the permissions as a backup is running, the permissions start as 644, but change to 600 by the time the backup completes.

      The dnusbaum user on IRC recommended I create this issue. 

      EDIT: This issue was discovered when automation attempts to copy the backups files off of the server as non jenkins user. I assume since the permissions of the backups are different than JENKINS_HOME, that restoring would fail. I have not had a chance to test this theory.

          [JENKINS-48407] Permission issue after upgrade to 2.93

          b harper created issue -
          Devin Nusbaum made changes -
          Link New: This issue relates to JENKINS-36088 [ JENKINS-36088 ]
          b harper made changes -
          Description Original: After upgrading to Jenkins 2.93, ThinBackup sets the permissions of installedPlugins.xml to 600.  Previously, the permission were 644, matching the original file.

          If I watch the permissions as a backup is running, the permissions start as 644, but change to 600 by the time the backup completes.

          The dnusbaum user on IRC recommended I create this issue. 
          New: After upgrading to Jenkins 2.93, ThinBackup sets the permissions of installedPlugins.xml to 600.  Previously, the permission were 644, matching the original file.

          If I watch the permissions as a backup is running, the permissions start as 644, but change to 600 by the time the backup completes.

          The dnusbaum user on IRC recommended I create this issue. 

          This issue was discovered when automation attempts to copy the backups files off the server as non jenkins user. I assume since the permissions of the
          b harper made changes -
          Description Original: After upgrading to Jenkins 2.93, ThinBackup sets the permissions of installedPlugins.xml to 600.  Previously, the permission were 644, matching the original file.

          If I watch the permissions as a backup is running, the permissions start as 644, but change to 600 by the time the backup completes.

          The dnusbaum user on IRC recommended I create this issue. 

          This issue was discovered when automation attempts to copy the backups files off the server as non jenkins user. I assume since the permissions of the
          New: After upgrading to Jenkins 2.93, ThinBackup sets the permissions of installedPlugins.xml to 600.  Previously, the permission were 644, matching the original file.

          If I watch the permissions as a backup is running, the permissions start as 644, but change to 600 by the time the backup completes.

          The dnusbaum user on IRC recommended I create this issue. 

          This issue was discovered when automation attempts to copy the backups files off the server as non jenkins user. I assume since the permissions of the backups are different than
          b harper made changes -
          Description Original: After upgrading to Jenkins 2.93, ThinBackup sets the permissions of installedPlugins.xml to 600.  Previously, the permission were 644, matching the original file.

          If I watch the permissions as a backup is running, the permissions start as 644, but change to 600 by the time the backup completes.

          The dnusbaum user on IRC recommended I create this issue. 

          This issue was discovered when automation attempts to copy the backups files off the server as non jenkins user. I assume since the permissions of the backups are different than
          New: After upgrading to Jenkins 2.93, ThinBackup sets the permissions of installedPlugins.xml to 600.  Previously, the permission were 644, matching the original file.

          If I watch the permissions as a backup is running, the permissions start as 644, but change to 600 by the time the backup completes.

          The dnusbaum user on IRC recommended I create this issue. 

          EDIT: This issue was discovered when automation attempts to copy the backups files off of the server as non jenkins user. I assume since the permissions of the backups are different than JENKINS_HOME, that restoring would fail. I have not had a chance to test this theory.
          Devin Nusbaum made changes -
          Link New: This issue relates to JENKINS-34855 [ JENKINS-34855 ]
          Devin Nusbaum made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: thinbackup-plugin [ 15780 ]
          Baptiste Mathus made changes -
          Assignee Original: Thomas Fürer [ tofuatjava ] New: Baptiste Mathus [ batmat ]
          Baptiste Mathus made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Baptiste Mathus made changes -
          Summary Original: ThinBackup permision issue after upgrade to 2.93 New: Permision issue after upgrade to 2.93
          Baptiste Mathus made changes -
          Summary Original: Permision issue after upgrade to 2.93 New: Permission issue after upgrade to 2.93

            batmat Baptiste Mathus
            bharper b harper
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: