Closed
Bug 650882
Opened 13 years ago
Closed 13 years ago
port hgtool to mozharness
Categories
(Release Engineering :: Applications: MozharnessCore, defect, P4)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
References
Details
(Whiteboard: [mozharness][automation])
Attachments
(1 file)
137.34 KB,
patch
|
rail
:
feedback+
|
Details | Diff | Splinter Review |
This should make mozharness' mercurial actions standardized and more robust.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → aki
Assignee | ||
Comment 2•13 years ago
|
||
* port hgtool in a completely backwards compatible way * port hgtool to work naturally in the mozharness framework * port hgtool with an eye towards clean and maintainable code Right now it's looking like we need to choose two. I'm thinking about the latter two... keep the same functionality but break some direct hgtool/util.hg backwards compatibility.
Assignee | ||
Comment 3•13 years ago
|
||
http://hg.mozilla.org/users/asasaki_mozilla.com/talosrunner/file/4d1db9f026c2/scripts/sourcetool.py works! ./scripts/sourcetool.py http://hg.mozilla.org/build/buildbotcustom gave me a buildbotcustom and an hg revision. However, I think mozharness.base.vcs.mercurial.MercurialVCS needs lots of work (see comment 2). http://hg.mozilla.org/users/asasaki_mozilla.com/talosrunner/file/4d1db9f026c2/mozharness/base/vcs/mercurial.py#l84
Assignee | ||
Comment 4•13 years ago
|
||
The diff is probably too large to be helpful. This is basically an |hg diff -r default| from the tip of the 0.4-devel branch in my talosrunner user repo. It may be easiest to look at the source: http://hg.mozilla.org/users/asasaki_mozilla.com/talosrunner/file/896b5368ad7d/scripts/sourcetool.py I was able to successfully: scripts/hgtool.py http://hg.mozilla.org/build/buildbotcustom ../foo and scripts/hgtool.py -s ~/src/clean/buildbotcustom http://hg.mozilla.org/build/buildbotcustom ../foo
Attachment #528768 -
Flags: feedback?(rail)
Assignee | ||
Updated•13 years ago
|
Attachment #528768 -
Flags: feedback?(catlee)
Assignee | ||
Comment 5•13 years ago
|
||
All unit tests from build/tools/lib/python/buildtools/test/test_util_hg.py are ported as of http://hg.mozilla.org/users/asasaki_mozilla.com/talosrunner/rev/36e76a3e6fd9 .
Comment 6•13 years ago
|
||
Comment on attachment 528768 [details] [diff] [review] huge diff; working hgtool.py Some nits: * as you said in the comments it would be better to remove env variables * url = "%s/rev/%s" % (c['vcs_repo'], got_revision) looks HG specific, probably you may want to wrap it in the future, something like vcs.get_url(...) * vcs or scm? :p BTW, there are a lot of functions from build/tools. We need to switch to mozharness to prevent more divergence in the future.
Attachment #528768 -
Flags: feedback?(rail) → feedback+
Assignee | ||
Updated•13 years ago
|
Attachment #528768 -
Flags: feedback?(catlee)
Assignee | ||
Comment 7•13 years ago
|
||
hgtool-in-mozharness will be landing as part of the 0.4 landing (bug 651974).
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•10 years ago
|
Component: Other → Mozharness
You need to log in
before you can comment on or make changes to this bug.
Description
•