Create a CI job that builds without the lockfile
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
### Is your feature request related to a problem or challenge?
I recently filed https://github.com/apache/datafusion/issues/20756 which was not detected by any CI jobs because they all use the lockfile and it was locked to substrait version 0.62.2.
### Describe the solution you'd like
In lance, to gain a balance of lockfile convenience (better CI caches, reproducible builds, etc.) without missing issues like this, we have one CI job that builds without the lockfile and just verifies that things compile. We could do this same thing in Datafusion.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by reviewing the existing DataFusion CI jobs and the commands they use with the lockfile, then compare the lockfile-free build approach described from lance. Add a CI job that builds without the lockfile and verifies compilation; done means the new job runs successfully alongside the existing lockfile-based jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100