Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 561609

Summary: [JIRO] Send properly formatted mail from JIRO instance
Product: [Eclipse Project] Platform Reporter: Sravan Kumar Lakkimsetti <sravankumarl>
Component: RelengAssignee: Platform-Releng-Inbox <platform-releng-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: akurtakov, akurtakov, daniel_megert
Version: 4.15   
Target Milestone: ---   
Hardware: PC   
OS: Windows 10   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=562042
https://bugs.eclipse.org/bugs/show_bug.cgi?id=562087
Whiteboard:

Description Sravan Kumar Lakkimsetti CLA 2020-03-31 06:49:54 EDT
There are multiple issues in this. A mail needs to be sent at the end of build and end of each test run

We are currently getting mail as follows at the end of build

Eclipse downloads: https://download.eclipse.org/eclipse/downloads/drops4/I20200330-1800 / Build logs and/or test results (eventually): https://download.eclipse.org/eclipse/downloads/drops4/I20200330-1800 /testResults.php

here is the expected format
Eclipse downloads:
   https://download.eclipse.org/eclipse/downloads/drops4/I20200310-1800/

   Build logs and/or test results (eventually):
      https://download.eclipse.org/eclipse/downloads/drops4/I20200310-1800/testResults.php

Software site repository:
   https://download.eclipse.org/eclipse/updates/4.16-I-builds

Specific (simple) site repository:
   https://download.eclipse.org/eclipse/updates/4.16-I-builds/I20200310-1800

Equinox downloads:
   https://download.eclipse.org/equinox/drops/I20200310-1800

and if there are comparator errors or pom version updates. The link to those logs should be included in the mail

Second issue is
At the end of test run we should get a mail with test results similar to https://www.eclipse.org/lists/platform-releng-dev/msg36206.html
Comment 1 Alexander Kurtakov CLA 2020-04-03 02:55:51 EDT
Regular success builds notification should be fine starting tomorrow (they are good even today except for some formatting issues). Comparator/pom issues handling in the mail will be huge task due to the way email sending in JIRO works - I don't think it's feasible for this to happen prior to moving the build file to Jenkinsfile and using groovy syntax.
I would rather fail the build directly so we get build failure and nothing deployed. 
Either way, rest of this request is really low priority compared to unstable tests, missing perf tests results and etc.
Comment 2 Sravan Kumar Lakkimsetti CLA 2020-04-14 00:57:16 EDT
Please see 562042 for the second part of this bug
Comment 3 Dani Megert CLA 2020-04-14 03:43:54 EDT
(In reply to Sravan Kumar Lakkimsetti from comment #2)
> Please see 562042 for the second part of this bug
See bug 562042 and bug 562087.
Comment 4 Alexander Kurtakov CLA 2022-02-03 15:06:11 EST
This should be done or at least in best state we can get for now.