Update Mattermost to 9.7.1

• Please check this box if this contribution uses AI-generated content as outlined in the GitLab DCO & CLA

What does this MR do?

Update Mattermost to 9.7.1

Changelog: other

The full changelog for this release can be found here.

cc @amyblais @spirosoik @neil.barnett @jasonblais @toninis

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• MR title and description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• Latest Merge Result pipeline is green.
• When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

• The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
• If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
• If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
• If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes.
• Documentation created/updated.
• Tests added.
• Integration tests added to GitLab QA.
• Equivalent MR/issue for the GitLab Chart opened.
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.

Hey @akis.maziotis!

Thank you for your contribution to GitLab. Please refer to the contribution documentation for an overview of the process.

Did you know about our community forks? Working from there will make your contribution process easier. Please check it out!

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help, feel free to post @gitlab-bot help or initiate a mentor session on Discord. Read more on how to get help.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added Community contribution workflowin dev labels

assigned to @akis.maziotis

changed the description

@gitlab-bot label typemaintenance groupdistribution devopssystems

@gitlab-bot ready

added workflowready for review label and removed workflowin dev label

Some labels are not valid: devopssystems

added groupdistribution typemaintenance labels

@gitlab-bot label typemaintenance groupdistribution

	2 Warnings
	You've made some changes to the software definitions. Any change in software definition requires: package rebuild to verify that builds across the supported platforms are successful. manual verification to confirm the package is installable uses an approved license If the change does not affect existing functionality, for example when resolving rubocop warnings, adding comments, or fixing typos, add one of the following labels: maintenancepipelines maintenanceworkflow
	Please add a merge request subtype to this merge request.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@WarheadsSE (UTC-4)	@apatterson2 (UTC-6)

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

E2E Test Result Summary

allure-report-publisher generated test report!

qa-subset-test: test report for 87ecb13f

expand test summary

+---------------------------------------------------------------------+
|                           suites summary                            |
+----------------+--------+--------+---------+-------+-------+--------+
|                | passed | failed | skipped | flaky | total | result |
+----------------+--------+--------+---------+-------+-------+--------+
| Systems        | 3      | 7      | 0       | 1     | 10    | ❌     |
| Plan           | 108    | 6      | 11      | 5     | 125   | ❌     |
| Verify         | 0      | 45     | 0       | 5     | 45    | ❌     |
| Create         | 30     | 111    | 18      | 6     | 159   | ❌     |
| Release        | 5      | 0      | 0       | 0     | 5     | ✅     |
| Data Stores    | 35     | 20     | 0       | 0     | 55    | ❌     |
| Govern         | 61     | 33     | 1       | 1     | 95    | ❌     |
| Package        | 0      | 130    | 32      | 0     | 162   | ❌     |
| Monitor        | 20     | 4      | 1       | 4     | 25    | ❌     |
| GitLab Metrics | 1      | 1      | 1       | 0     | 3     | ❌     |
| Manage         | 0      | 2      | 0       | 0     | 2     | ❌     |
| Configure      | 1      | 0      | 0       | 0     | 1     | ✅     |
+----------------+--------+--------+---------+-------+-------+--------+
| Total          | 264    | 359    | 64      | 22    | 687   | ❌     |
+----------------+--------+--------+---------+-------+-------+--------+

qa-remaining-test-manual: test report for 87ecb13f

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Fulfillment | 2      | 0      | 75      | 0     | 77    | ✅     |
| Plan        | 215    | 0      | 16      | 0     | 231   | ✅     |
| Verify      | 126    | 0      | 30      | 0     | 156   | ✅     |
| Manage      | 27     | 0      | 9       | 0     | 36    | ✅     |
| Package     | 87     | 0      | 20      | 0     | 107   | ✅     |
| Create      | 464    | 0      | 69      | 0     | 533   | ✅     |
| Govern      | 161    | 0      | 6       | 0     | 167   | ✅     |
| Monitor     | 20     | 0      | 12      | 0     | 32    | ✅     |
| Data Stores | 104    | 0      | 1       | 0     | 105   | ✅     |
| Analytics   | 4      | 0      | 0       | 0     | 4     | ✅     |
| Release     | 14     | 0      | 3       | 0     | 17    | ✅     |
| Ai-powered  | 0      | 0      | 3       | 0     | 3     | ➖     |
| Secure      | 6      | 0      | 3       | 0     | 9     | ✅     |
| Growth      | 0      | 0      | 6       | 0     | 6     | ➖     |
| Configure   | 0      | 0      | 9       | 0     | 9     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 1230   | 0      | 262     | 0     | 1492  | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

added devopssystems group::distributionbuild labels

added sectioncore platform label

changed milestone to %17.0

added workflowin review label and removed workflowready for review label

requested review from @clemensbeck

Triggered a fresh build/QA since the last one was setting removed the sidekiq flag sidekiq (revert in gitlab!149888 (merged)), causing multiple failures.

Mattermost component upgrade test plan

Test plan

Build tests

• Built on all supported platforms
• Ran Trigger:ee-package and then qa-subset-test as well as manual qa-remaining-test-manual CI jobs on gitlab.com.

Fresh installation tests

Installed a Linux package created in the build system on a fresh OS installation and ran the following actions, checks, and tests:

• Installed Linux package with the new Mattermost version:

  • Verified that package installation logs/output shows no errors.
  • Verified Mattermost version by running /opt/gitlab/embedded/bin/mattermost version. 9.7.1

• Edited /etc/gitlab/gitlab.rb and set:

  • external_url
  • mattermost_external_url

  Both URLs should point to the same system so that GitLab and Mattermost are co-located. Example:

  external_url 'gitlab.example.com'
  mattermost_external_url 'mattermost.example.com'

• Ran gitlab-ctl reconfigure.

• Connected to gitlab.example.com.

• Navigated to Admin>Settings>Network>Outbound requests and added mattermost.example.com to Local IP addresses and domain names that hooks and services can accesss and clicked Save changes.

• Navigated to mattermost.example.com.

• Verified that single-sign on using GitLab credentials was working:

  1. Clicked on or create and account with GitLab.
  2. When presented with the Authorize GitLab Mattermost to use your account? page, clicked on Authorize. You should have landed on the Select teams page.

• Verified that when creating a group in GitLab, checking the box for Create a Mattermost team for this group also created a team in Mattermost and the GitLab user is a member of that team.

• Created a test project within the group created in the previous step and initialize with a README.

• Verified Mattermost slash command operation:

  • Enabled slash commands using GitLab documentation.
  • Tested slash commands by creating a new issue from the Mattermost instance. After following the prompt to re-authorize, the issue should have been successfully created in GitLab.

• Verified GitLab issue notification.

  • Configured incoming web hooks in Mattermost using the GitLab Documentation. Note that you have to configure both Mattermost and GitLab.
  • Using the created web hook, followed the documentation for adding notification support.
  • Created an issue in the test project. Verified that the notification for the issue appeared in Mattermost for the GitLab user.

Upgrade installation tests

Install a Linux package from the previous, latest minor number release on a fresh OS installation. Run the following actions, checks, and tests:

• Installed Linux package from the previous, latest minor number release 16.11.0:

  • Verified that package installation logs/output showed no errors.
  • Verified Mattermost version by running /opt/gitlab/embedded/bin/mattermost version. 9.6.1

• Edited /etc/gitlab/gitlab.rb and set:

  • external_url
  • mattermost_external_url

  Both URLs should point to the same system so that GitLab and Mattermost are co-located. Example:

  external_url 'gitlab.example.com'
  mattermost_external_url 'mattermost.example.com'

• Ran gitlab-ctl reconfigure.

• Connected to gitlab.example.com.

• Navigated to Admin>Settings>Network>Outbound requests and added mattermost.example.com to Local IP addresses and domain names that hooks and services can accesss and clicked Save changes.

• Navigated to mattermost.example.com.

• Verified that single-sign on using GitLab credentials is working:

  1. Clicked on or create and account with GitLab.
  2. When presented with the Authorize GitLab Mattermost to use your account? page, clicked on Authorize.
  3. You should have landed on the Select teams page.

• Verified that when creating a group in GitLab, checking the box for Create a Mattermost team for this group also created a team in Mattermost and the GitLab user is a member of that team.

• Created a test project within the group created in the previous step and initialized with a README.

• Verified Mattermost slash command operation:

  • Enabled slash commands using GitLab documentation.
  • Tested slash commands by creating a new issue from the Mattermost instance. After following the prompt to re-authorize, the issue should have been successfully created in GitLab.

• Verified GitLab issue notification.

  • Configured incoming web hooks in Mattermost using the GitLab Documentation. Note that you have to configure both Mattermost and GitLab.
  • Using the created web hook, followed the documentation for adding notification support.
  • Created an issue in the test project. Verified that the notification for the issue appears in Mattermost for the GitLab user.

Upgrade GitLab with a Linux package created with the new Mattermost version. Run the following actions, checks, and tests:

• Upgraded to package with new Mattermost version:

  • Verified that package installation logs/output shows no errors.
  • Verified Mattermost version by running /opt/gitlab/embedded/bin/mattermost version. 9.7.1

• Verified Mattermost slash command operation:

  • Tested slash commands by creating a new issue from the Mattermost instance. After following the prompt to re-authorize, the issue should have been successfully created in GitLab.

• Verified GitLab issue notification.

  • Created an issue in the test project. Verified that the notification for the issue appeared in Mattermost for the GitLab user.

mentioned in commit gitlab@888fa36d

mentioned in merge request gitlab!150277 (merged)

approved this merge request

gitlab.com/gitlab-org docs update: gitlab!150277 (merged)

requested review from @apatterson2

approved this merge request

LGTM.

merged

mentioned in commit 82c190a3

@akis.maziotis, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

1. React with a or a on this comment to describe your experience.
2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Subscribe to the GitLab Community Newsletter for contributor-focused content and opportunities to level up.

Thanks for your help!

This message was generated automatically. You're welcome to improve it.

added workflowstaging-canary label and removed workflowin review label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label