Our project is being built by Docker CLoud autobuild CI and I need to pass a few ENVs to the build sequence, so the public assest will be deployed on the AWS S3.
We have a few environments (devs/test/production) so I need to specify not only the AWS creds but also the specific bucket and folder which the files should be put to.
There is a build-wise ENV section on the auto-build page, but
- After altering the variables the get hidden and reappear only after the page reload (it must be a UI bug).
- The values don’t seem to be injected in the build system environment (I’ve checked via creating a variable and trying RUN touch $VARNAME / RUN mkdir $VARNAME / RUN echo $VARNAME.
What am I doing wrong? Are the variables besides mentioned in https://docs.docker.com/docker-cloud/builds/advanced/ even allowed in the build process?
What other secure options do I have? I have a couple of builder nodes and at 6 Docker Hub registries being built regularly (all registries are environment-specific, but builder nods are not).
Thanks and have a nice day!