CI_BRANCH_TO_TEST interferes with CI_COLCON_BRANCH
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 55
- Forks
- 39
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 7
Description
It seems that when using CI_COLCON_BRANCH, the colcon repositories are cloned into a subdirectory of the workspace. Though colcon itself doesn't consider the subdirectory to be part of the workspace sources, it seems that vcstool does, and attempts to check out CI_BRANCH_TO_TEST in each colcon repository, possibly overriding CI_COLCON_BRANCH.
Contributor guide
No contributing guide indexed for this repository
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 by tracing the CI handling of CI_BRANCH_TO_TEST and CI_COLCON_BRANCH, then inspect how vcstool discovers repositories under the workspace and how colcon places them. Reproduce a run with both variables set; done means the colcon repositories retain CI_COLCON_BRANCH while CI_BRANCH_TO_TEST does not override them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100