Merged
Conversation
phil-davis
force-pushed
the
use-docker-buildkit-secret
branch
from
82f83e5 to
cffe84a
Compare
phil-davis
force-pushed
the
use-docker-buildkit-secret
branch
from
cffe84a to
a1472c1
Compare
DeepDiver1975
approved these changes
May 2, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use the "secrets" functionality of docker buildkit to pass in the authentication for the Freexian deb package server.
The drone secrets are put into temporary files that are passed into
owncloudci/drone-docker-buildxand are used there to access the Freexian deb package server. Those files are discarded at the end of the CI pipeline, they do not end up in the published image details.