Make CI faster #57
No reviewers
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#57
Loading…
Reference in a new issue
No description provided.
Delete branch "trinity-1686a/garage:improve-ci"
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?
Analysing CI logs, it seems to be doing nothing really useful a considerable part of the time :
Registry download can be avoided by keeping cargo home from one step to the next, and the restore-cache makes sure to prime the cache so the (which it currently doesn't really do as /drone/cargo get discarded between steps). This is what this pr implements.
apt/pip/rustup can be not run at all during CI by making a docker image with the required dependancies, with a dockerfile looking like (untested)
This is not implemented here as it needs the image to get pushed to docker-hub (or a custom registry), which should probably be done with a user named after either the project, or the organisation developing it (garage or deuxfleurs).
These changes requires renewing signature for
.droneci.yml