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

ci: log errors caused by deployment or infrastructure issues #4090

Closed
gustavovalverde opened this issue Apr 11, 2022 · 0 comments · Fixed by #4252
Closed

ci: log errors caused by deployment or infrastructure issues #4090

gustavovalverde opened this issue Apr 11, 2022 · 0 comments · Fixed by #4252
Assignees
@gustavovalverde
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles A-infrastructure Area: Infrastructure changes C-enhancement Category: This is an improvement I-integration-fail Continuous integration fails, including build and test failures

Comments

@gustavovalverde
Copy link
Member

Motivation

Sometimes CI fails because of a deployment or infrastructure issue, but this issues are hard to track if we don't show those in the logs, at least to know that the same issue is causing multiple checks to fail, like the one from the screenshot below, which has been causing multiple failures in the past week, and re-running after an specific time fixes the issue

image

Examples:

Designs

  • If reading the container logs fails, add further information to the PR (annotations?) to understand what's causing it
@gustavovalverde gustavovalverde added A-infrastructure Area: Infrastructure changes A-devops Area: Pipelines, CI/CD and Dockerfiles C-enhancement Category: This is an improvement S-needs-triage Status: A bug report needs triage I-integration-fail Continuous integration fails, including build and test failures labels Apr 11, 2022
@gustavovalverde gustavovalverde self-assigned this Apr 11, 2022
@ftm1000 ftm1000 removed the S-needs-triage Status: A bug report needs triage label Apr 11, 2022
gustavovalverde added a commit that referenced this issue Apr 12, 2022
@gustavovalverde
imp(ci): test full sync when pushing to main
26565f6 
This will allow faster merges to main, and reduce the considerably when a CI fails because of deployment or infrastructure bugs.

This is a temporal fix.

Related: #4090
This was referenced Apr 12, 2022
Closed
Open
@gustavovalverde gustavovalverde mentioned this issue May 3, 2022
Merged
3 tasks
@mergify mergify bot closed this as completed in #4252 May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gustavovalverde gustavovalverde

Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles A-infrastructure Area: Infrastructure changes C-enhancement Category: This is an improvement I-integration-fail Continuous integration fails, including build and test failures
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

refactor(ci): use docker instead of Konlet for GCP deployments in CI ZcashFoundation/zebra
3 participants
@teor2345 @gustavovalverde @ftm1000