Bugzilla – Full Text Bug Listing
| Summary: | Send mail to platform-releng-dev when build starts | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Dani Megert <daniel_megert> |
| Component: | Releng | Assignee: | Platform-Releng-Inbox <platform-releng-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne, kim.moir, pwebster, remy.suen |
| Version: | 3.8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Dani Megert
Related to bug 364078. More interesting than a simple "build started" would be to email the contents of the report.txt generated by the tagging script. This tells which bundles have changed, and related bugzillas. (In reply to comment #1) > Related to bug 364078. More interesting than a simple "build started" would be > to email the contents of the report.txt generated by the tagging script. This > tells which bundles have changed, and related bugzillas. It depends how long it takes until this info is ready to be sent. Last week showed, that builds got started which were not on the build schedule and which were not announced. If committers don't expect a build and then modify 'integration' during that time, evil things can happen. (In reply to comment #2) > It depends how long it takes until this info is ready to be sent. Last week > showed, that builds got started which were not on the build schedule and which > were not announced. If committers don't expect a build and then modify > 'integration' during that time, evil things can happen. Right, the first problem in the last set of builds was caused by the difference between the build-started time and the build-tagging/build-report time. PW build notes and etc. are no longer provided and the mail about built started is sent so I'm closing this one. |