Skip to content

chore: add test for new client generation - #8670

Merged
meltsufin merged 24 commits into
mainfrom
gh-action-newclient
Oct 27, 2022
Merged

meltsufin merged 24 commits into
mainfrom
gh-action-newclient

Conversation

@meltsufin

@meltsufin meltsufin commented Oct 23, 2022 •

Copy link
Copy Markdown
Contributor

Fixes: #8659

@meltsufin
meltsufin force-pushed the gh-action-newclient branch 2 times, most recently from a8da0ea to 80d3706 Compare October 23, 2022 21:33
@meltsufin
meltsufin force-pushed the gh-action-newclient branch from f74563f to d1d9dd2 Compare October 24, 2022 01:29
@meltsufin meltsufin changed the title chore: add test for new client generation chore: add test for new client generation [BLOCKED] Oct 24, 2022
@suztomo

suztomo commented Oct 24, 2022

Copy link
Copy Markdown
Member

because the repository is private.

How about yoshi-code-bot account? https://github.com/googleapis/google-cloud-java/blob/main/.github/workflows/readme.yaml#L35 (I don't know its entitlement)

@meltsufin

Copy link
Copy Markdown
Contributor Author

because the repository is private.

How about yoshi-code-bot account? https://github.com/googleapis/google-cloud-java/blob/main/.github/workflows/readme.yaml#L35 (I don't know its entitlement)

Doesn't seem to be working either.

@meltsufin meltsufin added the owlbot:run Add this label to trigger the Owlbot post processor. label Oct 24, 2022
@gcf-owl-bot gcf-owl-bot Bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Oct 24, 2022
@meltsufin
meltsufin force-pushed the gh-action-newclient branch from 123c243 to 40cd445 Compare October 26, 2022 03:46
@meltsufin meltsufin changed the title chore: add test for new client generation [BLOCKED] chore: add test for new client generation Oct 26, 2022
@meltsufin
meltsufin marked this pull request as ready for review October 26, 2022 22:49
@meltsufin
meltsufin requested a review from suztomo October 26, 2022 22:49
Comment on lines +49 to +58
- name: Push to branch
run: |
[ -z "`git config user.email`" ] && git config --global user.email "${USERNAME:-script}@google.com"
[ -z "`git config user.name`" ] && git config --global user.name "${USERNAME:-script}"
git checkout -b newclient_output_${{ github.event_name }}
git add --all
git commit -m 'feat: re-generated apikeys'
git remote add monorepo https://${{ github.actor }}:${{ github.token }}@github.com/${{ github.repository }}.git
git fetch -q --unshallow monorepo
git push -f monorepo newclient_output_${{ github.event_name }}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does "Push to branch" help verify the behavior of new-client.py?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's just there for debugging, in case the job fails.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's helpful. Nice.

Comment thread .github/workflows/newclient.yaml
Comment thread .github/workflows/newclient.yaml
Comment thread .github/workflows/newclient.yaml
@suztomo

suztomo commented Oct 27, 2022

Copy link
Copy Markdown
Member

How might we verify new-client.py’s logic of adding a corresponding new entry to gapic BOM, release please configuration files, and the root pom.xml?

@meltsufin
meltsufin requested a review from suztomo October 27, 2022 17:16
@meltsufin
meltsufin merged commit 7a0fa4d into main Oct 27, 2022
@meltsufin
meltsufin deleted the gh-action-newclient branch October 27, 2022 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a Github Action check for new-client.py

2 participants