自动构建设置的触发关键词应可关闭，触发构建望可通知企微或钉钉。

[sundaqiang]

1. 部分场景下，开发、测试、生产环境是独立分支的。

   • 当指定分支部署的时候，自动构建设置的触发关键子并不是必须的。

   • 所以希望能有选项不设置这个关键字触发。

2. 触发自动部署的情况下，现在都要去后台查看是否成功。

   • 希望能够在如下节点可以通知外部，如企微和钉钉。

   1. 启动构建计划，通知内容可包含如下
      a.commit：70dd1c127f5553477e2b58de32fc695ef49c75d2
      b.触发方式：仓库 xxxxx/xxxxx 推送至分支 master 触发
      c.状态：开始执行

   2. 构建计划执行结束（构建结束状态可以是“构建结束”也可以是“组件重启完成”）
      a.commit：70dd1c127f5553477e2b58de32fc695ef49c75d2
      b.触发方式：仓库 xxxxx/xxxxx 推送至分支 master 触发
      c.状态：执行完毕
      d.耗时：3 m 14 s
      e.状态消息：SUCCEED||FAILED

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Title: The trigger keyword of the automatic build setting should be able to be turned off, and the trigger build is expected to notify Qiwei or DingTalk.

1. In some scenarios, the development, testing, and production environments are independent branches.
   When deploying to a specific branch, the trigger key for the automatic build setting is not required.
   So I hope there is an option not to set this keyword trigger.
2. When automatic deployment is triggered, now you have to go to the background to check whether it is successful.
   It is hoped that the following nodes can be used to notify the outside world, such as Qiwei and DingTalk.
   A. Start the build plan, and the notification content can include the following
   a.commit:70dd1c127f5553477e2b58de32fc695ef49c75d2
   b. Triggering method: Push warehouse xxxxx/xxxxx to branch master to trigger
   c. Status: Start execution
   B. The build plan execution ends (the build end status can be "build completed" or "component restart completed")
   a.commit:70dd1c127f5553477e2b58de32fc695ef49c75d2
   b. Triggering method: Push warehouse xxxxx/xxxxx to branch master to trigger
   c. Status: Execution completed
   d. Time consumption: 3 m 14 s
   e. Status message: SUCCEED||FAILED