Is it possible to stop a 'Queued - Waiting to run this check...' in Google Cloud Build Integration?

[estellise-yukihime]

A few days ago, I integrated a Google Cloud Build to automate the build and deployment of the web application. The integration was successful and was even able to fail a few times, something happened along the way that it got stuck in the 'Queued -Waiting to run this check...' and the build was never triggered on the GCP side.

This is probably the cause, when I was doing the integration and testing the trigger, the other dev made some changes to the branch ruleset and when I pushed it to the branch, it got stuck on this queue. Deleting the branch ruleset fixes the subsequent triggers, but somehow two commits still got stuck in this queue.

Is It possible to stop this queue check and how? and would this get billed by GitHub?

[tahmidbintaslim]

Stopping a Stuck Build in Google Cloud Build

1. Check the Google Cloud Console: The first step is to visit the Google Cloud Console and navigate to the Cloud Build section. Here, you should be able to see all the builds that have been triggered, including those that are currently queued, running, or have completed/failed.

2. Cancel the Build: If you identify the stuck build in the Google Cloud Console, you should be able to cancel it manually. Look for an option to cancel or stop the build. This action should remove the build from the queue and stop any further actions from being taken on it.

3. Investigate the Cause: Since you mentioned that changes to the branch ruleset might have contributed to the issue, ensure that no configurations are currently in place that could inadvertently block or delay builds. Sometimes, webhook configurations or branch protection rules might interfere with the triggering of builds.

4. Contact Support: If you're unable to resolve the issue through the Google Cloud Console or if the stuck build does not appear there, consider reaching out to Google Cloud Support. There might be underlying issues with the Cloud Build service or your specific project that require intervention from their side.

GitHub Billing Concerns

• Google Cloud Build Billing: Typically, billing for Google Cloud Build is based on the computing resources consumed during the build process. If a build is stuck in a queue and not actually running, it should not consume resources that would lead to charges. However, it's important to review Google Cloud's billing documentation or contact their support for confirmation based on your specific billing plan.

• GitHub Billing: Since the issue is with a build not triggering on the Google Cloud side, billing concerns on GitHub would largely relate to any actions or services on GitHub's end that are priced (e.g., GitHub Actions minutes for private repositories). If the build was never triggered, then GitHub Actions (if used) would not have been initiated, and thus, there should be no impact on billing related to this specific issue.

In summary, you should be able to manually stop a queued build through the Google Cloud Console. For builds that are stuck due to configuration issues, rectifying these configurations and contacting support if necessary are your best courses of action. Billing should not be impacted for a build that has not consumed resources, but always consult the specific services' billing documentation or support for detailed insights.

[estellise-yukihime]

I have thoroughly checked the Cloud Build in Google Cloud Console and there is no build triggered or queued around the time the run check stuck.

Thank you, I will contact Google Cloud support and GitHub support as well.

[majiangqin]

Do you resolve this problem? I have the same issues.

[tahmidbintaslim]

Yes, you can follow my instructions @majiangqin or you are unable to fix, you can always contact the Google Support to clear the queue for you

[majiangqin]

Thank you for your advice. The google support only provides limited service. So I configured the Cloud Build trigger for 'Manual invocation'. When I executed the trigger manually, it revealed multiple issues. For instance, there were problems with my cloudbuild.yaml configuration, and I had to enable the IAM API, which I've done through the provided link. Additionally, I was reminded that Cloud Build is only available in certain regions. I have now addressed these problems. Any way, configuring the Cloud Build trigger for 'Manual invocation' is the most important, it will show what problem you have.