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

workflows: Auto-refresh tasks container every week #629

Merged
merged 2 commits into from
Dec 6, 2024

Conversation

martinpitt
Copy link
Member

We tend to forget about refreshing the tasks container, and thus fall
behind on browser and toolchain updates.

Run these every Saturday, so that they are ready for the Sunday night
runs of our projects' tasks-container-update workflows.

We tend to forget about refreshing the tasks container, and thus fall
behind on browser and toolchain updates.

Run these every Saturday, so that they are ready for the Sunday night
runs of our projects' tasks-container-update workflows.
@martinpitt
Copy link
Member Author

If this lands today, it can run tomorrow morning, and I'll watch/fix up the results on Monday.

@martinpitt martinpitt requested a review from jelly December 6, 2024 08:05
Copy link
Member

@jelly jelly left a comment

Choose a reason for hiding this comment

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

Weekly feels like a lot of churn but lets see how it goes. This is all gated in the end right?

Just wondering how we detect deploy failures? I guess for folks following the repo and have github notifications they would catch it :)

@martinpitt
Copy link
Member Author

This is all gated in the end right?

Yes, all our projects have a .cockpit-ci/container which pins down a particular tag. And a "tasks-container-update" workflow which tries to update to the new one, and will tell us about changed browser pixel tests or other incompatibilities. I.e. gated on the project level.

Just wondering how we detect deploy failures?

Yes, at least I get email about it. Also, even if nobody listens, we are no worse off than right now -- every now and then the pilot updates it manually, and then on https://github.com/cockpit-project/cockpituous/actions/workflows/build-tasks.yml we see the failures.

@martinpitt martinpitt merged commit 4824188 into main Dec 6, 2024
3 checks passed
@martinpitt martinpitt deleted the tasks-auto-update branch December 6, 2024 09:02
@jelly
Copy link
Member

jelly commented Dec 6, 2024

This is all gated in the end right?

Yes, all our projects have a .cockpit-ci/container which pins down a particular tag. And a "tasks-container-update" workflow which tries to update to the new one, and will tell us about changed browser pixel tests or other incompatibilities. I.e. gated on the project level.

Just wondering how we detect deploy failures?

Yes, at least I get email about it. Also, even if nobody listens, we are no worse off than right now -- every now and then the pilot updates it manually, and then on https://github.com/cockpit-project/cockpituous/actions/workflows/build-tasks.yml we see the failures.

Sounds good, I just don't want the burden of keeping track of this to fall all on you. So I'll try to keep an eye and put it on the pilot board when relevant.

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.

2 participants