In order to run specific tests, the developers currently need to push a (potentially empty) git commit with its message containing a specific string: [CodeBuild] for AWS CodeBuild tests and [run-notebook-tests] for note notebook tests.
Various other repositories are using a different mechanism based on GitHub environments to separate different phases of testing or deployments.
In the context of issue #295 this new mechanism has already been applied for executing the notebook-tests.
The current ticket requests to switch to using this new mechanism for executing the AWS CodeBuild, too.
For that, the filter in the AWS webhook (currently COMMIT_MESSAGE) probably needs to be changed to WORKFLOW_NAME.
Situation
In order to run specific tests, the developers currently need to push a (potentially empty) git commit with its message containing a specific string:
[CodeBuild]for AWS CodeBuild tests and[run-notebook-tests]for note notebook tests.Various other repositories are using a different mechanism based on GitHub environments to separate different phases of testing or deployments.
In the context of issue #295 this new mechanism has already been applied for executing the notebook-tests.
The current ticket requests to switch to using this new mechanism for executing the AWS CodeBuild, too.
For that, the filter in the AWS webhook (currently
COMMIT_MESSAGE) probably needs to be changed toWORKFLOW_NAME.References and details
AWS documentation.
Codebuild buildspec.yml should print branch and commit ID initially to enable debugging. See SLC release for an example.
See repos