- Le plus récent
- Le plus de votes
- La plupart des commentaires
Is this account recently provisioned, if so, can you please launch an ec2 instance(t2.micro) for few minutes and then terminate it. Try running the codebuild after that, it should work fine then.
Also, be noted that codebuild scales based on customer build requests coming. It may be possible that capacity might not be available at given point of time and in that case codebuild puts the build request into queue and wait for additional capacity to be available in the build fleet(ie. on-demand). Once capacity becomes available, it starts processing the queued build request.
I'd also suggest you to check build concurrency limit from codebuild service quota page.
Hope you find this useful.
Comment here if you have additional questions, happy to help.
Abhishek
Hi, Its not provisioned recently, instead atleast 10-12 months old. All the builds were running without any issues till yesterday. I have tried creating ec2 instance which is working fine without any issues. But even then my pipelines are still stuck at build stage and what i can see is same QUEUED message from the logs.
Can you create a sample/test build in another region and try to run it?
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 6 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Do you have support plan through which you can create technical support case? I found another user facing same issue and was resolved with the help of AWS Support team. Please take a look at this thread.