open-telemetry / open-telemetry/opentelemetry-python

infra: reduce toil of manually sync workflows between contrib and core (generate-workflows-lib)

Open
#4,263 1 comment 0 reactions 1 assignee View on GitHub

@emdneto is already working on this.

Since Nov 8, 2024.

build & infra discussion
Dominant language
Python
Stars
2.6k
Forks
1k
Avg merge
4d 15h
Merged PRs (30d)
19

Description

Frequently we face situations when we change tox.ini in contrib (e.g., adding a new env or instrumentation or fixing a env name) we are required to manually update workflows in core as well (we need this to test core changes don't break contrib). Here are some PRs:

https://github.com/open-telemetry/opentelemetry-python/pull/4258
https://github.com/open-telemetry/opentelemetry-python/pull/4256
https://github.com/open-telemetry/opentelemetry-python/pull/4239
https://github.com/open-telemetry/opentelemetry-python/pull/4192
https://github.com/open-telemetry/opentelemetry-python/pull/4158

Maybe there's a better way to do that without the need to wait someone deal with a broken PR in core because tox -e generate-workflows is failing in CI.

Right now, the solution is: we need to manually fix workflows (i.e., run tox -e generate-workflows locally) and commit the changes (this is the process for keep workflows synced between -core and -contrib).

  1. We need to have this explicit in documentation as well.
  2. Investigate better way to automate this.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.