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

Task Reactor should require specifying a default attains()

      Surprisingly, Lib Task Reactor does not define the default attains. In Jenkins it means that some initialization tasks may be executed AFTER Jenkins switches to the COMPLETED initialization milestone. It was a root cause of SECURITY-667.

      IMHO we need to prevent it alltogether by hardening the default rules in the Task Reactor.

          [JENKINS-48728] Task Reactor should require specifying a default attains()

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Oleg Nenashev made changes -
          Link New: This issue is related to SECURITY-667 [ SECURITY-667 ]
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Summary Original: Task Reactor should allow specifying a default attains() New: Task Reactor should require specifying a default attains()
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]

            Unassigned Unassigned
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: