open-telemetry / open-telemetry/opentelemetry-python
CI Failure on patch release PRs if main branch contains different instrumentations than the release branch
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
It looks like the workflow we are using for the contrib workflow is hardcoded to the main branch:
https://github.com/open-telemetry/opentelemetry-python/blob/main/.github/workflows/contrib.yml#L19
This is a problem if the release branch contains different instrumentations because it'll try to run tox environments that are not available there.
e.g. When preparing the release of 1.39.1 CI tried to run the anthropic tox environments that were added after 1.39.0.
https://github.com/open-telemetry/opentelemetry-python/actions/runs/20134499734/job/57784060744
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/contrib.yml around line 19 and compare how patch release PRs select their branch with the available tox environments on that release branch. Reproduce the failure using the linked CI run or an equivalent release-branch PR, then verify that the workflow runs only environments available from the relevant branch without breaking main-branch CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100