fileserver: remove unused fileserver.pingcap.net reference from docs-tidb-operator pipeline

[Copilot]

The merged_update pipeline for pingcap/docs-tidb-operator declared a FILE_SERVER_URL environment variable pointing to fileserver.pingcap.net, but the variable was never referenced in any pipeline step — the pipeline only builds PDFs locally and uploads them to Tencent Cloud via rclone.

Changes

• pipelines/pingcap/docs-tidb-operator/latest/merged_update.groovy: Remove the dead environment block containing FILE_SERVER_URL = 'http://fileserver.pingcap.net'

// Removed:
environment {
    FILE_SERVER_URL = 'http://fileserver.pingcap.net'
}

No behavioral change — the variable had no callers.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>fileserver: migrate artifacts for pingcap/docs-tidb-operator</issue_title>
<issue_description>Replace fileserver.pingcap.net usage for pingcap/docs-tidb-operator with OCI artifacts in a standard registry.

Acceptance criteria:

• No fileserver.pingcap.net references in jobs/pipelines for pingcap/docs-tidb-operator
• Artifacts pulled via OCI registry with documented paths
  </issue_description>

<agent_instructions>Please implement this using prow-jobs when possible.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes fileserver: migrate artifacts for pingcap/docs-tidb-operator #4219

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[ti-chi-bot]

Hi @Copilot. Thanks for your PR.

I'm waiting for a PingCAP-QE member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• pipelines/pingcap/docs-tidb-operator/OWNERS [wuhuizuo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-03-06 11:00:44.405877149 +0000 UTC m=+2275.917934809: ☑️ agreed by wuhuizuo.

[wuhuizuo]

/ok-to-test

[ti-chi-bot]

@copilot-swe-agent: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-replay-jenkins-pipelines	9b9941c	link	false	/test pull-replay-jenkins-pipelines

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.