You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First thanks for making this tool, it's so useful and saving me a lot of time.
I am using GitLab's project-level secure files feature. Essentially you add an extra step to your build process and secure files (uploaded separately in GitLab UI) magically appear in $CWD/.secure_files during the CI build. This only works on the real GitLab runner of course as an auth token they inject has to be present to fetch the secure files.
My first thought to make this work with gitlab-ci-local is to use an extra volume (I am using container builds):
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
First thanks for making this tool, it's so useful and saving me a lot of time.
I am using GitLab's project-level secure files feature. Essentially you add an extra step to your build process and secure files (uploaded separately in GitLab UI) magically appear in
$CWD/.secure_files
during the CI build. This only works on the real GitLab runner of course as an auth token they inject has to be present to fetch the secure files.My first thought to make this work with
gitlab-ci-local
is to use an extra volume (I am using container builds):gitlab-ci-local --volume "/path/to/local/secure/files/:/gcl-builds/.secure_files/:ro"
...then in my build I make sure to skip the secure files download if the dir already exists:
I couldn't find any existing discussion of secure files here so thought I drop this note in case it helps someone else or there's a better way?
Beta Was this translation helpful? Give feedback.
All reactions