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

Configuration Job-Watching in jobA affects all of other job's Job-Watching

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • email-ext-plugin
    • None
    • Ubuntu 16.04.4
      OpenJDK 8u171-b11-0ubuntu0.16.04.1
      Jenkins core 2.107.3 | 2.46.2
      Email Extension 2.62 | 2.57.2

      Steps:
      1. Create 2 free-style jobs with "Watch Job" enabled:
      Test1 and Test2

      (To enable "Watch Job" you need to add "Editable Email Notification" step in Post-Build)

      2. Click "Watch Job" link to configure job watching for Test1 job
      and "SUBMIT" and the link becomes "Configure Job Watching"

      3. Open Test2 job and "Watch Job" link becomes "Configure Job Watching" too!

      4. Under "User > Configure > Extended Email Job Watching" setcion,
      it shows "No configuration available"
      ------------------------------
      At this point, only Test1 watch job email notification is really working
      ------------------------------

      5. Open Test2 job and click "Configure Job Watching" and "SUBMIT"
      ------------------------------
      Now both Test1 and Test2 watch job email notification is working.
      But job wtach configuration in one job affects configurations in other jobs,
      and "User > Configure > Extended Email Job Watching" setcion still shows "No configuration available".
      ------------------------------

      6. Open "Test1" job and stop job watching.
      ------------------------------
      This would stop all of job watching including "Test2".
      "Test2" job link becomes "Watch Job" and no more emails
      ------------------------------

        1. EditableEmailNotificationt.PNG
          EditableEmailNotificationt.PNG
          40 kB
        2. Selection_007.png
          Selection_007.png
          67 kB
        3. Selection_008.png
          Selection_008.png
          19 kB
        4. Selection_009.png
          Selection_009.png
          18 kB

          [JENKINS-52684] Configuration Job-Watching in jobA affects all of other job's Job-Watching

          Rick Liu added a comment -

          I can reproduce on:
          Jenkins core 2.107.3
          Email Extension 2.62
          and
          Jenkins core 2.46.2
          Email Extension 2.57.2

          Rick Liu added a comment - I can reproduce on: Jenkins core 2.107.3 Email Extension 2.62 and Jenkins core 2.46.2 Email Extension 2.57.2

          Daniel Gront added a comment -

          totoroliu, When I created a freestyle job there is no "Watch Job" option and I enabled "Enable watching for jobs" in global configuration.

          How can I reproduce this?

           

          Daniel Gront added a comment - totoroliu , When I created a freestyle job there is no "Watch Job" option and I enabled "Enable watching for jobs" in global configuration. How can I reproduce this?  

          Rick Liu added a comment -

          I believe you need to at least add "Editable Email Notification" step in Post-Build section.

          Rick Liu added a comment - I believe you need to at least add "Editable Email Notification" step in Post-Build section.

          Daniel Gront added a comment -

          Yeah, I've done that, It might be another issue that it doesn't appear. I'll try to look it up.

          Daniel Gront added a comment - Yeah, I've done that, It might be another issue that it doesn't appear. I'll try to look it up.

          Daniel Gront added a comment -

          totoroliu, I successfully reproduced it, it seems that you need to login in order to have this feature visible.

          Anyway as far as I can see all the design of this is flawed, the triggers are bound by the user and not by the job.

          I think it will require a redesign of the feature itself, which I lack the experience on how.

          If circumstances allow, davidvanlaatum could advise me on how to approach to it.

          Daniel Gront added a comment - totoroliu , I successfully reproduced it, it seems that you need to login in order to have this feature visible. Anyway as far as I can see all the design of this is flawed, the triggers are bound by the user and not by the job. I think it will require a redesign of the feature itself, which I lack the experience on how. If circumstances allow,  davidvanlaatum  could advise me on how to approach to it.

          Rick Liu added a comment -

          agree with you~

          Rick Liu added a comment - agree with you~

          Ben Portner added a comment -

          Any updates on this? I really like the idea of letting users subscribe to jobs. Unfortunately, this bug makes the feature completely useless.

          Ben Portner added a comment - Any updates on this? I really like the idea of letting users subscribe to jobs. Unfortunately, this bug makes the feature completely useless.

          Alex Earl added a comment -

          The fix for this has been merged, but unreleased

          Alex Earl added a comment - The fix for this has been merged, but unreleased

            Unassigned Unassigned
            totoroliu Rick Liu
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: