-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a generic template #1132
Comments
generate_coverage_data should be replaced by Codecov: actually this will destroy our system of tracking the bridged example conversion data quality (what generate_coverage_data) does, and I do not think this is advisable as no equivalent exists in codecov. |
Couple more notes here. I think we should close this as won't fix in favor of onboarding the remaining providers onto a modified version of the bridged workflow, as done for awsx and continuing two api-gateway and eks. The bridge workflow automatically satisfies:
In addition to this some work has been done to cover:
Remainders, it appears these are more nice to have:
|
On #1131 we decided with @danielrbradley not to go as written but introduce some simpler form of configuration-driven script entry point overrides. This seems good enough to support AWSX, and I am following up to remove all custom make commands from the repos that had them. Make in particular Not planning to do anything else here for this iteration. |
We now have a "generic" template in provider-ci that's in use by AWSX, EKS and aws-api-gateway, so I think we can consider this complete. |
Cannot close issue:
Please fix these problems and try again. |
We should create a new workflow template which does not assume anything about the underlying provider.
The contract between CI and the provider should be driven entirely by
make
targets.make
is not necessarily the best task runner for this purpose, but it's the one we use most widely right now so we should start there.As we build this template, keep in mind that it should eventually be able to work equally well with native providers, component providers, or bridged providers. However our initial goal is to use it with providers not currently managed by ci-mgmt.
We should use the existing bridged provider template as a starting point as this is already quite battle-tested.
Changes we should consider making to the bridged template:
make
target customization #1131. Concretely, this means if a provider previously needed a separate action to perform e.g. some setup, we should instead try to do that as part of amake
target override or we should do it inside the test itself. This is a good practice in general as it makes things easier to reproduce locally. Examples of options we likely don't need:lint
action by default.generate_coverage_data
should be replaced by Codecov.gotestfmt
.The text was updated successfully, but these errors were encountered: