2 個答案
- 最新
- 最多得票
- 最多評論
1
Frequency is not conditional it will trigger the build at the required frequency whether there are changes or not. Is there a particular reason not to build on every commit? It's usually better that a build fails sooner rather than later.
Using a phase within your build spec, for example, pre_build you could run git commands/script to determine if there have been any changes within the last hour. This could set a custom env var which you then use to conditionally wrap the build phase. Additionally, the env var CODEBUILD_RESOLVED_SOURCE_VERSION might allow you to determine if there have been any changes since last build.
已回答 2 年前
0
Using the pre build phase to set env var that's a great idea, will give that a go. Thanks.
已回答 2 年前
相關內容
- AWS 官方已更新 1 年前