Codeberg-CI/feedback
488
71

Is "pull: true" necessary? #287

Closed
opened 2025年12月07日 19:13:14 +01:00 by mathisdt · 2 comments

I created a build helper image to speed up my builds (packages were installed onto ubuntu:noble in every pipeline run, which was a waste of resources).

Now I want to use it in my other builds and was wondering if I have to add pull: true for the build helper image to be updated after I rebuild it once a month. Is there a cache policy for images on Woodpecker? If so, how long are images kept and not re-fetched?

I created a **build helper image** to speed up my builds (packages were installed onto `ubuntu:noble` in every pipeline run, which was a waste of resources). Now I want to use it in my other builds and was wondering if I have to add `pull: true` for the build helper image to be updated after I rebuild it once a month. Is there a cache policy for images on Woodpecker? If so, how long are images kept and not re-fetched?

@mathisdt wrote in #287 (comment):

Is there a cache policy for images on Woodpecker

To my knowledge, none.

@mathisdt wrote in #287 (comment):

for the build helper image to be updated after I rebuild it once a month.

Yeah if the tag doesn't changes then pull: true is necessary as the image will not be deleted from cache. Another option would be to publish the build image with a newer tag and then use something like https://docs.renovatebot.com/ to update the tag in all the repository you use this to the newer tag.

@mathisdt wrote in https://codeberg.org/Codeberg-CI/feedback/issues/287#issue-2831784: > Is there a cache policy for images on Woodpecker To my knowledge, none. @mathisdt wrote in https://codeberg.org/Codeberg-CI/feedback/issues/287#issue-2831784: > for the build helper image to be updated after I rebuild it once a month. Yeah if the tag doesn't changes then `pull: true` is necessary as the image will not be deleted from cache. Another option would be to publish the build image with a newer tag and then use something like https://docs.renovatebot.com/ to update the tag in all the repository you use this to the newer tag.
Author
Member
Copy link

@Gusted Thank you, that helps a lot!

The tag should stay "latest", so I'll include pull: true. I already use Renovate for dependency updates, but I don't want one PR every month for every project just to use the current build helper image.

@Gusted Thank you, that helps a lot! The tag should stay "latest", so I'll include `pull: true`. I already use Renovate for dependency updates, but I don't want one PR every month for every project just to use the current build helper image.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg-CI/feedback#287
Reference in a new issue
Codeberg-CI/feedback
No description provided.
Delete branch "%!s()"

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?