• Bundles management UI

      The Support core plugins automatically creates a bundle when the instance starts and after every hour.
      These bundles are directly stored under JENKINS_HOME/support but the user have to access to the Jenkins server FS to manage them.
      We would like to add the following features :

      • List bundles stored on the instance (name + creation date + size)
      • Allow to download each bundle
      • Allow to delete each bundle or all bundles
      • Allow to browse the content of each bundle

          [JENKINS-33090] Ease bundles management by the administrator

          Also it will very interesting the ability to automatically delete all support bundles older than X days.

          Ivan Fernandez Calvo added a comment - Also it will very interesting the ability to automatically delete all support bundles older than X days.

          yes good idea. If we have enough time we'll see if we can propose it

          Arnaud Héritier added a comment - yes good idea. If we have enough time we'll see if we can propose it

          +1
          I hope there will be enough time for this implementation. If not, we can add this feature after the gsoc period.

          Minudika Malshan added a comment - +1 I hope there will be enough time for this implementation. If not, we can add this feature after the gsoc period.

          yes sure minudika
          I need to check with rtyler if we can activate sub-tasks in Jira (he told me why they weren't but I don't remember - crappy brain).
          If we have subtasks we can easily split the work of such big tasks into subtasks with few optional ones and if we don't process them we'll just convert them as new tasks for a future fix

          Arnaud Héritier added a comment - yes sure minudika I need to check with rtyler if we can activate sub-tasks in Jira (he told me why they weren't but I don't remember - crappy brain). If we have subtasks we can easily split the work of such big tasks into subtasks with few optional ones and if we don't process them we'll just convert them as new tasks for a future fix

          R. Tyler Croy added a comment -

          aheritier we do have Epics in JIRA, which I personally fine more useful than tasks/sub-tasks since JIRA workflows usually don't play nicely with sub-tasks in my experience.

          They're enable-able, but if this can be accomplished with Epics and Issues then that would be preferred since it's already present.

          R. Tyler Croy added a comment - aheritier we do have Epics in JIRA, which I personally fine more useful than tasks/sub-tasks since JIRA workflows usually don't play nicely with sub-tasks in my experience. They're enable-able, but if this can be accomplished with Epics and Issues then that would be preferred since it's already present.

          ok I didn't remember that we had agile epics here thus it's good. I can convert this one to Epic and create others tasks to attach to the epic.
          I'll do this later. It's perfect

          Arnaud Héritier added a comment - ok I didn't remember that we had agile epics here thus it's good. I can convert this one to Epic and create others tasks to attach to the epic. I'll do this later. It's perfect

          Jesse Glick added a comment -

          A Story plus Tasks would be more appropriate for this sort of thing.

          Jesse Glick added a comment - A Story plus Tasks would be more appropriate for this sort of thing.

          jglick sub-tasks aren't activated on this instance. That's why I used Epic + Tasks..

          Arnaud Héritier added a comment - jglick sub-tasks aren't activated on this instance. That's why I used Epic + Tasks..

            allan_burdajewicz Allan BURDAJEWICZ
            aheritier Arnaud Héritier
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: