Skip to content
VeraDocs
Back to main site

AWS CodeBuild

Inspect CodeBuild project records.

Plan: Pro57 of 59 operations implemented, 2 failed in testing3Known differences

Starting a build returned HTTP 501 NotIncluded in Vera 1.2.2, because the build engine isn't included, and a Pro license doesn't add it.

Example checked on Vera 1.2.2, 8 November 2026. Each coverage note names its own evidence and date.

Connect

Section titled “Connect”

Activate your license key and start the emulator with the Vera launcher, as in Activate Pro, then run this in a terminal of its own, from an empty scratch directory. It gives the official AWS CLI dummy credentials and a config file of its own, so no AWS account is needed and your own AWS profile isn't touched.

Terminal window
export VERA_ENDPOINT="http://localhost:5003"
export AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test
export AWS_REGION=us-east-1 AWS_DEFAULT_REGION=us-east-1
export AWS_SHARED_CREDENTIALS_FILE=/dev/null
export AWS_EC2_METADATA_DISABLED=true
export AWS_PAGER="" AWS_CLI_AUTO_PROMPT=off
unset AWS_PROFILE AWS_DEFAULT_PROFILE
unset AWS_SESSION_TOKEN AWS_SECURITY_TOKEN
unset AWS_WEB_IDENTITY_TOKEN_FILE AWS_ROLE_ARN AWS_ROLE_SESSION_NAME
unset AWS_CONTAINER_CREDENTIALS_FULL_URI
unset AWS_CONTAINER_CREDENTIALS_RELATIVE_URI
cat > vera-aws-config <<'EOF'
[default]
region = us-east-1
output = json
cli_binary_format = base64
s3 =
    addressing_style = path
EOF
export AWS_CONFIG_FILE="$PWD/vera-aws-config"

When you've finished every example in this terminal, close it and delete vera-aws-config, not before.

Use the AWS CLI’s codebuild commands. The emulator serves the 2016-10-06 API over the AWS JSON protocol, and the examples use us-east-1. In testing of Vera 1.2.0 preview, project and build ARNs had the region local, such as arn:aws:codebuild:local:123456789012:project/docs-example-project, even when requests were signed for us-east-1.

A project needs a service role from the emulator’s IAM. In Vera 1.2.2, project metadata worked with a freshly created role. A role ARN that doesn’t exist isn’t a substitute: CreateProject rejects it as an IAM role that doesn’t exist. This page’s example only lists projects. Starting builds is a separate limit, which a working role doesn’t remove: see Limitations.

Example

Section titled “Example”

List the build projects. This only reads: it creates no resources and no local files, so it needs no cleanup.

Terminal window
aws --endpoint-url "$VERA_ENDPOINT" codebuild list-projects

On an empty emulator it returns no projects:

Output
{ "projects": [] }

Supported features

Section titled “Supported features”
  • Project inventory: ListProjects, as in the example.
  • Project records. In Vera 1.2.2, project metadata worked with a freshly created IAM role.
  • Project and build records, in Vera 1.2.0 preview only. In a separate check of Vera 1.2.0 preview, with an IAM role record that already existed in the emulator, CreateProject, BatchGetProjects, StartBuild, BatchGetBuilds, StopBuild and DeleteProject completed. A started build was a record that had already succeeded, and StopBuild marked it STOPPED. This doesn’t describe Vera 1.2.0-rc.3 or Vera 1.2.2, where starting a build returns NotIncluded.
  • Listed in the earlier implementation inventory; not rechecked against Vera 1.2.0-rc.3: retries, report groups and test reports, code coverage, fleets, sandboxes and command executions, webhooks, source credentials, resource policies and project visibility.

Limitations

Section titled “Limitations”

The main limits are below. A few more apply to every service, and the API coverage notes cover smaller differences.

  • Builds can’t start. In Vera 1.2.2, starting a build returned HTTP 501 NotIncluded, because this release doesn’t include the build engine, and a Pro license doesn’t add it. In Vera 1.2.0-rc.3, StartBuild and StartBuildBatch both returned it. A working IAM role doesn’t remove this separate limit.
  • Builds didn’t run in Vera 1.2.0 preview. With a role record that already existed, a project’s buildspec contained exit 97, yet StartBuild returned its build as SUCCEEDED and COMPLETED at once, with no result from running anything. StopBuild then changed that completed build to STOPPED, and BatchDeleteBuilds didn’t delete it, returning its ID in buildsNotDeleted with BUILD_NOT_FOUND. Don’t use the emulator to test build failures, logs or durations.
  • ARNs had the region local in Vera 1.2.0 preview. Code that reads the region from a project or build ARN got local, not the request’s region.
  • Build infrastructure wasn’t tested. Fleets, reports, sandboxes, webhooks and source credentials weren’t run.

API coverage

Section titled “API coverage”

Every operation in AWS's published 2016-10-06 API (SDK model, botocore 1.43.105), and whether the emulator implements it. Availability combines the earlier implementation inventory with the dated observations below; checking a page's example does not verify every operation. Each note names its evidence first; an observation given without a build or date comes from earlier testing, on 3 November 2026. What the statuses mean

OperationStatusNotes
BatchDeleteBuildsKnown differenceLocal observation: Didn't delete the build StartBuild had just created: its ID came back in buildsNotDeleted as BUILD_NOT_FOUND. Local observation: Vera 1.2.0 preview, 5 November 2026 — the same, with an empty buildsDeleted list.
BatchGetBuildBatchesImplemented
BatchGetBuildsKnown differenceLocal observation: Reports the build as SUCCEEDED and COMPLETED, though its buildspec didn't run and no artifacts were produced. Local observation: Vera 1.2.0 preview, 5 November 2026 — the same for a build whose buildspec runs exit 97.
BatchGetCommandExecutionsImplemented
BatchGetFleetsImplemented
BatchGetProjectsImplementedLocal observation: Vera 1.2.0 preview, 5 November 2026 — read back a project created with a role record that already existed.
BatchGetReportGroupsImplemented
BatchGetReportsImplemented
BatchGetSandboxesImplemented
CreateFleetImplemented
CreateProjectKnown differenceLocal observation: Vera 1.2.2, 8 November 2026 — project metadata worked with a freshly created IAM role. Local observation: The observed project ARN uses local as its region instead of the request region. This was observed in the local example. Local observation: Vera 1.2.0 preview, 5 November 2026 — succeeded with an IAM role record that already existed, since creating a role failed in that release, and still returned a local ARN. A role ARN that doesn't exist was rejected.
CreateReportGroupImplemented
CreateWebhookImplemented
DeleteBuildBatchImplemented
DeleteFleetImplemented
DeleteProjectImplementedLocal observation: Vera 1.2.0 preview, 5 November 2026 — deleted a project created with a role record that already existed.
DeleteReportImplemented
DeleteReportGroupImplemented
DeleteResourcePolicyImplemented
DeleteSourceCredentialsImplemented
DeleteWebhookImplemented
DescribeCodeCoveragesImplemented
DescribeTestCasesImplemented
GetReportGroupTrendImplemented
GetResourcePolicyImplemented
ImportSourceCredentialsImplemented
InvalidateProjectCacheImplemented
ListBuildBatchesImplemented
ListBuildBatchesForProjectImplemented
ListBuildsImplemented
ListBuildsForProjectImplemented
ListCommandExecutionsForSandboxImplemented
ListCuratedEnvironmentImagesImplemented
ListFleetsImplemented
ListProjectsImplementedLocal observation: Vera 1.2.0 preview, 5 November 2026 — returned an empty projects list on an empty emulator, in this page's example.
ListReportGroupsImplemented
ListReportsImplemented
ListReportsForReportGroupImplemented
ListSandboxesImplemented
ListSandboxesForProjectImplemented
ListSharedProjectsImplemented
ListSharedReportGroupsImplemented
ListSourceCredentialsImplemented
PutResourcePolicyImplemented
RetryBuildImplemented
RetryBuildBatchImplemented
StartBuildFailed in testingLocal observation: Vera 1.2.2, 8 November 2026 — returned HTTP 501 NotIncluded. Local observation: Vera 1.2.0-rc.3, 6 November 2026 — returns HTTP 501 NotIncluded, because this Vera release doesn't include the build engine. A Pro license doesn't add the engine. The request named a project that doesn't exist; the refusal came before the project was looked up. The earlier observations that follow don't describe Vera 1.2.0-rc.3 or Vera 1.2.2. Local observation: earlier testing, 3 November 2026 — returned a build that was already SUCCEEDED and COMPLETED, with the same start and end time; the buildspec didn't run. Local observation: Vera 1.2.0 preview, 5 November 2026 — the same for a buildspec that runs exit 97, with no result from running anything.
StartBuildBatchFailed in testingLocal observation: Vera 1.2.0-rc.3, 6 November 2026 — returns HTTP 501 NotIncluded, because this Vera release doesn't include the build engine. A Pro license doesn't add the engine. The request named a project that doesn't exist; the refusal came before the project was looked up.
StartCommandExecutionImplemented
StartSandboxImplemented
StartSandboxConnectionImplemented
StopBuildImplementedMarks the already completed build STOPPED. Local observation: Vera 1.2.0 preview, 5 November 2026 — the same.
StopBuildBatchImplemented
StopSandboxImplemented
UpdateFleetImplemented
UpdateProjectImplemented
UpdateProjectVisibilityImplemented
UpdateReportGroupImplemented
UpdateWebhookImplemented