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.

Sign up for GitHub

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

Jump to bottom

Update GCP Pipeline Zone #377

Open
neelanjan00 opened this issue May 17, 2022 · 0 comments · May be fixed by #379
Open

Update GCP Pipeline Zone #377

neelanjan00 opened this issue May 17, 2022 · 0 comments · May be fixed by #379
Assignees
@neelanjan00
Labels
bug Something isn't working

Comments

@neelanjan00
Copy link
Member

To avoid resource bottlenecking in a single zone, the pipeline can be updated to use a different zone than us-central1-a.
@neelanjan00 neelanjan00 self-assigned this May 17, 2022
@neelanjan00 neelanjan00 added the bug Something isn't working label May 17, 2022
@neelanjan00 neelanjan00 linked a pull request May 17, 2022 that will close this issue
Open
23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@neelanjan00 neelanjan00

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

GCP Pipeline Fixes neelanjan00/litmus-e2e
1 participant
@neelanjan00