action: Enable cache #1269
No reviewers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1269
Loading…
Reference in a new issue
No description provided.
Delete branch "achuprov/frostfs-node:feat/make_Forgejo_more_great"
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?
Signed-off-by: Alexander Chuprov a.chuprov@yadro.com
Can you please clarify, why are you enabling cache in actions?
Please, use the
.forgejo:
prefix, see git history for examples.This will decrease server load noticeably.
7d0cec95b0
to13a69afd19
13a69afd19
tof25b601e0a
The motivation for change should be in the commit message, not in the form of
+1
to a message.This change directly affects actions, so I will not merge this until they are red.
706b88f6b3
tof25b601e0a
@elebedeva
Enabling caching will save runner resources. However,, enabling caching seems to make the test more flaky (See: https://git.frostfs.info/TrueCloudLab/frostfs-node/actions/runs/9489/jobs/0 or https://git.frostfs.info/TrueCloudLab/frostfs-node/actions/runs/9460/jobs/1). Let's wait for update from Forjejo before turning this feature on.
Pull request closed