Plugin failed to upload data: Request handler not found about sbt-codacy-coverage

[onema]

At this time, I'm able to bypass this issue by using a condition in my buildspec.yml that skips the coverage report if the CODEBUILD_SOURCE_VERSION does not match a git-sha:

      - echo Submit coverage report to Codacy
      - if [[ $CODEBUILD_SOURCE_VERSION =~ [0-9a-f]{5,40} ]] ; then sbt codacyCoverage; fi

Is this an issue with the plugin? or is something I have to live with when using codebuild?

[rtfpessoa]

Hi @onema, isn't the content of CODEBUILD_SOURCE_VERSION always the commit uuid being built?

[onema]

According to the docs

CODEBUILD_SOURCE_VERSION: For Amazon S3, the version ID associated with the input artifact. For AWS CodeCommit, the commit ID or branch name associated with the version of the source code to be built. For CODEBUILD_RESOLVED_SOURCE_VERSIONGitHub, the commit ID, branch name, or tag name associated with the version of the source code to be built.

I’m not sure why the pr is a special case :(

[rtfpessoa]

We always need a commit to submit coverage. I think the best we can do is remove that variable and you can pass the commit from the CLI.

[onema]

I found this in the AWS forums: Github pull requests are built twice

Basically, the simplest thing to do is to disable the PR from the CodeBuild webhook.

The GitHub checks will still run and get reported on PRs as long as the push event triggers CodeBuild.

I'm closing this issue, as I consider this being a CodeBuild problem and not a plugin problem.

As usuall, thank you for the quick response!

[onema]

For reference, this is the CodeBuild definition I've been using

codebuild-4scala_cfn.yml