Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 376229 - (eventually) need to send mail and not build if autotagging detects no changes
Summary: (eventually) need to send mail and not build if autotagging detects no changes
Status: RESOLVED DUPLICATE of bug 377666
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 375807 376460
  Show dependency tree
 
Reported: 2012-04-06 00:16 EDT by David Williams CLA
Modified: 2012-05-13 12:59 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2012-04-06 00:16:29 EDT 
Once things are running smoothly, if it comes time to a schedule a build, if the "autotag" script detects no changes, then a) should send email saying the build will be skipped since no changes and b) not do the build. 

From what I can tell now, if there's no changes, it sends no mail, but merrily continues on doing the build (which, of course, is what we want, right now ... but .... not in a few weeks). 

This isn't just a nicity, but helps people know if something they were expecting to be "released" was not (or, at least, was not detected for some reason). Mostly likely committed but not pushed. Perhaps not "merged" with integration.
Comment 1 David Williams CLA 2012-05-13 12:59:23 EDT 
seems I was getting carried away recording my "to do" items (i.e. seems same work as described elsewhere).

*** This bug has been marked as a duplicate of bug 377666 ***