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

Email-Ext groovy.template does show wrong changes

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: git-plugin, scm-api-plugin
    • Labels:
      None
    • Environment:
      master node ubunut x64
      slave node windows10 x64
    • Similar Issues:

      Description

      I use the groovy template from email-ext in a multibranch pipeline (blue ocean).
      However, for unknown reason the email contains in the changed section hundreds of files, which where not touched in the commit (they are all from the 3rdpart directory in the src repo) but totally unrelated to any changes.

        Attachments

        1. email-ext-changes.jpg
          email-ext-changes.jpg
          160 kB
        2. git_log.jpg
          git_log.jpg
          153 kB
        3. installed_plugins.txt
          8 kB
        4. my-html.template
          6 kB

          Activity

          Hide
          davidvanlaatum David van Laatum added a comment -

          This is not a problem with emailext it purely asks the SCM api for the list of changes.

          Show
          davidvanlaatum David van Laatum added a comment - This is not a problem with emailext it purely asks the SCM api for the list of changes.
          Hide
          zack Zack Snyder added a comment -

          Okay, maybe the API has changed and you have to use something different?
          Is there something I can do to fix it?

          Show
          zack Zack Snyder added a comment - Okay, maybe the API has changed and you have to use something different? Is there something I can do to fix it?
          Hide
          davidvanlaatum David van Laatum added a comment -

          what does the build page show for changes. If it doesn't agree with whats in the email then its a bug otherwise its either correct or a bug in the SCM api

          Show
          davidvanlaatum David van Laatum added a comment - what does the build page show for changes. If it doesn't agree with whats in the email then its a bug otherwise its either correct or a bug in the SCM api
          Hide
          zack Zack Snyder added a comment - - edited

          See the attached git log:

          It seems to be a bug in git SCM...

          PS: Can you change the assignee to the correct developer?

          Show
          zack Zack Snyder added a comment - - edited See the attached git log: It seems to be a bug in git SCM... PS: Can you change the assignee to the correct developer?
          Hide
          markewaite Mark Waite added a comment -

          Can you provide steps to duplicate the problem?

          Show
          markewaite Mark Waite added a comment - Can you provide steps to duplicate the problem?
          Hide
          zack Zack Snyder added a comment -

          Use jenkins, 2.107.2 and all the plugins I logged in the text file.
          Use the groocy HTML mail template for ext-mail.

          Create a repo and from this create a fork via bitbucket.
          Connect to bitbucket from jenkins via post webhook.
          Create a new branch and change something, push changes to origin and you will get the result I got.

          Show
          zack Zack Snyder added a comment - Use jenkins, 2.107.2 and all the plugins I logged in the text file. Use the groocy HTML mail template for ext-mail. Create a repo and from this create a fork via bitbucket. Connect to bitbucket from jenkins via post webhook. Create a new branch and change something, push changes to origin and you will get the result I got.
          Hide
          markewaite Mark Waite added a comment -

          Zack Snyder is it possible that your description of the steps to duplicate the problem are for a different bug report?

          This report says that the list of changes includes files which were not changed between the preceding build and the most recent build. Your description seems to have no preceding build, since a new job is created for the new branch, and the build of that new job will only include a single build. The single build will not show any changes, because there is no preceding build.

          Show
          markewaite Mark Waite added a comment - Zack Snyder is it possible that your description of the steps to duplicate the problem are for a different bug report? This report says that the list of changes includes files which were not changed between the preceding build and the most recent build. Your description seems to have no preceding build, since a new job is created for the new branch, and the build of that new job will only include a single build. The single build will not show any changes, because there is no preceding build.
          Hide
          zack Zack Snyder added a comment -

          Mark Waite
          You are right, when you perform the second build, you will get the mail with the wrong list of changes
          That you get no email for the first build was the other bug: JENKINS-51218

          Show
          zack Zack Snyder added a comment - Mark Waite You are right, when you perform the second build, you will get the mail with the wrong list of changes That you get no email for the first build was the other bug: JENKINS-51218

            People

            • Assignee:
              Unassigned
              Reporter:
              zack Zack Snyder
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: