This assumes that the spec sets are logically independent from each other,
i.e., building different ABIs.
Code shamelessly adapted from locale-gen.
Signed-off-by: Andreas K. Huettel <dilfridge@gentoo.org>
The snapshot generation logic was moved earlier in the build (before
the cleaning logic) which caused the preclean to nuke the freshly
generated cache. Move all the preclean logic back up before that.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Due to https://bugs.gentoo.org/722108 , selinux stable builds cannot
possibly succeed right now. We are wasting lots of hours in update_seed
since that part cannot be cached. We can re-enable them when
https://bugs.gentoo.org/714376 is fixed (stabilization).
Signed-off-by: Ben Kohler <bkohler@gentoo.org>
Added a small debug echo so that post_build.log shows some information
about what's being uploaded. Might add destination info later.
Signed-off-by: Ben Kohler <bkohler@gentoo.org>
Use an easier-to-read "upload" function in place of "${cmd[@]}" array
syntax. Added a helper var UPLOAD_DEST to be set in advance so that
upload function takes only a list of filenames to be uploaded.
Signed-off-by: Ben Kohler <bkohler@gentoo.org>
Previously when we were copying locally there was no (major) problem
with wildcarding a long list of files to be transferred after every
single spec finishes. Now that we are transferring to a remote host,
this results in a lot of wasted transfer time & bandwidth.
I have adjusted the post_build function to only transfer the new files
known to be produced by each spec (which has files meant to be
published).
Signed-off-by: Ben Kohler <bkohler@gentoo.org>
Previously when we were copying locally there was no (major) problem
with wildcarding a long list of files to be transferred after every
single spec finishes. Now that we are transferring to a remote host,
this results in a lot of wasted transfer time & bandwidth.
I have adjusted the post_build function to only transfer the new files
known to be produced by each spec (which has files meant to be
published).
Signed-off-by: Ben Kohler <bkohler@gentoo.org>
Most architecture's build systems are hosted at OSUOSL. The place the
stages need to end up is ultimately masterreleases.gentoo.org, also at
OSUOSL. For some unknown reason, instead of rsync'ing from one system to
another in the same building, we were sending the stages first (slowly,
I might add) to nightheron in France, before sending them back to
OSUOSL.
robbat2 has added a releng-incoming.gentoo.org DNS record that currently
points to nightheron. This will allow us to switch the record in the
future and save the stages from needing to circumnavigate the globe
before reaching the mirrors.
Signed-off-by: Matt Turner <mattst88@gentoo.org>
We're using UserKnownHostsFile=/dev/null to force ssh to use the
fingerprint from DNSSEC, so StrictHostKeyChecking=no just prevents ssh
from asking us to confirm the fingerprint.
Signed-off-by: Matt Turner <mattst88@gentoo.org>
This causes an interactive prompt:
Are you sure you want to continue connecting (yes/no/[fingerprint])?
The plan is to get the SSH fingerprint via DNSSEC, so I'll revert this
change until that is in place and wired up.
This reverts commit 63174346f2.
Signed-off-by: Matt Turner <mattst88@gentoo.org>
Most architecture's build systems are hosted at OSUOSL. The place the
stages need to end up is ultimately masterreleases.gentoo.org, also at
OSUOSL. For some unknown reason, instead of rsync'ing from one system to
another in the same building, we were sending the stages first (slowly,
I might add) to nightheron in France, before sending them back to
OSUOSL.
robbat2 has added a releng-incoming.gentoo.org DNS record that currently
points to nightheron. This will allow us to switch the record in the
future and save the stages from needing to circumnavigate the globe
before reaching the mirrors.
Signed-off-by: Matt Turner <mattst88@gentoo.org>
