-
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
Simplify provider-ci makefile #993
Conversation
- Rewrite example provider testing targets to be more linear and easy to follow. - Move "test-workflows" to "test-providers". - Move config files for testing into each provider repo - named .ci-mgmt.yaml - just like the real repo. - Move temp linting repo into the bin directory which is fully ignored as it's just temp files.
b3e395e
to
e3f8626
Compare
d86a962
to
f54dd74
Compare
rm -rf bin/test-provider/$*/repo/.git | ||
|
||
# Fetch the latest .ci-mgmt.yaml from the provider repositories ready for testing. | ||
update-provider-configs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Who/what will be calling this target, and when?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just whenever we want to update our test data - would be manual right now but could create a CI job to call this. It seems like this hasn't been done in quite a while - see the follow-up PR stacked on this one.
- Use path filters to only test things that have changed. - Only run downstream tests for provider-ci.
0c3395b
to
f6a87e7
Compare
The ci-mgmt makefiles themselves don't use pulumictl - we only need this when calling `make upstream` during rollouts.
- Use explicit tag & cache. - Use custom token.
14e01d0
to
175e5b6
Compare
Update the test configs to match the real repos by running `make update-provider-configs`, then re-run `make` to re-generate. Stacked on #993
Rewrite example provider testing targets to be more linear and easy to follow. This is a clean-up in order to add more providers to test as we start to migrate new ones in (i.e. native providers & components).
This is now slightly faster for running both clean and repeated runs of
make
.Clean run on
make
:2.40s user 2.76s system 159% cpu 3.224 total
1.39s user 1.77s system 127% cpu 2.480 total
Repeated run of
make
:1.63s user 1.99s system 231% cpu 1.561 total
0.63s user 0.95s system 243% cpu 0.649 total