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

Make Docker Traceability tolerant against FingerprintCleanupThread

XMLWordPrintable

      FingerprintCleanupThread may delete fingerprints if there is no references to jobs.

      • [DECLINED] For old cores it is required to create an artificial project, which would reference builds on-demand. Such project would also allow to manage fingerprints from its interface.
      • We should add an extension point, which would allow to prohibit the Fingerprint deletion

      Old discussion summary:

      • Container fingerprints are not protected from fingerprint cleanup by the core due to the missing build references
      • I've never seen the Traceability fingerprints cleanup, but it may happen according to the Jenkins core code
      • FingerprintsCleanupThread should run randomly with one day interval according to the code

          [JENKINS-28655] Make Docker Traceability tolerant against FingerprintCleanupThread

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "docker-traceability-plugin/pull/5 (Web Link)" [ 12925 ]
          Oleg Nenashev made changes -
          Description Original: FingerprintCleanupThread may delete fingerprints if there is no references to jobs. For old cores it is required to create an artificial project, which would reference builds on-demand. Such project would also allow to manage fingerprints from its interface. New: FingerprintCleanupThread may delete fingerprints if there is no references to jobs.

          * [DECLINED] For old cores it is required to create an artificial project, which would reference builds on-demand. Such project would also allow to manage fingerprints from its interface.
          *
          Oleg Nenashev made changes -
          Description Original: FingerprintCleanupThread may delete fingerprints if there is no references to jobs.

          * [DECLINED] For old cores it is required to create an artificial project, which would reference builds on-demand. Such project would also allow to manage fingerprints from its interface.
          *
          		New: FingerprintCleanupThread may delete fingerprints if there is no references to jobs.

          * [DECLINED] For old cores it is required to create an artificial project, which would reference builds on-demand. Such project would also allow to manage fingerprints from its interface.
          * We should add an extension point, which would allow to prohibit the Fingerprint deletion
          Oleg Nenashev made changes -
          Description Original: FingerprintCleanupThread may delete fingerprints if there is no references to jobs.

          * [DECLINED] For old cores it is required to create an artificial project, which would reference builds on-demand. Such project would also allow to manage fingerprints from its interface.
          * We should add an extension point, which would allow to prohibit the Fingerprint deletion
          		 New: FingerprintCleanupThread may delete fingerprints if there is no references to jobs.

          * [DECLINED] For old cores it is required to create an artificial project, which would reference builds on-demand. Such project would also allow to manage fingerprints from its interface.
          * We should add an extension point, which would allow to prohibit the Fingerprint deletion

          Old discussion summary:
          {quote}
          * Container fingerprints are not protected from fingerprint cleanup by the core due to the missing build references
          * I've never seen the Traceability fingerprints cleanup, but it may happen according to the Jenkins core code
          * FingerprintsCleanupThread should run randomly with one day interval according to the code
          {quote}
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 163508 ] New: JNJira + In-Review [ 185605 ]
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          Oleg Nenashev made changes -
          Assignee New: Alex Taylor [ ataylor ]

            ataylor Alex Taylor
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: