Replies: 1 comment 1 reply
-
|
For "the DBA approves the request", do you mean the change is released to the database or the risk-based issue approval step? I guess the goal is to make sure database changes pushed before deploying software? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yes, after the database changes are completed, then proceed with the subsequent CD process on GitLab to complete the deployment of the application. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We need the database change process as follows:
1、Developers push code to the development branch, triggering the CI process to automatically check the database change scripts.
2、When a feature development is completed and the code is merged into the main branch, the CD process is automatically or manually triggered. In one phase of the CD process, a request is submitted to ByteBase, and the DBA needs to manually review it. After the DBA approves the request, a callback to GitLab is made to execute the remaining CD process.
Can the CD process be triggered by a callback to GitLab after approval? What methods does ByteBase provide?
Beta Was this translation helpful? Give feedback.
All reactions