That output looks like it's coming from your Beanstalk environment, so the good news is that your CI/CD pipeline appears to be working correctly.
It looks like you have a prebuild hook in your application bundle which is failing. Check for
.platform/hooks/prebuild/01login.sh in your repo, it appears that lines 2 and 3 of this script are trying to run an
environment command, but there is no such command on the Beanstalk instance. Is it possible that this script should instead be using the
env command (1)?
Setting up Beanstalk with Gitlab CI/CD fails when executing .sh scripts for gitlab registry user authenticationasked 9 months ago
Using tags with spaces with cloudformation deployasked 4 years ago
Elastic Beanstalk npm install fails without error messageAccepted Answerasked 6 months ago
Elastic Beanstalk failed to unzip source file with UTF-8 file nameasked 8 months ago
How to get GitLab like Analytics with CodeCommit?asked 9 months ago
Deploying .NET with Beanstalk: must include '.runtimeconfig.json'asked 2 years ago
Forbbiden 403 access denied with AWS SSO SAML application from Gitlab integrationAccepted Answerasked 6 months ago
How can we connect a Sagemaker Studio user to a gitlab repo within a private VPN?Accepted Answerasked 8 months ago
Does Sagemaker support private GitLab repos?asked 5 months ago
SageMaker Pipelines and CI/CD with GitLab Multiaccountasked 4 months ago