Add CI/CD settings for Automatic Deployment Rollbacks
What does this MR do?
This MR prepares the frontend work (and partly backend) to add CI/CD Project Settings item for Automatic Deployment Rollbacks
. The UI is conditionally rendered based on the availability of auto_deployment_rollback
licensed feature.
At this stage, the licensed feature is not added therefore the UI is never rendered.
Additionally, the More information
link has been commented out because the documentation page is not yet available. Check this discussion for more context.
Screenshots (strongly suggested)
Database migration output
- Migration
shinya@shinya-MS-7A34:~/workspace/thin-gdk/services/rails/src$ tre bin/rails db:migrate:up VERSION=20201027135651
INFO: This script is a predefined script in devkitkat.
== 20201027135651 AddAutoRollbackSetting: migrating ===========================
-- add_column(:project_ci_cd_settings, :auto_rollback_enabled, :boolean, {:default=>false, :null=>false})
-> 0.0007s
== 20201027135651 AddAutoRollbackSetting: migrated (0.0025s) ==================
- Rollback
shinya@shinya-MS-7A34:~/workspace/thin-gdk/services/rails/src$ tre bin/rails db:migrate:down VERSION=20201027135651
INFO: This script is a predefined script in devkitkat.
== 20201027135651 AddAutoRollbackSetting: reverting ===========================
-- remove_column(:project_ci_cd_settings, :auto_rollback_enabled)
-> 0.0005s
== 20201027135651 AddAutoRollbackSetting: reverted (0.0023s) ==================
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Related to #35404 (closed)
Edited by Shinya Maeda