-
Notifications
You must be signed in to change notification settings - Fork 22
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
ci: Add Java Smoke Tests #477
Conversation
edbcb83
to
90aca67
Compare
90aca67
to
91dd5f3
Compare
path: ${{ env.LIBRARY_CHECKOUT_PATH }} | ||
ref: snowpea-build | ||
|
||
- name: Proto Schemas > Checkout Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we could do a single checkout of proto schemas and reuse across all languages?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it's worth the work trying to create a parent job to checkout and have child jobs uses that one source. Are you concerned or just trying to minimize each language setup?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just thinking about avoiding redundant actions and per-language complexity. But agreed, refactoring for that is a good future improvement.
.github/workflows/test_clients.yaml
Outdated
with: | ||
repository: googleapis/google-cloudevents-java | ||
path: ${{ env.LIBRARY_CHECKOUT_PATH }} | ||
ref: snowpea-build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self: remove before merging
path: ${{ env.LIBRARY_CHECKOUT_PATH }} | ||
ref: snowpea-build | ||
|
||
- name: Proto Schemas > Checkout Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just thinking about avoiding redundant actions and per-language complexity. But agreed, refactoring for that is a good future improvement.
No description provided.