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

Bug 350368

Summary: can not tag map files each build, with only wtpBuild id
Product: [WebTools] WTP Releng Reporter: David Williams <david_williams>
Component: relengAssignee: webtools.releng <webtools.releng-inbox>
Status: NEW --- QA Contact: Carl Anderson <ccc>
Severity: normal    
Priority: P3 CC: ccc, krzysztof.daniel, thatnitind
Version: 3.10   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description David Williams CLA 2011-06-26 01:22:48 EDT 
As we are working to make wtpBuild independent of specific committer ids, one issue is that, currently, we tag cvs map files each build, to help make them reproducible, and easier to compare one build to another. 

But, of course, cvs can only be tagged, or written to, with committer id, not wtpBuild. 

So, we'll have to stop tagging each build ... or, figure out some other solution.
Comment 1 David Williams CLA 2012-07-11 08:33:37 EDT 
I sort of hate to suggest it, because its a stretch of "the rules" (and, because Denis doesn't like it :)  but the Eclipse Project's PMC requested the Eclipse Project's equivalent (e4Build) be granted the ability to tag and push changes to all their git repos, thus making it a sort of "super committer". If WTP also requests it ... that might make the whole thing be re-considered. 

Of course, there are other solutions as well, which some would say would better from a git point of view ... for example, one could simply record the hash tag for a change set used in build ... and often, recording that might often be enough, but if committers wanted a more meaningful tag for the long term for some builds, they could always do that later, once they had that hash tag.

Just saying what I know ... not recommending any particular action.
Comment 2 David Williams CLA 2012-07-11 08:59:41 EDT 
(In reply to comment #1)
> ... [e4Build has] ability to tag and push
> changes to all their git repos, thus making it a sort of "super committer". 

To be more exact, I think it only can commit changes to one repo ("the map files") and it can push tags to other repos ... but, in both cases (map files or tags) they are not really considered "Intellectual Property" which was the main justification.