CLDSRV-835: Add troubleshooting details to CI

[BourgoisMickael]

• Add mongodb logs to artifacts
• Collect workflow telemetry

[bert-e]

Hello bourgoismickael,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.23%. Comparing base (1ff2d99) to head (0b93adb).
⚠️ Report is 29 commits behind head on development/9.3.
✅ All tests successful. No failed tests found.

Additional details and impacted files

see 2 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.3    #6106      +/-   ##
===================================================
- Coverage            84.25%   84.23%   -0.02%     
===================================================
  Files                  206      206              
  Lines                13251    13251              
===================================================
- Hits                 11164    11162       -2     
- Misses                2087     2089       +2     

Flag	Coverage Δ
file-ft-tests	67.91% <ø> (ø)
kmip-ft-tests	28.08% <ø> (ø)
mongo-v0-ft-tests	69.11% <ø> (ø)
mongo-v1-ft-tests	69.13% <ø> (-0.12%)	⬇️
multiple-backend	35.10% <ø> (ø)
sur-tests	36.46% <ø> (ø)
sur-tests-inflights	37.49% <ø> (+<0.01%)	⬆️
unit	69.90% <ø> (ø)
utapi-v2-tests	34.36% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[claude]

Supply chain risk: This pins to a branch (@use_quickchart) on a third-party fork. The branch can be force-pushed at any time with arbitrary code that runs in your CI. Pin to a specific commit SHA instead.

— Claude Code

[tcarmet]

I think that's fair, configuring it to the sha for now would be good and eventually when we know more about the state of the telemetry action we'll do something about it.

Or fork it inside the org (if you don't have permissions to do so let me know and I can do it for you).

[BourgoisMickael]

Replaced branch by commit in 0b93adb

[claude]

• Supply chain risk in .github/actions/setup-ci/action.yaml:59: the telemetry action is pinned to a branch on a third-party fork which can be force-pushed with malicious code. Pin to a full commit SHA to prevent tampering.

Review by Claude Code

[claude]

• Security: unpinned third-party GitHub Action - whywaita/workflow-telemetry-action@use_quickchart uses a branch ref instead of a pinned commit SHA. Pin to the commit SHA and keep the branch name as a comment.
  
  Review by Claude Code

[anurag4DSB]

Can we add some developer docs so that everyone knows how to use collected metrics

[BourgoisMickael]

Can we add some developer docs so that everyone knows how to use collected metrics

@anurag4DSB It's charts posted on the action summary: https://github.com/scality/cloudserver/actions/runs/23124100067?pr=6106

[claude]

LGTM

Review by Claude Code

[BourgoisMickael]

/approve

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge bugfix/CLDSRV-835-CI-details into
  development/9.3
• w/9.4/bugfix/CLDSRV-835-CI-details will be merged into development/9.4

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.8
• development/9.0
• development/9.1
• development/9.2

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

• ✔️ development/9.3

• ✔️ development/9.4

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.8
• development/9.0
• development/9.1
• development/9.2

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the
  current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/9.3

• ✔️ development/9.4

The following branches have NOT changed:

• development/7.10
• development/7.4
• development/7.70
• development/8.8
• development/9.0
• development/9.1
• development/9.2

Please check the status of the associated issue CLDSRV-835.

Goodbye bourgoismickael.