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

Roll out stable 40.20240519.3.0, testing 40.20240602.2.0, next 40.20240602.1.0 #908

Conversation

coreosbot-releng
Copy link

Requested by @yasminvalim via GitHub workflow (source).

Copy link

github-actions bot commented Jun 5, 2024

next
    version: 40.20240602.1.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:03:29)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)
stable
    version: 40.20240519.3.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:03:29)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)
testing
    version: 40.20240602.2.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:03:28)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)

@coreosbot-releng coreosbot-releng force-pushed the rollout-40.20240519.3.0-40.20240602.2.0-40.20240602.1.0 branch from 5cce5ce to 9630f65 Compare June 5, 2024 16:57
@coreosbot-releng coreosbot-releng force-pushed the rollout-40.20240519.3.0-40.20240602.2.0-40.20240602.1.0 branch from 9630f65 to 004796e Compare June 5, 2024 16:57
Copy link

github-actions bot commented Jun 5, 2024

next
    version: 40.20240602.1.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:02:11)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)
stable
    version: 40.20240519.3.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:02:11)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)
testing
    version: 40.20240602.2.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:02:11)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)

Copy link

github-actions bot commented Jun 5, 2024

next
    version: 40.20240602.1.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:01:50)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)
stable
    version: 40.20240519.3.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:01:50)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)
testing
    version: 40.20240602.2.0 (latest)
    start: 2024-06-06 14:00:00+00:00 UTC (in 21:01:50)
           2024-06-06 16:00:00+02:00 Germany/France/Poland
           2024-06-06 11:00:00-03:00 Brazil
           2024-06-06 08:00:00-06:00 Colorado
           2024-06-06 15:00:00+01:00 Ireland
           2024-06-06 10:00:00-04:00 Raleigh/New York/Toronto
           2024-06-06 07:00:00-07:00 Vancouver
    duration: 1440m (24.0h)

Copy link

@yasminvalim yasminvalim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ✅

Copy link
Member

@c4rt0 c4rt0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@yasminvalim yasminvalim merged commit 338c519 into coreos:main Jun 5, 2024
3 checks passed
@jlebon
Copy link
Member

jlebon commented Jun 5, 2024

Sorry, missed this.

Since we're a bit late this week, let's make it start today, with a 48h window as usual.

@yasminvalim
Copy link

Sorry, missed this.

Since we're a bit late this week, let's make it start today, with a 48h window as usual.

I already did it, but for tomorrow with a 24hrs window since I notice that its a bit late. There is a way to edit it or could I run another one?

@jlebon
Copy link
Member

jlebon commented Jun 5, 2024

I already did it, but for tomorrow with a 24hrs window since I notice that its a bit late. There is a way to edit it or could I run another one?

I don't think the GitHub workflow can deal with that. The easiest would probably be to run the same script locally. Try e.g.:

./rollout.py add $stream $version '3 PM EDT today' 48 --replace

Do this for each stream, and then open a new PR with the changes.

@yasminvalim
Copy link

I already did it, but for tomorrow with a 24hrs window since I notice that its a bit late. There is a way to edit it or could I run another one?

I don't think the GitHub workflow can deal with that. The easiest would probably be to run the same script locally. Try e.g.:

./rollout.py add $stream $version '3 PM EDT today' 48 --replace

Do this for each stream, and then open a new PR with the changes.

Thanks for doing it for me!

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.

5 participants