feat: crane-backed derivations! #6
No reviewers
Labels
No labels
⚠️Priority
A (Highest)
⚠️Priority
C (High)
⚠️Priority
D (Medium-High)
⚠️Priority
E (Medium)
⚠️Priority
G (Low)
⚠️Priority
H (Lowest)
🏷️Kind
Bug
🏷️Kind
Chore
🏷️Kind
Documentation
🏷️Kind
Epic
🏷️Kind
Feature
🏷️Kind
Improvement
🏷️Kind
Task
🏷️Kind
Testing and CI
👁️Reviewed
Duplicate
👁️Reviewed
Invalid
👁️Reviewed
Under Discussion
👁️Reviewed
Valid
👁️Reviewed
Won't Fix
📋️Kind/Security
📋️Status
Abandoned
📋️Status
Blocked
📋️Status
In Progress
📋️Status
Need More Info
🔧Difficulty
A (Very hard)
🔧Difficulty
B (Hard)
🔧Difficulty
C (Medium)
🔧Difficulty
D (Easy)
🔧Difficulty
E (Trivial)
Compat
Breaking
Good First Issue
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
polyphony/workflows!6
Loading…
Reference in a new issue
No description provided.
Delete branch "flori/crane2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've been meaning to do this for a while: We now use crane to get drvs for all dependencies in a project. This way, dependencies can be built once and then cached in attic. Restoring the dependencies from attic before building in CI again means, that you do not have to build them again. yay!
Tested in PR: https://codeberg.org/polyphony/polyproto-rs/actions/runs/797/jobs/0/attempt/1