Closed Bug 925022 Opened 9 years ago Closed 5 years ago

[marionette-js-runner] Stage marionette js runner on TBPL


(Testing Graveyard :: JSMarionette, defect)

Not set


(Not tracked)



(Reporter: gaye, Assigned: gaye)



In order to do this, we need releng (eg Dustin) to deploy the npm-mirror utility wlach and I wrote. Currently it lives on github and If we were to install it from github, we could do something like...

git clone
git clone
cd npm-mirror

# The following command syncs all of npm package dependencies
# for gaia from to ../packages. It also.
# writes the json manifest files necessary to have a web server
# rooted at ../packages listening on port 8080 behave like
# a bonafide npm mirror.
bin/npm-mirror \
    --host http://localhost:8080 \
    --manifestFile ../marionette-js-runner/package.json \
    --registry \
    --packageDir ../packages

cd ../packages
# Start a web server listening on port 8080

I will go ahead and make the changes aki suggested in 902124 and then push my
changeset to Then jgriffin suggested
we do a test build on tbpl staging (cedar).
Oh also I tested my sync utility with wlach's which is built on top of mozhttpd. I think other things would work fine, but they probably have to set the right mime types and also allow something in lalala/index.json to get served at http://localhost:8080/lalala/.
Assignee: nobody → gaye
Flags: needinfo?(dustin)
Depends on: 902124
Over in bug 912973, I'm waiting for some changes to the mirror script before we can finish the deployment.  So that mirror's not ready yet, pending work by :wlach.
Hey Dustin,

Just FYI, I hijacked some of wlach's work to turn it into a more "open source" node utility with things like unit/integration/lint suites and documentation so that perhaps the gaia and larger js community can help us maintain it. I'll take a look at the issues you brought up in 912973 later today.
That's aweseome!
Flags: needinfo?(dustin)
Hey Dustin!

1. I believe npm needs absolute urls.
2. I still mirror all of the versions of all of the packages, but if it's too much data I can do follow-up work.

Can we go ahead and try deploying the node npm-mirror utility as is (much like you did with wlach's last iteration)?
Flags: needinfo?(dustin)
I would like to point the mozharness I wrote to it this week ideally :)
Sure, but the big question there was how to provide the mirror at two different URLs, with a few possible solutions.  Was one of those selected and/or implemented?
OK, bug 912973 is closed, but AIUI there's some additional work to mirror devDependencies.  I can re-deploy the mirror script whenever that's necessary.

I'm a little leery of embedding into the code directly.  If this is run from Mozharness, then I suspect it should be a config variable (/cc aki).  Otherwise, I'm not sure what method is best to specify this link.
Flags: needinfo?(dustin) → needinfo?(aki)
(In reply to Dustin J. Mitchell [:dustin] from comment #8)
> I'm a little leery of embedding into
> the code directly.  If this is run from Mozharness, then I suspect it should
> be a config variable (/cc aki).

That's correct.
Flags: needinfo?(aki)
Depends on: 925419, 925422, 925424
Depends on: 925516
Depends on: 925524
No longer depends on: 925516
Depends on: 928487
Depends on: 918303
No longer depends on: 918303
Depends on: 934608
cc yurenju,

I think we could use npm-mirror in TBPL once the bug is fixed.
Bulk closed as part of
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.