PointCloudLibrary / PointCloudLibrary/pcl
[CI] new CI that covers uncommon build configurations
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 4.7k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 6
Description
An idea for a new CI (this was discussed a few times in comments of other issues or PRs):
Build and test PCL with less-common build configurations, e.g.:
- C++17 or C++20 instead of C++14
- other values for
CMAKE_BUILD_TYPE - non-default versions of VTK, CMake, Eigen, etc.
- ...
Covering all possible combinations is probably not doable, maybe we could choose a few random combinations for each run.
This CI could run maybe weekly or monthly. Running it for every PR does not seem feasible because of PCL's long build time.
We could add a badge to the README to increase visibility of failures.
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
The issue names no specific files, tests, or CI entry points. Start by reviewing the repository's existing CI and build configuration, then define a limited set of uncommon configurations and a weekly or monthly schedule; done means those builds and tests run reliably and the README exposes failures with a badge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100