Execute blueos tests in Gitlab CI
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32
- Forks
- 7
- Avg merge
- 19h 49m
- Merged PRs (30d)
- 14
Description
This issue has no description.
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
The issue provides no file or test entry point. Locate the existing BlueOS test entry point and GitLab CI configuration, then determine how the tests are invoked; done means the BlueOS tests run successfully in GitLab CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, gitlab
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100