aws-codebuild-run-build icon indicating copy to clipboard operation
aws-codebuild-run-build copied to clipboard

Cannot read property 'split' of undefined

Open aolds01 opened this issue 3 years ago • 10 comments

We have a GitHub Action which utilizes aws-actions/aws-codebuild-run-build. We have been using this for the past 6 months in a few different repos. Yesterday (7/8/22) at around 2pm CST the action started failing with an error STARTING CODEBUILD Error: Cannot read property 'split' of undefined CODEBUILD COMPLETE All of our repos utilizing this action are experiencing the same error. The CodeBuild project in AWS is triggered and runs successfully, however, the workflow in GitHub fails.
We are using v1 in one of our repos and v1.0.3 in another one of our repos. Both experience the same error.
We are using self hosted runners in one of the repos and ubuntu-latest from GitHub runners in another repo. Both experience the same error

aolds01 avatar Jul 09 '22 13:07 aolds01

Was facing the same issue so I submitted a PR to fix it #99. It was literally breaking all our CI checks lol.

Canas avatar Jul 10 '22 18:07 Canas

Any updates on this? I have a support ticket open with AWS and all of our builds are suddenly failing due to this issue. Theres been radio silence on this. Thinking about just moving to plain github actions or travis or something

ThrowsException avatar Jul 13 '22 15:07 ThrowsException

I have a support ticket open with AWS as well. I have not gotten any resolution yet. We had to implement manual workarounds in our pipeline to deal with the error coming back which is definitely not ideal

aolds01 avatar Jul 13 '22 15:07 aolds01

@aolds01 Were you able to get this github actions that were triggered to pass despite the error? right now all our fail but were just manually checking the runs in codebuild before merging PRs. Can you add something to the action or the codebuild job to make github report it as passing?

ThrowsException avatar Jul 13 '22 15:07 ThrowsException

@ThrowsException - We added continue-on-error: true to the step in our action to have GitHub always report it as success and continue on with subsequent steps. However, we still need to manually inspect CodeBuild outcome for failures. In the case of failures we have to manually revert the github repo, etc. Definitely not ideal but a workaround while this is broken

aolds01 avatar Jul 13 '22 15:07 aolds01

Hey, thanks for raising awareness about this issue--we identified a recent change that deployed to a couple regions which was causing the problem and have rolled it back. We'll update the CodeBuild action before rolling forward.

leoherran-aws avatar Jul 13 '22 16:07 leoherran-aws

Thanks @leoherran-aws ! I can confirm it's working for us now

aolds01 avatar Jul 13 '22 17:07 aolds01

@leoherran-aws - This issue started occurring again this afternoon. Did the change get deployed again prior to making the necessary updates to the CodeBuild action?

aolds01 avatar Jul 19 '22 20:07 aolds01

Also saw this briefly pop again this afternoon in us-east-2. Seemed intermittent, rerunning the action passed.

ThrowsException avatar Jul 20 '22 00:07 ThrowsException

Hey guys. I see that GitHub Action is not supported last few months. If you really need a quick solution, I can offer to you use the dark-mechanicum/aws-codebuild instead. Try this, and in case of some issues, I can help you to resolve them.

akazakou avatar Jul 23 '22 11:07 akazakou