refactor(apps/prod/tekton/configs): use delicated publisher to fast tiup publishing

[wuhuizuo]

• make fast and stable for staging nightly ad RC tiup pkg publishing
• make fast and stable for GA tiup pkg publishing.
• rate limit for nightly is not implemented yet, so we still use old way for prod nightly publising.

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the pull request title and description, it seems like the changes made are related to optimizing the publishing of TIUP packages for different environments. The new implementation uses a dedicated publisher to speed up the publishing process for staging, nightly, and GA packages.

Looking at the diff, the main changes are the addition of a new task publish-tiup-from-oci-artifact-v2.yaml and the modification of the trigger template to use this task instead of the old one publish-tiup-from-oci-artifact.yaml. The new task fetches the manifest config, gets the .tiup file from the config, and loops to publish to the TIUP mirror.

However, there are a few potential issues that need to be addressed:

• The rate limit for nightly is not implemented yet, so the old way is still being used for prod nightly publishing. This could cause inconsistency in the publishing process and should be resolved before merging this PR.
• The new task is using a hard-coded URL for the publisher. It would be better to use a variable or configuration file to specify the URL, which would make it easier to switch between different publishers in the future.
• The new task does not have any error handling or retries in case of failures during publishing. This could cause the publishing process to fail silently, leading to issues down the line.

To address these issues, I suggest the following:

• Implement rate limiting for nightly publishing to ensure consistency across environments.
• Use a variable or configuration file to specify the publisher URL, which will make it easier to switch between different publishers in the future.
• Add error handling and retries to the new task to ensure that publishing failures are handled properly and do not cause issues down the line.

[wuhuizuo]

/approve

[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

Needs approval from an approver in each of these files:

• apps/prod/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]

I have already done a preliminary review for you, and I hope to help you do a better job.

This pull request aims to refactor the publish-tiup-from-oci-artifact.yaml task by adding a new task called publish-tiup-from-oci-artifact-v2.yaml to use a dedicated publisher to improve the stability and speed of publishing TIUP packages. The changes also allow for the customization of the publisher URL and force version. However, rate limiting for nightly is not implemented yet, so the old way is still used for prod nightly publishing.

One potential problem is that the rate limiting for nightly publishing is not yet implemented, which could cause issues with the stability and speed of publishing.

To fix this issue, the team could look into implementing rate limiting for nightly publishing to ensure that it is stable and efficient. Additionally, they could consider adding more tests to ensure that the changes made in this pull request do not cause any issues.

Overall, the changes made in this pull request seem to be beneficial for the stability and speed of publishing TIUP packages.