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

Adopting "push" rather than "pull" model for claim

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • claim-plugin
    • None

    Description

      The current claim model adopts pull model, in the sense that it relies on someone to claim the failed build. This requires a proactive team member to work well.

      a suggestion is to support "push" model, so that when a build fails it is automatically assigned to a default assignee, which shall be visible on the dashboard, then he/she will be urged to assign it to the real owner, which will then be urged to fix it ASAP.

      In case the owner made the fix in his code, but the problem persist due to another owner code dependency for example, he/she can reassign it to the designated owner, until the build succeed.

      This makes it sort of "Blame" instead of "Claim". Another feature request was opened before this one (JENKINS-5308) but then I was redirected to Claim.

      Please let me know whether this is possible to handle in the current plugin, or should it be a separate one.

      Attachments

        Issue Links

          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-5308 HotPotato plugin: a new plugin to help organize fixing failed hudson builds involving multiple developers

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            nikitad nikitad added a comment - - edited

            The patch in JENKINS-7824 has some of the functionality requested in this ticket.

            nikitad nikitad added a comment - - edited The patch in JENKINS-7824 has some of the functionality requested in this ticket.
            drekbour Marc Carter added a comment -

            JENKINS-7824 (claim assignment) is a good idea and I will implement that.

            Not a fan of this though.
            I think Claim should remain a human action as anything else devalues it. I feel that many developers would simply ignore "claims" if they are systematic for this reason. Crucially, auto-assigning to a poor tech-lead means he cannot differentiate real Claims from the noise of failed builds.

            Lastly, with a good dashboard, claimed failures are clearly distinguished from unclaimed failures so the cue for aforementioned tech-lead to "assign" the failure is there already. See https://github.com/jan-molak/jenkins-build-monitor-plugin

            drekbour Marc Carter added a comment - JENKINS-7824 (claim assignment) is a good idea and I will implement that. Not a fan of this though. I think Claim should remain a human action as anything else devalues it. I feel that many developers would simply ignore "claims" if they are systematic for this reason. Crucially, auto-assigning to a poor tech-lead means he cannot differentiate real Claims from the noise of failed builds. Lastly, with a good dashboard, claimed failures are clearly distinguished from unclaimed failures so the cue for aforementioned tech-lead to "assign" the failure is there already. See https://github.com/jan-molak/jenkins-build-monitor-plugin
            rggjan rggjan added a comment -

            @Marc: We have the following model: Every morning in daily scrum we look at jenkins, check the broken jobs and assign them to people. However, this is not possible to do with the claim plugin, since you would have to log out and log in all the time.

            In this case, I think a push model would be nice, so that one person can assign whoever volunteers to fix on jenkins... what do you think?

            rggjan rggjan added a comment - @Marc: We have the following model: Every morning in daily scrum we look at jenkins, check the broken jobs and assign them to people. However, this is not possible to do with the claim plugin, since you would have to log out and log in all the time. In this case, I think a push model would be nice, so that one person can assign whoever volunteers to fix on jenkins... what do you think?
            drekbour Marc Carter added a comment -

            @rggjan
            What you want is JENKINS-7824 which covers "assigning" claims to others (aka Blame). Vote/Watch that jira.

            I know this Jira predates it by a year, but assuming 7824 is implemented, then all that remains of this request is auto-assigning claims which I personally don't see adding value.

            drekbour Marc Carter added a comment - @rggjan What you want is JENKINS-7824 which covers "assigning" claims to others (aka Blame). Vote/Watch that jira. I know this Jira predates it by a year, but assuming 7824 is implemented, then all that remains of this request is auto-assigning claims which I personally don't see adding value.
            rggjan rggjan added a comment -

            Ah, you're right! 7824 is what I was thinking of... thanks for the correction

            rggjan rggjan added a comment - Ah, you're right! 7824 is what I was thinking of... thanks for the correction
            oleg_nenashev Oleg Nenashev added a comment -

            @Marc
            Seems that issue could be closed with the "won't fix" status

            oleg_nenashev Oleg Nenashev added a comment - @Marc Seems that issue could be closed with the "won't fix" status

            People

              Unassigned Unassigned
              mgalal mgalal
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: