Bug 8770 - Release rsync isn't automated causing items to not be released to production servers.
Summary: Release rsync isn't automated causing items to not be released to production ...
Status: VERIFIED FIXED
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.1 M3
Assignee: Michael Halstead
QA Contact: Bogdan Alexandru Voiculescu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-12-04 12:58 UTC by Beth Flanagan
Modified: 2016-05-09 14:24 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Beth Flanagan 2015-12-04 12:58:03 UTC
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8734 is an example of this.

During our release, we move the release bits to various locations on the autobuilder infrastructure. Downloads is supposed to pick them up and rsync them to the appropriate places. This doesn't seem to be happening anymore.

I know part of the reason why is that we were generating so much data that we moved to an as needed model, but I'm wondering if:

a. That is how we really want to do this as it seems to cause issues.
b. If we do want to have it occur this way, if there isn't a better way to ensure all release bits are picked up.

Perhaps this is just documentation on for infrastructure release process or reimplementing the cron rsyncs?
Comment 1 Michael Halstead 2016-03-09 19:19:10 UTC
New release directories are automatically created. For changes to existing releases intervention is still required.
Comment 2 Bogdan Alexandru Voiculescu 2016-05-09 14:24:31 UTC
We have not seen anymore problems in this area. Marking this as verified.