- 最新
- 投票最多
- 评论最多
Hi, I would recommend to use AWS CodeBuild action EnvironmentVariables
configuration parameter for values originating from the prior pipeline stages. See Example: Use a BranchName variable with CodeBuild environment variables. Values that do not depend on prior pipelines stages can be set as EnvironmentVariables (a different configuration with the same name) on the CodeBuild project directly. FYI, it is also mentioned in AWS CDK documentation for environmentVariables property of CodeBuildActionProps
interface.
Hi, thank you for your response!
Indeed this was the solution that I ended up employing, but only due to lack of better alternatives.
Originally I had a single CodeBuild
project, and I injected different variables into it through CodePipeline
based on the environment. I had a single CodeBuild
project and multiple (staging
, production
, etc) CodePipeline
pipelines. In the new setup, in order to accommodate more variables, I had to create multiple CodeBuild
projects, one for each environment. Is this the end of the world? No, of course not. But I don't think it's ideal, and it shouldn't be too hard to just raise the size limit of this one property, should it?
相关内容
- AWS 官方已更新 1 年前