1201085 - Delete unused code form mozharness repositories

Status: RESOLVED FIXED

(Release Engineering :: Applications: MozharnessCore, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

To reduce the chance of confusion or, worse, divergence between the two mozharness repos (build/mozharness itself and gecko), we should delete unused code from each.

That would mean deleting everything not needed for vcs-sync, etc. from build/mozharness, and deleting vcs-sync, etc. from gecko.

This will have several advantages:
 1. reduce possibility of confusion over where to land a patch
 2. prevent divergence of matching code between the two repos (e.g., FooMixin on gecko has features A, B, but FooMixin in build/mozharness has features B, C, and oh there's that patch to B, I'm not sure if that got ported to gecko)
 3. suss out any remaining users of build/mozharness that should be using the gecko copy (it's not clear to me whether B2G has completely transitioned, for example)

Comment 1

[Armen [:armenzg]]

TC has not moved away from it

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

TC itself doesn't use Mozharness at all.  There are *tasks* in TC using mozharness -- which of those haven't moved away?

Comment 3

[Jordan Lund (:jlund)]

+1 this is a great idea!

Comment 4

[Armen [:armenzg]]

The b2g tc tasks that is.

Some of these:
https://treeherder.allizom.org/#/jobs?repo=mozilla-central&filter-searchStr=taskcluster

Comment 5

[Selena Deckelmann :selenamarie :selena]

Dylan -- can someone from your team tackle this? Wander can mentor.

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

I filed bug 1201171 to track that work -- Dylan, please re-product and re-component as necessary :)

Comment 7

[[e-mail] (:bhearsum)]

cc'ing Tom, I think he was looking at doing some of this.