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

Schedule recurring CI cron job #98

Merged
merged 2 commits into from
Dec 19, 2022
Merged

Schedule recurring CI cron job #98

merged 2 commits into from
Dec 19, 2022

Conversation

ajnelson-nist
Copy link
Member

This will have the benefit of catching when an upstream updated package introduces a compatibility issue.

This cron job should trigger to leave notices for maintainers on the US East Coast to see on their Tuesday mornings.

PR Note: This will probably fail CI on its first pass, due to a recent update to NumPy that removed Python 3.7 support. That will be addressed in a separate PR.

This will have the benefit of catching when an upstream updated package
introduces a compatibility issue.

This cron job should trigger to leave notices for maintainers on the US
East Coast to see on their Tuesday mornings.

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
@ajnelson-nist ajnelson-nist added this to the 0.10.0 milestone Dec 19, 2022
@ajnelson-nist
Copy link
Member Author

This PR will be ready to leave draft status once #99 is merged.

@ajnelson-nist ajnelson-nist marked this pull request as ready for review December 19, 2022 21:27
@ajnelson-nist ajnelson-nist requested a review from a team as a code owner December 19, 2022 21:27
@ajnelson-nist
Copy link
Member Author

Feedback is welcome on whether we'd like this canary.

@kchason kchason merged commit 9bae915 into develop Dec 19, 2022
@kchason kchason deleted the schedule_regular_ci branch December 19, 2022 21:33
@ajnelson-nist
Copy link
Member Author

For our awareness - this didn't fire this morning. I suspect that is because the repository's primary branch needs to have the cron entry in its actions YAML file.

Over on the case_gnu_time repository, the scheduled job did fire because I'd made a release yesterday:

https://github.com/casework/CASE-Implementation-GNU-Time/actions/runs/3737787589

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