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

Bug 387373

Summary:	Builder should report error if there is no v-tag
Product:	[Eclipse Project] Platform	Reporter:	Dani Megert <daniel_megert>
Component:	Releng	Assignee:	Platform-Releng-Inbox <platform-releng-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert, david_williams
Version:	3.8
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Dani Megert

2012-08-16 07:31:24 EDT

If a I- or M- tag is added to a commit which does not have a v-tag the builder should report an error (visibly) or even abort.

Comment 1 David Williams

2012-08-16 10:21:20 EDT

As a reminder (to myself if no one else :) it was bug 387352 that gave rise to this request. 

There, Dani discovered that repositories.txt paths (repo names) must match exactly the path in map files (there is no ".git" automatically added if left implicit).

Comment 2 Dani Megert

2012-08-16 10:23:30 EDT

(In reply to comment #1)
> As a reminder (to myself if no one else :) it was bug 387352 that gave rise
> to this request. 
> 
> There, Dani discovered that repositories.txt paths (repo names) must match
> exactly the path in map files (there is no ".git" automatically added if
> left implicit).

Actually, that would be a second check :-).

Comment 3 David Williams

2014-03-25 20:31:04 EDT

I think this best classified as "won't fix", since we no longer use this methodology. (Though, suspect there are improvements still that could be made to the way we handle the repositories.txt file ... I know of at least one bug open on allowing comments ... but, I think we simply log a warning if there is a line we don't recognize, and should perhaps fail -- but not sure ... going from memory.)