Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366282 - Auto tagging should not fail in case of a zombie tag
Summary: Auto tagging should not fail in case of a zombie tag
Status: RESOLVED DUPLICATE of bug 366279
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-09 22:43 EST by Deepak Azad CLA
Modified: 2011-12-11 20:50 EST (History)
3 users (show)

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 Deepak Azad CLA 2011-12-09 22:43:42 EST 
From https://bugs.eclipse.org/bugs/show_bug.cgi?id=364820#c37

Recently the auto-tagging failed (build I20111207-2118) when platform.common repo had a zombie tag, i.e. the map file contained the tag but it was not on a commit in master or integration branch. Look at http://git.eclipse.org/c/platform/eclipse.platform.common.git/, the tag 'v20111205-2016' is not on a commit on a branch, however it is shown under the 'Tag' section. The zombie state of 'v20111205-2016' was caused while rewriting the history to fix the git issues JDT team had on Tuesday 6 Dec.

To work around this issue we had to do manual tagging which resulted in further problems - http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg19407.html

I think the auto-tagging scripts should gracefully handle the zombie tag case and just tag the tip of the integration branch.
Comment 1 Kim Moir CLA 2011-12-10 08:49:23 EST 
I'm going to make the build fail instead.  See bug 366279.

*** This bug has been marked as a duplicate of bug 366279 ***
Comment 2 John Arthorne CLA 2011-12-11 20:50:47 EST 
(In reply to comment #0)
> The zombie state of 'v20111205-2016' was caused while rewriting
> the history to fix the git issues JDT team had on Tuesday 6 Dec.

Keep in mind that rewriting history in the master branch of the remote repository is a bad practice. This makes builds unreproducible, and can cause problems for anyone who has a clone of the repository. We discussed making this illegal in bug 343150 but haven't enacted it yet.