fix(apps/prod/tekton/configs/triggers): support devbuild to trigger darwin targets

[wuhuizuo]

Signed-off-by: wuhuizuo [email protected]

[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 that the changes in this pull request aim to support devbuild to trigger darwin targets. The diff shows that the os parameter has been removed from the GitHub branch push, GitHub PR, and GitHub tag create bindings, and the build-component template has been replaced with build-component-all-platforms in those bindings.

Some potential problems that I see in this pull request are:

1. Lack of context: The pull request description and diff do not provide enough context about why the os parameter was removed and what impact it will have on the overall system. It would be helpful to have some additional explanations to understand the reasoning behind the changes.

2. Testing: It is unclear whether the changes in this pull request were tested before submitting the pull request. It would be best if the changes were tested and validated in a non-production environment before merging them into the main branch.

3. Regression: Removing the os parameter from the bindings might cause some regression issues if the system assumes that the target platform is always Linux. If the system has any dependencies or requirements specific to the Darwin platform, those issues might not be detected until the changes are deployed.

To fix these potential problems, I suggest the following:

1. Add some context to the pull request description, explaining why the os parameter was removed and what impact it will have on the overall system.

2. Test the changes in a non-production environment to ensure that they work as expected and do not cause any regression issues.

3. Consider adding some additional checks to ensure that the system can handle both Linux and Darwin platforms, even if the os parameter is not present in the bindings. This could include adding some conditional logic or validation checks to ensure that the appropriate dependencies or requirements are met for both platforms.

[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