Closed Bug 633973 Opened 13 years ago Closed 11 years ago

TBPL shows pending/running builds for trees that the builds are not aimed at.

Categories

(Tree Management Graveyard :: TBPL, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Unassigned)

References

Details

Looking at:

http://tbpl.mozilla.org/?tree=Mobile

There are currently shown a lot of pending and running builds. However, this isn't really true, the pending/running builds there are mainly for the Firefox tree.

This is the same the other way round, the Firefox tree actually shows "Android opt" as building, even though the results go to the Mobile tree.

This also affects the comm-central based TBPL where we have Thunderbird/SeaMonkey/Sunbird all currently sharing the same TBPL instance.
There is nothing we can do about it right now. Both Trees use the same repo
http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/c929a1420853/js/Config.js#l22
In tbpl as well as in the running/pending json files.

Bug 633916 will help on our side, but the json files still list the builds under "mozilla-central"
Depends on: 633916
(In reply to comment #1)
> There is nothing we can do about it right now. Both Trees use the same repo
> http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/c929a1420853/js/Config.js#l22
> In tbpl as well as in the running/pending json files.

I don't think its just that. As you'd need to change the mobile builders to a different branch in buildbot as well.

> Bug 633916 will help on our side, but the json files still list the builds
> under "mozilla-central"

It may help for the mobile case, I'm not sure it would help for the comm-central app situation where we do all build from the same place.

I think the only way to help that case (which could also be used for Mobile) would be to additionally store the tree in the build databases.

The current system works for one-app per repo, but for example, if you got xulrunner builds reporting in, you'd end up with those broken in a similar way.
Exactly, the running/pending files need to be grouped in a different way that has the meaning of “what” is building, not from which repo.
The mobile tree no longer exists :-)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
This was probably a releng bug all along - if our reverse-engineering that the keys in builds-pending.js and builds-running.js are the part after a / in the primary repo was correct (which seems to be the case for gaia-central/gaia-master), then that's the thing that is broken.
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.