Closed
Bug 1167279
Opened 9 years ago
Closed 8 years ago
Please create an index to the latest simulator build for b2g
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nhirata, Unassigned)
Details
(Whiteboard: [spark])
Currently I see : https://tools.taskcluster.net/index/artifacts/#buildbot.branches.mozilla-central/buildbot.branches.mozilla-central.linux64_gecko for the simulator for linux 64 bit and https://tools.taskcluster.net/index/#gecko.v1.mozilla-central.latest.linux/gecko.v1.mozilla-central.latest.linux, where it has all the other links for emulator, flame, mulet, desktop and aries. Could we get a link to the simulator in the https://tools.taskcluster.net/index/#gecko.v1.mozilla-central.latest.linux/gecko.v1.mozilla-central.latest subdirectories please? note: the builds not being listed in any of the subdirectories: https://tools.taskcluster.net/index/#gecko.v1.mozilla-central.latest.linux/gecko.v1.mozilla-central.latest is being tracked in bug 1167266
Reporter | ||
Updated•9 years ago
|
Whiteboard: [spark]
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(nhirata.bugzilla)
Comment 1•9 years ago
|
||
So you want: buildbot.branches.mozilla-central.linux64_gecko To be listed in: gecko.v1.mozilla-central.latest.linux.<something> Is that correct? I think this is already the case, if you checkout: gecko.v1.mozilla-central.latest.linux.b2g-desktop.opt See: https://tools.taskcluster.net/index/artifacts/#gecko.v1.mozilla-central.latest.linux.b2g-desktop.opt/gecko.v1.mozilla-central.latest.linux.b2g-desktop.opt I might be wrong here... We should really document what kinds of builds we have an where we want them indexed. I certainly didn't expect "buildbot.branches.mozilla-central.linux64_gecko" to be the b2g-desktop build. Note, if you inspect the task, you can look at task.routes, to see what they are indexed under. Any route on the form "index.<namespace>" you have the task indexed under <namespace> in index.
Reporter | ||
Comment 2•9 years ago
|
||
Well, the thought is more to conglomerate all things B2G in one folder somewhere; you're right. We should be aware of x64 linux versus linux versus windows versus mac for the b2g desktop and .xpi (simulator ) and mulet and emulator. Note : all 4 build types are different. I don't know what the finished indexing should look like. The current situation is that it's easy to get lost in trying to search for the builds. I agree that we do need this documented; other people have mentioned the same. I believe we would have to update multiple moz dev docs, such as but not limited to : https://developer.mozilla.org/en-US/Firefox_OS/Phone_guide/Flame/Updating_your_Flame https://developer.mozilla.org/en-US/Firefox_OS/Developing_Gaia/Different_ways_to_run_Gaia https://developer.mozilla.org/en-US/docs/Tools/Firefox_OS_Simulator https://developer.mozilla.org/en-US/Firefox_OS/Building_the_Firefox_OS_simulator etc. etc...
Reporter | ||
Comment 3•9 years ago
|
||
(Please NI me if you need more information from me)
Flags: needinfo?(nhirata.bugzilla) → needinfo?(jopsen)
Comment 4•9 years ago
|
||
@jlal, You are documenting in-tree logic (integration bits) this quarter. Can you take a look at documenting index namespaces too? I'm not quiet sure what the logic behind the current design is, "linux.b2g-desktop.opt" seems like a lot of dots to me, where maybe we could do dashes to make less hierarchy where we might not need it.
Flags: needinfo?(jopsen) → needinfo?(jlal)
Updated•9 years ago
|
Component: TaskCluster → General
Product: Testing → Taskcluster
Comment 5•9 years ago
|
||
Naoki -- is any work here still needed?
Flags: needinfo?(jlal) → needinfo?(nhirata.bugzilla)
Reporter | ||
Comment 6•9 years ago
|
||
Yes. Documentation work on the indexes and indexes pointing to the simulator builds. (not to be confused with emulator, mulet, b2g desktop builds; these are all different.)
Flags: needinfo?(nhirata.bugzilla)
Updated•8 years ago
|
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.
Description
•