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

[CI:DOCS] Add cirrus-cron retry/monitor jobs #2082

Merged

Conversation

cevich
Copy link
Member

@cevich cevich commented Aug 7, 2023

@cevich
Copy link
Member Author

cevich commented Aug 7, 2023

Note to me: Need to add the e-mail secrets to the repo settings.

Copy link
Collaborator

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

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

ACK.

See #2074 (comment) about the periodic runs on c/image — I’m afraid I’ve made a mess of things.

@mtrmac
Copy link
Collaborator

mtrmac commented Aug 7, 2023

If I understand the situation correctly, we’ve been running the job on main for a long time, but we haven’t been reporting failures or paying attention to them.

If so, LGTM; please merge whenever ready.

@cevich
Copy link
Member Author

cevich commented Aug 7, 2023

I’m afraid I’ve made a mess of things.

It's okay, outside of the git-history, nobody will ever know 😀

If so, LGTM; please merge whenever ready.

Will do, thanks.

@cevich cevich marked this pull request as ready for review August 7, 2023 17:55
@cevich
Copy link
Member Author

cevich commented Aug 7, 2023

Secrets added.

Signed-off-by: Chris Evich <cevich@redhat.com>
@cevich cevich force-pushed the add_cirrus_cron_retry_and_notifications branch from d78f0e5 to 7884e7b Compare August 7, 2023 17:55
@cevich
Copy link
Member Author

cevich commented Aug 7, 2023

force-push: rebased

@cevich cevich merged commit c950225 into containers:main Aug 7, 2023
4 checks passed
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