Closed Bug 1205397 Opened 10 years ago Closed 10 years ago

repacked eme-free builds

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mixedpuppy, Assigned: coop)

References

Details

eme-free builds probably need to go someplace other than the partner bucket, for now I've removed them from the repack-manifests since the directory structure for eme-free is different. we can: - let eme-free go into partner bucket, just remove output_dir from the repack.cfg - handle eme-free separately from the rest of the partner builds
(In reply to Shane Caraveo (:mixedpuppy) from comment #0) > eme-free builds probably need to go someplace other than the partner bucket, > for now I've removed them from the repack-manifests since the directory > structure for eme-free is different. > > we can: > - let eme-free go into partner bucket, just remove output_dir from the > repack.cfg I think this is fine for now. Eventually we'll want to either copy them out of the partner bucket automatically, or override the default bucket from the repack.cfg file. > - handle eme-free separately from the rest of the partner builds We still need EME builds per release, although I should follow-up with Javaun to find out for how long. If we start moving the EME builds to the correct bucket, it shouldn't matter.
(In reply to Chris Cooper [:coop] from comment #1) > (In reply to Shane Caraveo (:mixedpuppy) from comment #0) > > eme-free builds probably need to go someplace other than the partner bucket, > > for now I've removed them from the repack-manifests since the directory > > structure for eme-free is different. > > > > we can: > > - let eme-free go into partner bucket, just remove output_dir from the > > repack.cfg > > I think this is fine for now. Eventually we'll want to either copy them out > of the partner bucket automatically, or override the default bucket from the > repack.cfg file. A bucket to bucket copy is cheap and fast, so that could be possible also. I'll remove output_dir from the config for now.
These are being created now as part of the normal partner repack process.
Assignee: nobody → coop
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.