Skip to content
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

[BUG] Gradle check should be required before merging changes #12735

Closed
peternied opened this issue Mar 18, 2024 · 7 comments
Closed

[BUG] Gradle check should be required before merging changes #12735

peternied opened this issue Mar 18, 2024 · 7 comments
Labels
bug Something isn't working Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. discuss Issues intended to help drive brainstorming and decision making

Comments

@peternied
Copy link
Member

peternied commented Mar 18, 2024

Describe the bug

Pull requests have been merged without a passing gradle check introducing defects into main. [1] The gradle check is the minimal bar that all changes should pass before they are merged into main to ensure consistent code quality.

Expected behavior

Pull requests should only be allowed to merge without a passing gradle check by the Admin team for the project.

Additional Details

Additional context

@peternied peternied added bug Something isn't working untriaged labels Mar 18, 2024
@github-actions github-actions bot added the Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. label Mar 18, 2024
@peternied
Copy link
Member Author

My thoughts are that I do not think changes should be mergeable unless they pass the gradle check - save a justification that the admin team agrees with and then performs the override.

@andrross
Copy link
Member

[Triage - attendees 1 2 3 4 5 6]
@peternied Thanks for filing.

@andrross andrross added discuss Issues intended to help drive brainstorming and decision making and removed untriaged labels Mar 20, 2024
@peternied
Copy link
Member Author

@opensearch-project/admin Could you please update the branch protection rules to require the gradle check in all branches? We have 3 maintainers (myself, @sohami , @reta) approving this issue.

@reta
Copy link
Collaborator

reta commented Mar 20, 2024

@msfroh @dblock FYI :-)

@bbarani
Copy link
Member

bbarani commented Mar 20, 2024

gradle-check has been added as a mandatory check for all branches.

Screenshot 2024-03-20 at 2 59 51 PM

@reta
Copy link
Collaborator

reta commented Mar 20, 2024

Thanks a lot @bbarani !

@reta reta closed this as completed Mar 20, 2024
@mgodwan
Copy link
Member

mgodwan commented Mar 24, 2024

Pull requests have been merged without a passing gradle check introducing defects into main. [1]

@peternied Please note that the referred PR has not introduced any test defects. The failing tests are due to some other changes which have been fixed by the respective owners

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. discuss Issues intended to help drive brainstorming and decision making
Projects
None yet
Development

No branches or pull requests

5 participants