Skip to content

move otel-collector to its own repo #137

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
Open
madwort opened this issue Sep 7, 2023 · 3 comments
Open

move otel-collector to its own repo #137

madwort opened this issue Sep 7, 2023 · 3 comments

Comments

@madwort
Copy link
Contributor

madwort commented Sep 7, 2023

  • this has grown a bit & it may now be more convenient to manage in its own repo
  • we recently had an issue where broken tests in an unrelated CI test in the sysadmin repo blocked us from merging an urgent update to otel-collector
@madwort
Copy link
Contributor Author

madwort commented Jan 30, 2025 •
edited
Loading

had exactly this problem this week with #178 (fixed by #181 )

@madwort
Copy link
Contributor Author

madwort commented Feb 5, 2025

alternatively, should we improve CI so that it doesn't run unnecessary tests?

@madwort
Copy link
Contributor Author

madwort commented Mar 13, 2025

One thing is that I think some other parts of the organisation assume a one-to-one mapping from repository to "pieces of software", and so didn't realise that the otel-collector even existed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@madwort