Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multi-arch-builders: force hostname; prune during the night #526

Merged
merged 2 commits into from May 25, 2022

Conversation

dustymabe
Copy link
Member

commit 3b8589daaff04eb1c95681641a7602f35f7c7a49
Author: Dusty Mabe <dusty@dustymabe.com>
Date:   Tue May 24 09:43:06 2022 -0400

    multi-arch-builders: build and prune at a different time of day.
    
    Rather than 00:00 UTC let's push it further back hopefully when
    most of our team is either still asleep or already asleep. I've
    seen a couple cases recently where the 00:00 UTC runs happen around
    the time the `testing-devel` is running for the day from the
    bump-lockfile bump and it ends up taking out an intermediate container
    and volume used by gangplank.

commit c4d44cfbc77ac96e6cfeeef52de38683751d9cf9
Author: Dusty Mabe <dusty@dustymabe.com>
Date:   Tue May 24 09:41:03 2022 -0400

    multi-arch-builders: Force writing /etc/hostname
    
    Force /etc/hostname even if the file already exists. I saw this on
    either the ppc64le or s390x builder where the hostname file had
    already been created.

Force /etc/hostname even if the file already exists. I saw this on
either the ppc64le or s390x builder where the hostname file had
already been created.
Rather than 00:00 UTC let's push it further back hopefully when
most of our team is either still asleep or already asleep. I've
seen a couple cases recently where the 00:00 UTC runs happen around
the time the `testing-devel` is running for the day from the
bump-lockfile bump and it ends up taking out an intermediate container
and volume used by gangplank.
@jlebon jlebon merged commit 4222c42 into coreos:main May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants