Closed Bug 693392 Opened 13 years ago Closed 8 years ago

mozharness MercurialVCS should differentiate tag and revision behavior

Categories

(Release Engineering :: Applications: MozharnessCore, defect, P5)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: mozilla, Unassigned)

References

Details

(Whiteboard: [mozharness])

In bug 692388 (http://hg.mozilla.org/build/mozharness/rev/e76fdabbca55) I fixed the mozharness MercurialVCS revision behavior to support tags. Essentially, since a tag is created *after* a revision is created, you need to update to tip and then update back to the tag. However, in certain cases, e.g. Try, where you know the revision, it's faster to just update to the revision without updating to tip first. We should split the 'revision' into 'revision' and 'tag'. One should take precedence (probably revision) if both are set. Revision should use the old behavior. Tag should use the new behavior.
Product: mozilla.org → Release Engineering
Component: Other → Tools
QA Contact: hwine
Component: Tools → Mozharness
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.