Enable third-party UCM flags by default
What does this MR do and why?
This MR sets bitbucket_server_user_mapping
and gitea_user_mapping
to be
enabled by default for self-managed instances.
The paired flag, importer_user_mapping
was enabled by default in
!175371 (merged)
The flag for GitHub was enabled by default in !176633 (merged)
Changelog: changed
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
- MR to enable UCM by default: !175371 (merged)
- Rollout issue for
bitbucket_server_user_mapping
FF: #509897 (closed) - Rollout issue for this
gitea_user_mapping
FF: #498390 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Merge request reports
Activity
assigned to @jnutt
changed milestone to %17.8
added pipelinetier-1 label
@rodrigo.tomonari, could you please review this upon your return from PTO, since you reviewed the MR for the main flag?
requested review from @rodrigo.tomonari
- A deleted user
added documentation feature flag labels
- Resolved by Rodrigo Tomonari
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/user/project/import/index.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
added 1 commit
- 64fe261b - Enable bitbucket_server_user_mapping by default
added 135 commits
-
64fe261b...248d2e7f - 134 commits from branch
master
- ca5fc5a5 - Enable bitbucket_server_user_mapping by default
-
64fe261b...248d2e7f - 134 commits from branch
- Resolved by Rodrigo Tomonari
added pipeline:mr-approved label
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-cng:
test report for b381a702expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Plan | 86 | 0 | 8 | 0 | 94 | ✅ | | Verify | 51 | 0 | 15 | 0 | 66 | ✅ | | Govern | 84 | 0 | 10 | 0 | 94 | ✅ | | Create | 140 | 0 | 19 | 1 | 159 | ✅ | | Package | 30 | 0 | 14 | 0 | 44 | ✅ | | Data Stores | 33 | 0 | 10 | 0 | 43 | ✅ | | Ai-powered | 0 | 0 | 2 | 0 | 2 | ➖ | | Manage | 1 | 0 | 9 | 0 | 10 | ✅ | | Configure | 0 | 0 | 3 | 0 | 3 | ➖ | | Monitor | 8 | 0 | 12 | 0 | 20 | ✅ | | Release | 5 | 0 | 1 | 0 | 6 | ✅ | | Secure | 2 | 0 | 5 | 0 | 7 | ✅ | | Fulfillment | 2 | 0 | 7 | 0 | 9 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | ModelOps | 0 | 0 | 1 | 0 | 1 | ➖ | | Growth | 0 | 0 | 2 | 0 | 2 | ➖ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 444 | 0 | 118 | 1 | 562 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-test-on-gdk:
test report for b381a702expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Package | 50 | 0 | 26 | 0 | 76 | ✅ | | Create | 270 | 0 | 40 | 0 | 310 | ✅ | | Verify | 100 | 0 | 32 | 0 | 132 | ✅ | | Monitor | 16 | 0 | 24 | 0 | 40 | ✅ | | Data Stores | 66 | 0 | 20 | 0 | 86 | ✅ | | ModelOps | 0 | 0 | 2 | 0 | 2 | ➖ | | Fulfillment | 4 | 0 | 14 | 0 | 18 | ✅ | | Plan | 164 | 0 | 16 | 0 | 180 | ✅ | | Secure | 8 | 0 | 6 | 0 | 14 | ✅ | | Govern | 160 | 0 | 24 | 0 | 184 | ✅ | | Manage | 2 | 0 | 18 | 0 | 20 | ✅ | | Release | 10 | 0 | 2 | 0 | 12 | ✅ | | Configure | 0 | 0 | 6 | 0 | 6 | ➖ | | Ai-powered | 0 | 0 | 4 | 0 | 4 | ➖ | | Growth | 0 | 0 | 4 | 0 | 4 | ➖ | | Analytics | 4 | 0 | 0 | 0 | 4 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 854 | 0 | 238 | 0 | 1092 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-test-on-omnibus:
test report for b381a702expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Plan | 164 | 0 | 16 | 0 | 180 | ✅ | | Data Stores | 66 | 0 | 20 | 0 | 86 | ✅ | | Package | 50 | 0 | 26 | 0 | 76 | ✅ | | Manage | 4 | 0 | 16 | 0 | 20 | ✅ | | Growth | 0 | 0 | 4 | 0 | 4 | ➖ | | Govern | 168 | 0 | 16 | 0 | 184 | ✅ | | Create | 683 | 0 | 95 | 4 | 778 | ✅ | | Verify | 102 | 0 | 30 | 2 | 132 | ✅ | | Fulfillment | 4 | 0 | 14 | 0 | 18 | ✅ | | Release | 10 | 0 | 2 | 0 | 12 | ✅ | | Monitor | 16 | 0 | 24 | 0 | 40 | ✅ | | Configure | 0 | 0 | 6 | 0 | 6 | ➖ | | Secure | 8 | 0 | 6 | 0 | 14 | ✅ | | ModelOps | 0 | 0 | 2 | 0 | 2 | ➖ | | Ai-powered | 0 | 0 | 4 | 0 | 4 | ➖ | | Analytics | 4 | 0 | 0 | 0 | 4 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 1279 | 0 | 281 | 6 | 1560 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
removed pipeline:run-e2e-omnibus-once label
added Importer:Bitbucket Server Importer:Gitea labels
- Resolved by James Nutt
- Resolved by James Nutt
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/user/project/import/index.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
Hey there
, could you please make sure this merge request gets merged?The merge request is set to auto-merge, but it is not currently mergeable (MR
detailed_merge_status
is discussions_not_resolved).This message was generated automatically. Improve it or delete it.
started a merge train
mentioned in commit 7f3caaac
mentioned in merge request !176984 (merged)
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
mentioned in issue #509897 (closed)
mentioned in issue #498390 (closed)
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label