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

metrics(ci): create a metrics deployment specifically for CI smoke tests #9148

Closed
Maddiaa0 opened this issue Oct 10, 2024 · 3 comments
Closed
Assignees
Labels
C-CI Component: continuous integration

Comments

@Maddiaa0
Copy link
Member

Overview

When we run the smoke cluster and it fails, we are running without a metrics deployment, so we lose logging.

We should have a second metrics deployment that collects logs from the ci jobs.

  • we can use some ci secret to authenticate access
@Maddiaa0 Maddiaa0 added this to the Sequencer & Prover Testnet milestone Oct 10, 2024
@Maddiaa0 Maddiaa0 added this to A3 Oct 10, 2024
@github-project-automation github-project-automation bot moved this to Todo in A3 Oct 10, 2024
@Maddiaa0 Maddiaa0 added the C-CI Component: continuous integration label Oct 10, 2024
@ludamad
Copy link
Collaborator

ludamad commented Oct 10, 2024

My idea for this was quite simple, have additional GitHub action jobs that just echo the logs

@ludamad
Copy link
Collaborator

ludamad commented Oct 10, 2024

We can already run on the same runner then it's just kubectl

@ludamad
Copy link
Collaborator

ludamad commented Oct 10, 2024

Actually even simpler, we can just have a bg process in the ci job that echoes the logs while the test runs

@Maddiaa0 Maddiaa0 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Oct 10, 2024
@iAmMichaelConnor iAmMichaelConnor removed this from A3 Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-CI Component: continuous integration
Projects
None yet
Development

No branches or pull requests

3 participants