Ah, I don't know enough about codebuild to know if this is a breaking change - can people self host?

Ah, I don't know enough about codebuild to know if this is a breaking change - can people self host?

Yes, we can.
We are using codebuild.
It is working.

If you can self-host then there may be cases where this new code breaks old builds - any chance you can make it backwards compatible? e.g. prioritise the new ENV vars but still keep the old ones working

@orta
For safety, if you want to keep the old ones working, I can implement it.

CODEBUILD_BATCH_BUILD_IDENTIFIER environment variable seems to be able to determine the mode of the code build, so use this to maintain backward compatibility.

@orta
Or is it better to have backward compatibility with a new environment variable that is not a CODEBUILD_BATCH_BUILD_IDENTIFIER environment variable?

If so, what is the better name for the new environment variable?

Yep, keep CODEBUILD_WEBHOOK_TRIGGER working if CODEBUILD_WEBHOOK_TRIGGER is not present

@orta
CODEBUILD_WEBHOOK_TRIGGER environment variable always returns a value at coudebuild when created PR.(ex pr/121)

CODEBUILD_BATCH_BUILD_IDENTIFIER returns a value only with batch build(ex build1)

I implement it has backward compatibility depending on the present CODEBUILD_BATCH_BUILD_IDENTIFIER.
Please review 🙇

Looks great, sorry of the delay!