(CodeBuild Report Group): Defining the report type in CDK
See original GitHub issueWhen you create a new Report Group you should be able to select the report type (e,g,. Coverage)
There is no way to change the report type from Test to Coverage in props
new ReportGroup(this.scope, 'test-coverage', {reportGroupName: 'test-coverage'});
Use Case
Proposed Solution
Other
- 👋 I may be able to implement this feature request
- ⚠️ This feature might incur a breaking change
This is a 🚀 Feature Request
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:10 (5 by maintainers)
Top Results From Across the Web
class ReportGroup (construct) · AWS CDK
Grants the given entity permissions to write (that is, upload reports to) this report group. toString(), Returns a string representation of this construct....
Read more >@aws-cdk/aws-codebuild - npm
Start using @aws-cdk/aws-codebuild in your project by running `npm ... the project's role permissions to write reports to that report group:.
Read more >CodeBuild — Boto3 Docs 1.26.35 documentation
Contains information that defines how the build project reports the build status to the ... A list of one or more security groups...
Read more >awscodebuild - Go Packages
The type of reports in the report group. Example: var source source // create a new ReportGroup reportGroup := codebuild.NewReportGroup(this, jsii.String(" ...
Read more >Tracking PHPUnit Test Results in AWS CodeBuild Test ...
I am also going to share the AWS CDK code so you can easily replicate it to your other projects/services. Test Reports is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t really feel strongly either way. The only reason I suggested using an adjustment on the existing class was that it mirrors the underlying CFN resource more that way.
I suppose a better implementation here would be to have
ReportGroup
be an interface thatTestReportGroup
andCoverageReportGroup
could both implement, but I guess it’s too late to do that without impacting backwards compatibility.Another option would be to make ReportGroup take a property like I suggested earlier and have two subclasses while preserving the existing behavior as the default. Thoughts?
Today, they don’t have different properties, but they do have different valid combinations with the buildspec property on the related CodeBuild project object. The
reports/<report-group>/file-format
property of buildspecs can have test reports can be one ofCUCUMBERJSON | JUNITXML | NUNITXML | NUNIT3XML | TESTNGXML | VISUALSTUDIOTRX
, while coverage reports must have it be one ofCLOVERXML | COBERTURAXML | JACOCOXML | SIMPLECOV
.It’s worth calling out that buildspecs can be imported from files, so compile time guarantees can’t be made without additional runtime checking.
⚠️COMMENT VISIBILITY WARNING⚠️
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.