reduce /gcbrun skip time

[DavidKorczynski]

When we dont need a trial run for a PR we use /gcbrun skip. However, there is still a lot of processing time for this workflow. We should reduce this.

[KKSurendran06]

Hi @DavidKorczynski

I looked into this issue and noticed that /gcbrun skip does not currently prevent all processing. Specifically:

There are no checks for /gcbrun skip in pypresubmit.yaml or in the helper/ scripts (presubmit and py_presubmit.py).

To address this, I’m considering two possible fixes:

1. Modify pypresubmit.yaml to completely skip the job if /gcbrun skip is in the PR body:
   if: "!contains(github.event.pull_request.body, '/gcbrun skip')"

2)Modify py_presubmit.py to exit early if /gcbrun skip is detected in the PR message:

pr_message = subprocess.check_output(['git', 'log', '-1', '--pretty=%B']).decode()
if "/gcbrun skip" in pr_message:
    print("Skipping Python presubmit checks due to /gcbrun skip")
    return 0 

Would this be the correct approach? Or should only specific parts of the process be skipped rather than the entire presubmit check?

I’d love to contribute a PR for this, any guidance would be greatly appreciated

Thanks!

[DavidKorczynski]

option 1 sounds good to me. I'm not sure it's the best option for you to contribute this, since controlling running the CI requires a certain level of permission. Perhaps it's smarter to work on something you can actively test? For example, wider support for build systems in https://github.com/google/oss-fuzz-gen/tree/main/experimental/c-cpp is appreciated

[KKSurendran06]

Hi @DavidKorczynski

Thanks for pointing me to the experimental/c-cpp directory! After reviewing the code, I’ve identified a few areas where I could contribute:

• Adding support for more build systems beyond Make, CMake, and Autotools.
• Improving detection heuristics to better recognize project structures.
• Enhancing error handling and debugging for more useful logs and failure insights.

I’ll start by debugging and improving logging while getting familiar with the codebase.

Are there any open issues or a TODO list related to build system improvements that I could work on? If not, could you guide me on where to start looking for areas that need improvement?

Also, is there a Discord, Slack, or another discussion channel where contributors can ask questions and stay updated?

Thanks!