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

Getting an old email notification everyday (of the same old build # of Jenkins pipeline job)

XMLWordPrintable

      We are regularly getting proper results daily but along with the actual report we are getting a duplicate mail (email report of 9th march 2023) daily. Even after deleting the 9th march 2023 build from the parallel pipeline job, we are still getting the report for it.

      We are facing this issue from last march 9th onwards in Jenkins 2.375.1 pipeline job.

          [JENKINS-70873] Getting an old email notification everyday (of the same old build # of Jenkins pipeline job)

          Mark Waite added a comment - - edited

          The initial information included in this report looks like a request for help diagnosing a configuration issue rather than a bug report.  If you believe this is a bug, please provide all the details requested in "How to report an issue".  That includes:

          • Detailed list of plugins and their specific versions as output from the script console 
          • Steps that will allow another person to duplicate the problem from a fresh Jenkins installation
          • Many more items that are listed in that page

          If you're requesting help to diagnose a configuration issue, you'll almost always have better results by asking in https://community.jenkins.io or in the Jenkins chat channels. More people read those locations than read bug reports.

          Mark Waite added a comment - - edited The initial information included in this report looks like a request for help diagnosing a configuration issue rather than a bug report.  If you believe this is a bug, please provide all the details requested in "How to report an issue" .  That includes: Detailed list of plugins and their specific versions as output from the script console   Steps that will allow another person to duplicate the problem from a fresh Jenkins installation Many more items that are listed in that page If you're requesting help to diagnose a configuration issue, you'll almost always have better results by asking in https://community.jenkins.io or in the Jenkins chat channels. More people read those locations than read bug reports.

          Mark Waite added a comment -

          Not enough information in the initial report and no response to the request for more information

          Mark Waite added a comment - Not enough information in the initial report and no response to the request for more information

            Unassigned Unassigned
            sivasankaranjen Siva
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: