Add ci pipeline using cloudbuild to run tests against actual GCS #31
Conversation
Mahalaxmibejugam
commented
Dec 4, 2025
Mahalaxmibejugam
commented
- Adds the ci pipeline configuration
- Anyone with the Cloud Build Approver role needs to approve for the pipeline to run
- Trigger is setup on gcs-aiml-clients-testing-101 GCP project
- This pipeline includes tests on both regional and Zonal buckets
- Logs from the test run would be visible in details section in the Checks tab of the PR
We need a pre setup zonal bucket as we don't have the writes implemented yet for zonal buckets. A bucket will need to be passed through substitution variable containing the required data for tests to run
Only print the errors and redirect standard logs to /dev/null
Instead of hardcoding the github repository to be cloned, use substitution rule so same cloudbuild file can be used for public repo
|
/gcbrun |
ankitaluthra1
left a comment
ankitaluthra1
left a comment
There was a problem hiding this comment.
Anyone with the Cloud Build Approver role needs to approve for the pipeline to run >> Does that mean pipeline wont run for external contributors ?
The pipeline on this PR should pass, correct ? as PR contains the cloudbuild yaml or does it need to be main to be successfull, also why are there 2 pipelines run ?
Pipeline would be in pending state till someone with Cloud Build Approver role approves it. This check was added as a safe guard as anyone with read access to repo can create PRs and it might include unsafe changes to access other resources from the GCP project. Let me know your thoughts if we want to remove this, as we are planning to have a project dedicatedly only for cloud build pipeline.
Yes, pipeline is successful on this PR. There are 2 pipelines runs as we have configured 2 triggers, one for integration tests and another for performance tests. Performance tests trigger failed as the yaml doesn't exist. If you are referring to Trigger: b27861cb-58fb-438e-8293-ed1a94ce3c1b, it is a manual trigger which can be ignored. |
