Started by GitHub push by ti-chi-bot[bot]Started by GitHub push by ti-chi-bot[bot]00186381863854376543761.00505450548575afecb37a85d8d4c68bf47ba1d4a2999a2e401fa5afecb37a85d8d4c68bf47ba1d4a2999a2e401faorigin/main5afecb37a85d8d4c68bf47ba1d4a2999a2e401fa5afecb37a85d8d4c68bf47ba1d4a2999a2e401faorigin/main5afecb37a85d8d4c68bf47ba1d4a2999a2e401fa5afecb37a85d8d4c68bf47ba1d4a2999a2e401faorigin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#8575437683303seed #857857falsefalse8571173022SUCCESS1750330812124https://do.pingcap.net/jenkins/view/all/job/seed/857/default-sj0qqpipelines/pingcap/tidb/latest/pull_build_next_gen/pipeline.groovy5afecb37a85d8d4c68bf47ba1d4a2999a2e401fa1750330785000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfix(pingcap/tidb): add `-next-gen` flag to pluginpkg commands for plugins (#3597) This pull request updates the pipeline configuration to use the next-generation plugin packaging approach for compiling Go plugins. The changes ensure that the `pluginpkg` command includes the `-next-gen` flag when processing plugins. Pipeline configuration updates: * [`pipelines/pingcap/tidb/latest/pull_build_next_gen/pipeline.groovy`](diffhunk://#diff-5d07f8a0316f7735c0722f8e9c4a63832c0fdef8f6ce42ee56dac322b85304c1L99-R103): Updated the `pluginpkg` command to include the `-next-gen` flag for both the `audit` and `whitelist` Go plugins, reflecting a shift to the next-generation plugin packaging method. 2025-06-19 10:59:45 +00005afecb37a85d8d4c68bf47ba1d4a2999a2e401fafix(pingcap/tidb): add `-next-gen` flag to pluginpkg commands foreditpipelines/pingcap/tidb/latest/pull_build_next_gen/pipeline.groovygithttps://do.pingcap.net/jenkins/user/noreplynoreply