- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello,
I would like to state that the initial process for Provisioning and Building an image might take some time because to pull the image, you would need to access ECR endpoint, login to ECR, get the image, then download the image. So it would require a short amount of time to do that.
Coming on to the testing steps for the build. The test case for the build to run might short amount of time or a long amount of time depending on the test cases. For example if you just have ECR login as a test then it would short amount of time. However, if your build contains a chain of command and use-case which need to be validated or run in order to get an output, then it might take more time for the total build to complete.
It also depends on the source code repo, whether the test is being performed on the source code or not. This might also be related to the long wait time for build.
Please refer the following document on how to Improve Build Performance and Save Time Using Local Caching in AWS CodeBuild: [+] https://aws.amazon.com/blogs/devops/improve-build-performance-and-save-time-using-local-caching-in-aws-codebuild/
Note - Please refer to the type of caching best suited for your use-case.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
AWS OFFICIELA mis à jour il y a 8 mois- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Hello, The initial state I meant the very first beginning when I click start build it takes too long to start on the very first command of the pipeline which is not pulling the image or login to ECR it's some other commands, it really takes about 2 mins to start the first command,
and about the testing yeah we use test case scenarios so yeah you're right it may be a code thing,
and about the local caching I have tried it already and nothing differs