Closed Bug 601362 Opened 14 years ago Closed 14 years ago

talos logs should be published somewhere accessible from buildbot data

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dbaron, Assigned: catlee)

References

Details

Attachments

(1 file)

Currently the build and unit test jobs have their logs published at a location that can be determined from the buildbot data and is not dependent on tinderbox: they're published on ftp.mozilla.org alongside the build. However, as far as I know, the talos runs don't have their logs published. Publishing the talos logs somewhere is needed for tinderboxpushlog without tinderbox.
I'm not sure how difficult it is to do this; assigning to Catlee for prioritization.
Assignee: nobody → catlee
Er, yeah, they are uploaded. But the build JSON doesn't have a "builddir" in properties, so I can't predict the filename.
I've filed bug 611448 about that problem.
Quick fix until we can get logUrls
Attachment #495016 - Flags: review?(rail)
Comment on attachment 495016 [details] [diff] [review] Add builddir to talos jobs Looks good to me. We use the similar approach for ScriptFactory based builders in release.py.
Attachment #495016 - Flags: review?(rail) → review+
Flags: needs-reconfig?
Reopening so we can land this patch.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment on attachment 495016 [details] [diff] [review] Add builddir to talos jobs Landed in changeset: 1246:8d2155a2fcdf, merged to the production-0.8 branch in 1250:30537b778f04
Attachment #495016 - Flags: checked-in+
Is this done now?
Flags: needs-reconfig?
Yup
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: