Skip to content

Comments

Add cron for creating OSS-Fuzz CC groups#5151

Merged
ViniciustCosta merged 11 commits intomasterfrom
feat/add_cron_oss_fuzz_group_issue_cc
Feb 3, 2026
Merged

Add cron for creating OSS-Fuzz CC groups#5151
ViniciustCosta merged 11 commits intomasterfrom
feat/add_cron_oss_fuzz_group_issue_cc

Conversation

@ViniciustCosta
Copy link
Collaborator

@ViniciustCosta ViniciustCosta commented Jan 30, 2026

Cronjob to create and sync the OSS-Fuzz projects' CCs with their respective google groups, which will be used in the issue tracker.

After running this for a couple of times (which will create all the groups for the existing projects and sync them), my plan is to add this step in the project setup and remove this cronjob.

Context: b/477964128, b/388390041, google/oss-fuzz#12945

@ViniciustCosta ViniciustCosta marked this pull request as ready for review February 3, 2026 12:55
@ViniciustCosta ViniciustCosta changed the title Feat/add cron oss fuzz group issue cc Add cron for creating OSS-Fuzz CC groups Feb 3, 2026
Copy link
Collaborator

@javanlacerda javanlacerda left a comment

Choose a reason for hiding this comment

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

It seems great! Could you please deploy it in dev and collect evidences? You would need to create the cronjob entity in the dev config as well.

@ViniciustCosta
Copy link
Collaborator Author

It seems great! Could you please deploy it in dev and collect evidences? You would need to create the cronjob entity in the dev config as well.

This is intended only for oss-fuzz, so deploying it to dev won't work

Also, this does not change any behavior from CF yet. It only creates the groups and add members, so the worst that can happen is the cronjob not finishing

Copy link
Collaborator

@javanlacerda javanlacerda left a comment

Choose a reason for hiding this comment

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

Approving to unblock, but I think we should be able to test this kind of change before landing. Probably implementing in further PRs an end to end tests for project setup?

@ViniciustCosta
Copy link
Collaborator Author

Approving to unblock, but I think we should be able to test this kind of change before landing. Probably implementing in further PRs an end to end tests for project setup?

Thanks!

In this case, I created the feature as a separate cronjob precisely for testing before adding it as a step in the project-setup, so that if this breaks, it does not interfere with any other code.

I agree that it would be great to have an e2e or integration test for project setup in the future, but that should be another task.

@ViniciustCosta ViniciustCosta merged commit fb1c36c into master Feb 3, 2026
11 checks passed
@ViniciustCosta ViniciustCosta deleted the feat/add_cron_oss_fuzz_group_issue_cc branch February 3, 2026 17:24
@google google deleted a comment from cemon721-a11y Feb 4, 2026
javanlacerda pushed a commit that referenced this pull request Feb 4, 2026
Cronjob to create and sync the OSS-Fuzz projects' CCs with their
respective google groups, which will be used in the issue tracker.

After running this for a couple of times (which will create all the
groups for the existing projects and sync them), my plan is to add this
step in the project setup and remove this cronjob.

Context: b/477964128, b/388390041,
google/oss-fuzz#12945
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