且构网

分享程序员开发的那些事...
且构网 - 分享程序员编程开发的那些事

没有将环境变量注入到Azure Devops管道上的多阶段Docker构建中

更新时间:2022-06-26 09:39:12

我针对此Dockerfile的最小示例进行了测试

I made a test for minimal example I mean for this Dockerfile

FROM alpine

ARG a_version
RUN echo $a_version

和这个管道

steps:
- pwsh: ls '***/85-docker/'
- task: Docker@2
  inputs:
    containerRegistry: 'devopsmanual-acr'
    command: 'build'
    Dockerfile: '***/85-docker/DOCKERFILE'
    arguments: '--build-arg a_version=$(System.AccessToken)'

我知道了

2020-11-23T15:39:04.0075804Z Step 3/12 : RUN echo $a_version
2020-11-23T15:39:04.0228448Z  ---> Running in 45fc8efb4968
2020-11-23T15:39:04.3523862Z ***

这是正确的,因为它检测到并掩盖了机密.

which is correct because it detected secret and masked it.

如果我将其用于非秘密变量,则我将拥有:

If I run it for nor secret variable I have:

2020-11-23T15:42:10.0106169Z Step 3/12 : RUN echo $a_version
2020-11-23T15:42:10.0288192Z  ---> Running in a59622e31abb
2020-11-23T15:42:10.3746013Z SomeValue123

其中 SomeValue123 是我的管道变量的值

where SomeValue123 is value of my pipeline variable