Adjust labels and docs to remove beta for self-hosted models
What does this MR do and why?
- Adjust labels and docs to remove beta for self-hosted models
Related to: #520666 (closed)
Merge request reports
Activity
changed milestone to %17.10
added groupcustom models maintenancerefactor typemaintenance labels
assigned to @mhamda
added pipelinetier-1 label
added devopsai-powered sectiondata-science labels
added documentation frontend labels
1 Message This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive. Documentation review
The following files require a review from a technical writer:
-
doc/administration/gitlab_duo_self_hosted/configure_duo_features.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.
Reviewer roulette
Category Reviewer Maintainer frontend @davidhampgonsalves
(UTC-4, 5 hours behind author)
@cngo
(UTC+0, 1 hour behind author)
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by ****-
mentioned in issue #520666 (closed)
added 1 commit
- a03fb063 - Adjust Self-hosted models in the Duo chat page
- Resolved by Coung Ngo
@marina.mosti Do you mind reviewing this small change?
requested review from @marina.mosti
added pipeline:mr-approved label
added pipelinetier-2 label 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.
requested review from @cngo
Bundle size analysis [beta]
This compares changes in bundle size for entry points between the commits 7f074d1f and a03fb063
Special assetsEntrypoint / Name Size before Size after Diff Diff in percent average 4.88 MB 4.88 MB - 0.0 % mainChunk 3.77 MB 3.77 MB - 0.0 %
Note: We do not have exact data for 7f074d1f. So we have used data from: c0251475.
The intended commit has no webpack pipeline, so we chose the last commit with one before it.Please look at the full report for more details
Read more about how this report works.
Generated by
DangerEdited by ****E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for a03fb063expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 135 | 0 | 23 | 0 | 158 | ✅ | | Verify | 51 | 0 | 21 | 0 | 72 | ✅ | | Plan | 82 | 0 | 8 | 0 | 90 | ✅ | | Data Stores | 33 | 0 | 10 | 0 | 43 | ✅ | | Govern | 79 | 0 | 13 | 0 | 92 | ✅ | | Configure | 0 | 0 | 3 | 0 | 3 | ➖ | | Fulfillment | 2 | 0 | 7 | 0 | 9 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Package | 24 | 0 | 14 | 0 | 38 | ✅ | | Manage | 1 | 0 | 9 | 0 | 10 | ✅ | | Release | 5 | 0 | 1 | 0 | 6 | ✅ | | Monitor | 8 | 0 | 12 | 0 | 20 | ✅ | | Ai-powered | 0 | 0 | 2 | 0 | 2 | ➖ | | Secure | 5 | 0 | 3 | 0 | 8 | ✅ | | Growth | 0 | 0 | 2 | 0 | 2 | ➖ | | ModelOps | 0 | 0 | 1 | 0 | 1 | ➖ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 427 | 0 | 129 | 0 | 556 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-test-on-cng:
test report for a03fb063expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Plan | 86 | 0 | 8 | 0 | 94 | ✅ | | Create | 140 | 0 | 22 | 0 | 162 | ✅ | | Govern | 84 | 0 | 10 | 0 | 94 | ✅ | | Verify | 52 | 0 | 20 | 0 | 72 | ✅ | | ModelOps | 0 | 0 | 1 | 0 | 1 | ➖ | | Monitor | 8 | 0 | 12 | 0 | 20 | ✅ | | Data Stores | 33 | 0 | 10 | 0 | 43 | ✅ | | Package | 29 | 0 | 15 | 0 | 44 | ✅ | | Manage | 1 | 0 | 9 | 0 | 10 | ✅ | | Secure | 3 | 0 | 5 | 0 | 8 | ✅ | | Release | 5 | 0 | 1 | 0 | 6 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Fulfillment | 2 | 0 | 7 | 0 | 9 | ✅ | | Configure | 0 | 0 | 3 | 0 | 3 | ➖ | | Ai-powered | 0 | 0 | 2 | 0 | 2 | ➖ | | Growth | 0 | 0 | 2 | 0 | 2 | ➖ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 445 | 0 | 127 | 0 | 572 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
Edited by ****added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-2 label
- Resolved by Mohamed Hamda
started a merge train
mentioned in commit 0ce43dd8
mentioned in merge request !182409 (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
- Resolved by Julie Huang
Hey @mhamda, I just noticed this change. May I ask why the beta label was removed from this check-box please? I didn't see a linked issue. The original label was correct — this checkbox is for enabling beta models where the Testing Agreement needs to be accepted. However it is not required for self-hosted models GA features (which is everything except for the beta models themselves).
In future, are you able to tag me for any frontend reviews on groupcustom models work please? It was a little confusing to discover this as I thought it was a regression.
mentioned in merge request !182688 (merged)
added workflowpost-deploy-db-staging label and removed workflowproduction label