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

chore(ci): add Cloud Build failure reporter #41

Merged
merged 2 commits into from
Dec 18, 2024

Conversation

vishwarajanand
Copy link
Collaborator

This should create cloud build failure notifications like this:

If nightly test suite run is found
--When a test suite fails
----If there’s an open issue:
------Comment on open issue
----Else:
------Create an issue
Else:
--Create an issue for no nightly tests found

Reference PRs:

googleapis/langchain-google-alloydb-pg-python#251
And a fix raised here: googleapis/langchain-google-alloydb-pg-python#278

Partially Addresses:

b/367373262

@vishwarajanand vishwarajanand marked this pull request as ready for review December 17, 2024 16:13
@vishwarajanand vishwarajanand requested review from a team as code owners December 17, 2024 16:13
@product-auto-label product-auto-label bot added the api: alloydb Issues related to the googleapis/llama-index-alloydb-pg-python API. label Dec 18, 2024
@averikitsch averikitsch merged commit 228c50c into main Dec 18, 2024
8 checks passed
@averikitsch averikitsch deleted the cloud-build-failure-notifications branch December 18, 2024 19:29
dishaprakash pushed a commit that referenced this pull request Jan 7, 2025
* chore(ci): add Cloud Build failure reporter

* chore: refer to langchain alloy db workflow
dishaprakash added a commit that referenced this pull request Jan 7, 2025
* feat: Adding Async Chat Store

* Removed user and password from tests

* Linter fix

* Added docstrings.

* chore(deps): update dependency google-cloud-alloydb-connector to v1.6.0 (#39)

Co-authored-by: Averi Kitsch <[email protected]>

* chore(ci): add Cloud Build failure reporter (#41)

* chore(ci): add Cloud Build failure reporter

* chore: refer to langchain alloy db workflow

* chore(deps): bump jinja2 from 3.1.4 to 3.1.5 in /.kokoro (#42)

Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.4 to 3.1.5.
- [Release notes](https://github.com/pallets/jinja/releases)
- [Changelog](https://github.com/pallets/jinja/blob/main/CHANGES.rst)
- [Commits](pallets/jinja@3.1.4...3.1.5)

---
updated-dependencies:
- dependency-name: jinja2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Made review changes

* Changed header to 2025.

* Changed header to 2025.

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: Averi Kitsch <[email protected]>
Co-authored-by: Vishwaraj Anand <[email protected]>
Co-authored-by: Mend Renovate <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: alloydb Issues related to the googleapis/llama-index-alloydb-pg-python API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants