[MXS-908] automatic prevention of bad stuff pushing Created: 2016-10-12  Updated: 2022-09-09  Resolved: 2022-09-09

Status: Closed
Project: MariaDB MaxScale
Component/s: test
Affects Version/s: None
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Timofey Turenko Assignee: Johan Wikman
Resolution: Won't Do Votes: 0
Labels: None


 Description   

certain branches should be protected from "bad stuff": push should be possible only if certain set of tests is green

 Comments   
Comment by Elena Stepanova [ 2022-03-13 ]

As you probably know, the foundation buildbot now runs branch protection for the server. I think it's of the similar version as the MDBE buildbot, so you should be able to adapt their solution if it's still a relevant task for MaxScale.

Comment by Timofey Turenko [ 2022-04-26 ]

Protected branches can be introduced in Github.

What is needed:

  • define set of tests to approve merge to protected branch (whole set should be 20--30 minutes max)
  • change current review process: first all changes should go to the developer branch, test are executed with this branch and then merge. Current process "post to rbt and then push directly to main branch" is not compatible with protected branches concept
Comment by Johan Wikman [ 2022-04-26 ]

What branches should be protected?

Generated at Thu Feb 08 04:02:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.