Over in bug 1289194, a landing outside js/src managed to break SM-tc(pkg) jobs. Said bustage showed up on later pushes that touched js/src. It's also easy to see how this could have been caught by a Try push had the job run there. Maybe adding just the top-level moz.build to the rules would suffice here?

It pulls from a number of different areas. We should add /configure.py /moz.configure /test.mozbuild /intl/icu/... /Makefile.in /moz.build /nsprpub/... /build/... /config/... /mfbt/... /python/... and then some weird stuff: /dom/bindings/mozwebidlcodegen /media/webrtc/trunk/tools/gyp /testing/mozbase/... /modules/fdlibm/... /modules/zlib/... /layout/tools/reftest/... /toolkit/mozapps/installer/... /mozglue/... /memory/... though it might be nice if we could remove the dependency on some of that stuff.

Actually, almost everything in there is already in the list. The only exceptions I see are: Makefile.in moz.build config/** I'll wait for bug 1286075 to land, unless dustin adds it in himself.

Perhaps config/** is overkill, but I'm just blindly adding everything mentioned in make-source-package.sh.

Comment on attachment 8791408 [details] [diff] [review] Add in more files to trigger the sm-package job Review of attachment 8791408 [details] [diff] [review]: ----------------------------------------------------------------- Unlike with GCs, a conservative approach seems like a good one in this case.

Pushed by sfink@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/edf9ffaf92b0 Add in more files to trigger the sm-package job, r=fitzgen