Upgrade Drone build file format from 0.8 to 1.x. #187
No reviewers
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#187
Loading…
Reference in New Issue
No description provided.
Delete Branch "upgrade-drone"
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?
Drone 1.x has a completely new file format, and explicit build matrix support is gone.
Is Drone the project doing weird things like this a lot!?
Dunno.. This is the first major Drone upgrade I've been through. Here's more info on the build matrix deprecation: https://docs.drone.io/user-guide/pipeline/migrating/#matrix
As you can see there, they do have a replacement matrix-like feature using jsonnet templating. I started going down that road, only to realize that it doesn't work out of the box and requires running a separate extension to make it work. We could certainly do that in the future, but I didn't want to bite that off as part of the upgrade.
And the related issue where most of the upgrade work was done: witten/provisioning#21