-
Notifications
You must be signed in to change notification settings - Fork 229
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
Add pull request workflow #1359
Add pull request workflow #1359
Conversation
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.
LGTM at a glance but some observations/questions:
- On Drone we ran
make docker-build
andmake build-rancher
is basically equivalent of it minus Docker. Why do we need to runmake package-rancher
? - Any specific reason we're running on
ubuntu-20.04
vs.ubuntu-latest
?
55c8c93
to
f0da508
Compare
I've updated to |
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.
LGTM
f0da508
to
d04a3bd
Compare
29d66ab
to
866fbbe
Compare
866fbbe
to
6efbc74
Compare
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.
Problem
#1351 missed a workflow for pull requests, as such we are not building and packaging the provider before allowing PRs to be merged
Solution
Add a pull request workflow which builds and packages the provider for each PR. This PR does not include the acceptance tests, as additional effort needs to be put into how we can modernize those tests such that they can work against a more modern version of rancher.
Testing
I've tested this workflow on my personal fork
Actions run: https://github.com/HarrisonWAffel/terraform-provider-rancher2/actions/runs/9571691853/job/26389359180